docs: PHASE-NEXT implementation plan for the post-launch roadmap#12
Merged
Conversation
WS0 ds-mcp vendored-core re-pin (step zero), WS1 FM-11 take-it-home, WS2 FM-10 design-system-swap groundwork, WS3 FM-7 completion. Per workstream: file-level tasks, cross-repo dependency order, agent vs owner gating, fail-first tests including three honesty checks (golden-context vs stale pin, validate-box agreement with fixture-001, receipt-hash-identical design-system swap), risks, and exit criteria. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a new roadmap document (docs/PHASE-NEXT.md) describing the planned “Phase Next” post-launch workstreams and sequencing across repos (including ds-mcp, dspack-gen, and future studio work).
Changes:
- Introduces a four-workstream plan (WS0–WS3) with task breakdowns, gating, risks, tests, and exit criteria.
- Documents cross-repo dependency ordering (ds-mcp re-pin/release; upstream shadcn contract work).
- Calls out “fail-first” testing discipline and multiple “honesty check” validations as phase requirements.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+4
to
+7
| FM-1 through FM-6, FM-8, FM-9, and FM-12 are shipped. npm publishing across | ||
| the ecosystem is resolved: dspack-gen 0.1.1, dspack-emit 0.3.1, and ds-mcp | ||
| 0.3.0 are published, match their repos, and the studio consumes the | ||
| published versions. This phase covers, in priority order: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
docs/PHASE-NEXT.md, the implementation plan for the next development phase (post-launch roadmap), covering four workstreams in priority order:374e1cd(verified: the onlysrc/corediff past the tag is a test file the vendor bundle never ships), golden-context honesty test written fail-first against the stalef651433bundle, report-only pin-drift CI check, ds-mcp 0.3.1 release with an optional trusted-publishing move.packages/shadcn-renderers, second gated catalog via dspack-emit's existingshadcnProfile, swap UI, CI additions; the owner-authored upstream shadcn contract extension is treated as a placeholder input with its required shape specified.runPipelinefor the live path; fixture-007).Per workstream: file-level touch points, cross-repo dependency order (ds-mcp re-pin; upstream shadcn contract), agent-executable vs owner-gated per task, fail-first test requirements including three honesty checks (ds-mcp served schema vs gen 0.1.1 goldens, validate-box agreement with fixture-001's recorded findings, receipt-hash-identical design-system swap), risks with mitigations, and phase-exit-style criteria. Ends by naming the highest-leverage first task: the golden-context assertion that fails on the stale pin.
Docs-only change; no implementation code.
🤖 Generated with Claude Code