golem15/summercms
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(roadmap): phase 2 depends on phase 1 command kernel

Browse Source
This commit is contained in:
Jakub Zych
2026-09-16 12:53:59 +02:00
parent fe52186191
commit 22ff001f7d
2 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
.planning/ROADMAP.md
View File

@@ -14,7 +14,7 @@ v1 ports the Płytarium (fonoteka) headless PHP backend to a single Go binary wi
Decimal phases appear between their surrounding integers in numeric order.
- [ ] **Phase 1: Framework kernel foundation** - Config, plugin registry, event bus, container and CLI skeleton boot the `summer` binary
- [ ] **Phase 2: API parity harness bootstrap** - Fixture recorder + replay-and-diff harness against the live PHP backend, day-one workstream
- [ ] **Phase 2: API parity harness bootstrap** - Fixture recorder + replay-and-diff harness against the live PHP backend, built on the Phase 1 command kernel
- [ ] **Phase 3: First vertical slice — genres end to end** - `GET /_fonoteka/api/v1/genres` passes the parity diff through every layer
- [ ] **Phase 4: CLI scaffolding, i18n and mail** - Scaffolding commands, translated/pluralized strings, mail templates
- [ ] **Phase 5: Data layer full fidelity** - All 25 models and 27 migrations with fillable/hidden/cast/soft-delete discipline
@@ -67,9 +67,9 @@ Plans:
### Phase 2: API parity harness bootstrap
**Goal**: A fixture recorder captures request/response pairs from the running PHP backend — including real Nuxt and MCP flows — and a replay-and-diff harness with a normalizer for nondeterministic fields can run against any HTTP backend. This is a day-one workstream with no dependency on framework progress, since it only needs a running PHP backend to record against.
**Goal**: A fixture recorder captures request/response pairs from the running PHP backend — including real Nuxt and MCP flows — and a replay-and-diff harness with a normalizer for nondeterministic fields can run against any HTTP backend. The recorder and replayer are `summer parity:*` commands on the Phase 1 command kernel (bonfire); recording itself only needs a running PHP backend, but the tooling waits for Phase 1.
**Mode:** mvp
**Depends on**: Nothing (parallel with Phase 1)
**Depends on**: Phase 1
**Repos:** summercms.go, fonoteka.go
**Requirements**: QA-01, QA-02, QA-03
**Success Criteria** (what must be TRUE):
@@ -303,7 +303,7 @@ Plans:
**Execution Order:**
Phases execute in numeric order: 1 → 2 → 3 → 4 → 5 → 6 → 7 → 8 → 9 → 10 → 11 → 12 → 13 → 14 → 15
(Phase 2 has no dependency on Phase 1 and may be executed in parallel with it.)
(Phase 2 depends on Phase 1's command kernel; the two are no longer parallel.)
| Phase | Plans Complete | Status | Completed |
|-------|----------------|--------|-----------|

6
.planning/STATE.md
View File

@@ -4,7 +4,7 @@ milestone: v1.0
milestone_name: milestone
status: executing
stopped_at: Phase 2 context gathered
last_updated: "2026-09-16T10:47:33.102Z"
last_updated: "2026-09-16T10:53:48.889Z"
last_activity: 2026-09-16 -- Phase 01 execution started
progress:
total_phases: 15
@@ -55,6 +55,10 @@ Progress: [░░░░░░░░░░] 0%
## Accumulated Context
### Roadmap Evolution
- Phase 2 edited: edited fields: depends_on (Phase 1), goal (summer parity:* on bonfire, no longer a parallel workstream)
### Decisions
Decisions are logged in PROJECT.md Key Decisions table.