bbceeb957f
- 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
1.2 KiB
1.2 KiB
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
paritypackage fails two tests before Phase 10.TestMigrateSeedsCanonicalGenresexpects nosummer_migrations_summercms_cabanahistory table, andTestSchemaMatchesPHPSnapshotreportsbackend_users,backend_user_rolesandbackend_jwt_blacklistas 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.go8c3e131, fonoteka.gofeaca6b), sogo 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.go21c0f12(fix(09): update parity expectations for the backend admin schema); Plan 10.1-04 removed them from thecheck-phase10.shallow-list (9aeb0e1), andcheck-phase10.1.shallow-lists nothing. gofmt -llistsinternal/build/registry.goin summercms.go. Pre-existing, untouched by Phase 10.