Context
The full-source audit for docs/InReview/MVP_EXPANSION/ confirmed that the main Wave I productization work is now seeded and documented, but a secondary layer from the source packs was only preserved as deferred follow-through.
Audit source:
docs/analysis/2026-03-07_mvp-expansion-source-coverage-audit.md
This secondary set is real and useful, but it should stay below Wave I in urgency.
It should be visible as a dependency-aware lower-priority wave instead of disappearing into notes.
Goal
Seed the deferred secondary MVP-expansion follow-through as a lower-priority wave covering:
- in-app demoability/product-evidence surfaces
- demo-director/harness maturity follow-through
- post-Wave-I productivity follow-through
- broader note/import/clip intake follow-through
Priority posture
- Child issues in this wave intentionally mix
Priority III and Priority IV.
- This wave must not outrun Wave I (
#318, #320, #322, #324, #326, #96, #100, #328).
Child issue checklist
Reuse-first rules
Do not duplicate scope where existing issues are already the correct anchor:
#93 for broader global search/launcher behavior
#216 for public-facing thesis/demo/landing framing
#75, #218, #219 for delivered or already-seeded import/capture-source overlap
#77 for broader dashboard-scale telemetry work
#311 as the completed historical demo-epic hardening pass; build follow-through on top of it instead of reopening it
Acceptance Criteria
Verification
node scripts/check-docs-governance.mjs
node scripts/check-github-ops-governance.mjs
Suggested branch
docs/mvp-secondary-followthrough-wave
Context
The full-source audit for
docs/InReview/MVP_EXPANSION/confirmed that the main Wave I productization work is now seeded and documented, but a secondary layer from the source packs was only preserved as deferred follow-through.Audit source:
docs/analysis/2026-03-07_mvp-expansion-source-coverage-audit.mdThis secondary set is real and useful, but it should stay below Wave I in urgency.
It should be visible as a dependency-aware lower-priority wave instead of disappearing into notes.
Goal
Seed the deferred secondary MVP-expansion follow-through as a lower-priority wave covering:
Priority posture
Priority IIIandPriority IV.#318,#320,#322,#324,#326,#96,#100,#328).Child issue checklist
Priority III)Priority III)Priority III)Priority IV)Priority IV)Reuse-first rules
Do not duplicate scope where existing issues are already the correct anchor:
#93for broader global search/launcher behavior#216for public-facing thesis/demo/landing framing#75,#218,#219for delivered or already-seeded import/capture-source overlap#77for broader dashboard-scale telemetry work#311as the completed historical demo-epic hardening pass; build follow-through on top of it instead of reopening itAcceptance Criteria
#107and canonical docs are updated to reflect the seeded lower-priority wave.Verification
node scripts/check-docs-governance.mjsnode scripts/check-github-ops-governance.mjsSuggested branch
docs/mvp-secondary-followthrough-wave