Sync repo docs and next-step plan with completed mechanika v1.0

[Copilot]

mechanika/ is now filled and has become the gameplay source of truth, but the top-level docs and workflow still described it as a placeholder. This updates the repo documentation and action plan so implementation work can start from the current spec instead of Sprint 0 assumptions.

• Source-of-truth update

  • Repositioned mechanika/ as the authoritative gameplay spec in README.md, docs/GDD.md, docs/SCOPE.md, and docs/ARCHITECTURE.md
  • Removed placeholder framing that implied mechanics were still pending or undefined
  • Tightened cross-document responsibilities: brief = product frame, fabula = canon, mechanika = gameplay rules, GDD = implementation/state tracking

• Implementation plan refresh

  • Rewrote the “what next” guidance in README.md
  • Moved the repo plan to:
    1. sync docs,
    2. resolve critical blockers from mechanika/99-open-questions.md,
    3. scaffold Vite + Phaser 4,
    4. derive schemas/systems from approved mechanics
  • Explicitly called out B1/B7 as the immediate pre-implementation decisions

• Scope and architecture alignment

  • Updated MVP scope to reflect the actual approved scene set, systems, resources, missions, events, and ending model from mechanika/
  • Refined architecture notes so deferred items are only the parts still intentionally post-MVP or unresolved, rather than the whole mechanics layer
  • Clarified which systems now have concrete implementation targets vs. which remain stub-only

• Workflow/documentation sync

  • Updated docs/COPILOT_WORKFLOW.md so the recommended sequence starts from mechanika sync and blocker resolution, not pre-mechanika discovery
  • Adjusted prompt guidance for /gdd, /fabula, /new-system, and /new-event to discourage drifting away from the approved spec
  • Updated docs/FABULA.md to reference the docs/files that now need ongoing synchronization rather than “next files to fill”

Example of the updated source-of-truth order:

1. `mechanika/` for final gameplay mechanics.
2. `docs/FABULA.md` for narrative canon and story direction.
3. `docs/SCOPE.md` for MVP boundaries and post-MVP exclusions.
4. `docs/ADRs/` for accepted technical decisions.
5. `docs/ARCHITECTURE.md` for project structure and system boundaries.

[Copilot]

Pull request overview

Updates repository documentation and workflow guidance to reflect that mechanika/ now contains the approved gameplay specification v1.0 (with remaining blockers tracked), so implementation can proceed from the current spec rather than Sprint 0 placeholders.

Changes:

• Repositions mechanika/ as the gameplay source of truth across core docs and refreshes “what next” guidance to prioritize doc sync + resolving B1/B7 blockers.
• Aligns MVP scope/scene list/system responsibilities with the concrete v1.0 spec (missions, events, endings, resources, systems).
• Updates Copilot workflow sequencing and prompt usage guidance to discourage drifting from approved mechanics.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
README.md	Updates current status and next-step plan to start from mechanika/ v1.0 + open blockers.
docs/SCOPE.md	Rewrites MVP scope to match the approved v1.0 scene set, models, content volume, and known blockers.
docs/GDD.md	Reframes GDD as an implementation/readiness tracker synced to mechanika/, with an updated action plan.
docs/FABULA.md	Updates the “keep in sync” list to reflect mechanika-driven implementation and failure/ending alignment.
docs/COPILOT_WORKFLOW.md	Adjusts recommended prompt order and guardrails to begin with mechanika sync + blocker resolution.
docs/ARCHITECTURE.md	Aligns deferred/mechanics notes and system responsibilities with mechanika v1.0 (combat still deferred).