docs(08-03): record parity test fix and fetchguard flake in deferred items

.planning/phases/08-oauth2-1-authorization-server/deferred-items.md

@@ -41,3 +41,22 @@ intermittently fails with "server wrote 71680 bytes, client appears to have
 buffered unbounded body" under `go test ./...` but passes reliably when run
 in isolation (`go test ./fetchguard -run TestFetchTooLargeIsStreaming
 -count=3`). `fetchguard` is untouched by this plan. Not fixed here.
+
+**Resolution (orchestrator, after 08-03):** fixed in `fonoteka.go` commit
+`f9b23e1` (`fix(08-03): update parity migration tests for the oauth schema
+correction head`). Five parity tests (`TestMigrateSeedsCanonicalGenres`,
+`TestAlbumSliceMigrationsUpDown`, `TestSecretsSliceMigrationsUpDown`,
+`TestRemainingMigrationsUpDown`, `TestRollbackIsolatesFonotekaFullSchema`)
+now expect `202609230019_oauth_schema_correction` as the head and walk one
+extra table-less rollback step. `go test ./...` in the `fonoteka.go` root
+module is green again.
+
+## Pre-existing flake: `fetchguard.TestFetchTooLargeIsStreaming` (summercms.go)
+
+**Found during:** post-wave test gates after 08-03.
+
+**Symptom:** fails intermittently only under a full parallel `go test ./...`
+run; passes on every isolated run (`-count=5`) and every package-level run
+(`-count=3`). Last touched in Phase 6 (`e50e2dd`); no Phase 8 plan modifies
+`fetchguard`. Timing-sensitive streaming assertion under load. Not a Phase 8
+regression; left for a later hardening pass.