Author the MVP rollup mission manifest at docs/MISSION-MANIFEST.md. Replaces the install-ux-v2 manifest that previously occupied the slot — that sub-mission is archived as complete (IUV-M03 substantively shipped via PR #446 + releases 0.0.27 → 0.0.29).
The new manifest treats MVP as a rollup:
Federation v1 declared as workstream W1 (planning-complete; 7 milestones; manifest at docs/federation/MISSION-MANIFEST.md; tracking issues #460–#466)
Three-surface parity (webUI / TUI / CLI) encoded as cross-cutting requirement MVP-X1 so it cannot be silently dropped
"Likely Additional Workstreams" pre-staged from PRD scope without committing execution capacity — scope creep is named and accommodated, not denied
Phase 0–8 history (sessions 1–14, 2026-03-13 → 2026-03-15) preserved in the scratchpad as prior execution context
Companion changes:
docs/TASKS.md becomes a workstream rollup; workers operating inside W1 read docs/federation/TASKS.md as their primary task source
Session 15 entry appended to docs/scratchpads/mvp-20260312.md (existing scratchpad, active since 2026-03-13 — append-only per orchestrator protocol)
install-ux-v2 manifest + tasks + scratchpads moved to docs/archive/missions/install-ux-v2-20260405/ with status corrected to complete
Scratchpad session 15 entry visible at the end without disrupting prior session log
Generated with Claude Code
## Summary
Author the MVP rollup mission manifest at `docs/MISSION-MANIFEST.md`. Replaces the `install-ux-v2` manifest that previously occupied the slot — that sub-mission is archived as complete (IUV-M03 substantively shipped via PR #446 + releases 0.0.27 → 0.0.29).
**The new manifest treats MVP as a rollup:**
- Federation v1 declared as workstream W1 (planning-complete; 7 milestones; manifest at `docs/federation/MISSION-MANIFEST.md`; tracking issues #460–#466)
- Three-surface parity (webUI / TUI / CLI) encoded as cross-cutting requirement MVP-X1 so it cannot be silently dropped
- "Likely Additional Workstreams" pre-staged from PRD scope without committing execution capacity — scope creep is named and accommodated, not denied
- Phase 0–8 history (sessions 1–14, 2026-03-13 → 2026-03-15) preserved in the scratchpad as prior execution context
**Companion changes:**
- `docs/TASKS.md` becomes a workstream rollup; workers operating inside W1 read `docs/federation/TASKS.md` as their primary task source
- Session 15 entry appended to `docs/scratchpads/mvp-20260312.md` (existing scratchpad, active since 2026-03-13 — append-only per orchestrator protocol)
- `install-ux-v2` manifest + tasks + scratchpads moved to `docs/archive/missions/install-ux-v2-20260405/` with status corrected to complete
## Test plan
- [ ] Manifest renders correctly in Gitea
- [ ] Cross-references resolve (federation manifest, PRD, scratchpad, archived install-ux-v2)
- [ ] Scratchpad session 15 entry visible at the end without disrupting prior session log
Generated with Claude Code
Replace the install-ux-v2 manifest at docs/MISSION-MANIFEST.md with a
top-level MVP rollup that tracks workstream-level missions instead of
sub-mission scope. install-ux-v2 substantively shipped (IUV-M03 via
PR #446 + releases 0.0.27 → 0.0.29) and is archived under
docs/archive/missions/install-ux-v2-20260405/ with status corrected
to complete.
The new MVP manifest:
- Names federation v1 as workstream W1 (planning-complete, 7 milestones,
manifest at docs/federation/MISSION-MANIFEST.md, issues #460-#466)
- Encodes three-surface parity (webUI/TUI/CLI) as cross-cutting
requirement MVP-X1 so it cannot be silently dropped
- Pre-stages additional workstreams (PRD-derived candidates) without
committing execution capacity to them — scope creep is named and
accommodated, not denied
- Preserves Phase 0–8 history from sessions 1-14 in the scratchpad as
prior execution context, not as the active control plane
docs/TASKS.md becomes a rollup pointing at workstream task files;
workers operating inside W1 read docs/federation/TASKS.md as their
primary task source.
Session 15 entry appended to docs/scratchpads/mvp-20260312.md (the
existing scratchpad, active since 2026-03-13).
Co-Authored-By: Claude Opus 4.7 <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Author the MVP rollup mission manifest at
docs/MISSION-MANIFEST.md. Replaces theinstall-ux-v2manifest that previously occupied the slot — that sub-mission is archived as complete (IUV-M03 substantively shipped via PR #446 + releases 0.0.27 → 0.0.29).The new manifest treats MVP as a rollup:
docs/federation/MISSION-MANIFEST.md; tracking issues #460–#466)Companion changes:
docs/TASKS.mdbecomes a workstream rollup; workers operating inside W1 readdocs/federation/TASKS.mdas their primary task sourcedocs/scratchpads/mvp-20260312.md(existing scratchpad, active since 2026-03-13 — append-only per orchestrator protocol)install-ux-v2manifest + tasks + scratchpads moved todocs/archive/missions/install-ux-v2-20260405/with status corrected to completeTest plan
Generated with Claude Code