Reorganize documentation into canonical repository layout

Adopt CoulombSocial/HelixForge/MarkiTect documentation structure:
- research/260608-yawex-prior-art/ — yawex exploration and sources
- demand/ — inbound NetKingdom integration requirements
- spec/ — PRD, TSD, UseCaseCatalog, ArchitectureBlueprint scaffolds
- docs/ — stakeholder documentation and repository-layout guide
- wiki/, issues/, history/ — scaffolded directories

Add SCOPE.md and AGENTS.md. Update workplan paths and README.

workplans/SHARD-WP-0001-yawex-requirements.md

@@ -22,10 +22,10 @@ that map onto `INTENT.md` without inheriting yawex's monolithic engine shape.
 
 ## Context
 
-- Prior art: `history/priorart/yawex-0.7.4/`
-- Requirements seed: `docs/requirements-from-yawex.md`
-- Access model draft: `docs/access-model-blueprint.md`
-- NetKingdom integration draft: `docs/requirements-user-engine-netkingdom.md`
+- Prior art: `research/260608-yawex-prior-art/sources/yawex-0.7.4/`
+- Research findings: `research/260608-yawex-prior-art/findings.md`
+- Architecture: `spec/ArchitectureBlueprint.md`
+- Inbound demand: `demand/260608-netkingdom-integration-requirements.md`
 
 Open architectural thread: a minimal authorization model in core revises an
 INTENT non-goal and needs a ratified INTENT amendment before the access model
@@ -111,7 +111,7 @@ red-link extension. Open question: core vs reference-UI concern.
 
 ## Acceptance criteria
 
-- Each task produces a written spec or ADR-ready design note in `docs/`.
+- Each task produces a written spec or ADR-ready design note in `spec/`.
 - Designs honor INTENT boundaries: mechanism over policy, union without erasure,
   overlay before mutation, capability-aware adapters.
 - Access-model and NetKingdom integration drafts are either ratified or explicitly