Files
summercms/.planning/phases/10-admin-vue-spa/deferred-items.md
Jakub Zych bbceeb957f docs(10.1-04): record the Phase 10.1 security review and validation map
- 10.1-SECURITY-REVIEW.md: T-10.1-01 to T-10.1-22 and T-10.1-SC with
  mitigation, test or gate stage, observed result and 23 removal checks
- 10.1-VALIDATION.md: every plan task mapped to its command, all green
  under check-phase10.1.sh --all; nyquist_compliant and wave 0 complete
- Phase 10 deferred item for the parity failures marked resolved
2026-09-29 03:13:18 +02:00

23 lines
1.2 KiB
Markdown

# Phase 10 deferred items
Out-of-scope issues found while executing Phase 10 plans. They are not caused by
Phase 10 changes and are not fixed here.
## From 10-01
- **fonoteka.go `parity` package fails two tests before Phase 10.**
`TestMigrateSeedsCanonicalGenres` expects no `summer_migrations_summercms_cabana`
history table, and `TestSchemaMatchesPHPSnapshot` reports `backend_users`,
`backend_user_roles` and `backend_jwt_blacklist` as unexpected extra tables.
All four come from the Phase 9 cabana migrations. Reproduced on untouched copies
of both repositories at the pre-10-01 commits (summercms.go `8c3e131`,
fonoteka.go `feaca6b`), so `go test ./...` in fonoteka.go was already red in
this package. Fix belongs to a Phase 9 follow-up: add the cabana history table
and the three backend tables to the parity allow-lists with a reason.
status: resolved
**Resolved:** both tests pass since fonoteka.go `21c0f12` (fix(09): update parity
expectations for the backend admin schema); Plan 10.1-04 removed them from the
`check-phase10.sh` allow-list (`9aeb0e1`), and `check-phase10.1.sh` allow-lists nothing.
- **`gofmt -l` lists `internal/build/registry.go`** in summercms.go. Pre-existing,
untouched by Phase 10.