chore: commit remaining worktree changes

scripts/test-no-deployment-coupling-scope.sh

@@ -14,8 +14,6 @@ new_fixture() {
     "$fixture/repository/deploy/workspaces" \
     "$fixture/repository/docker/smoke" \
     "$fixture/repository/docs/install" \
-    "$fixture/repository/docs/superpowers/specs" \
-    "$fixture/repository/docs/superpowers/plans" \
     "$fixture/repository/frontend" \
     "$fixture/repository/scripts"
 
@@ -31,11 +29,7 @@ new_fixture() {
   printf '%s\n' '# qdrant backup helper' >"$fixture/repository/scripts/vector-backup.sh"
   printf '%s\n' '# qdrant restore helper' >"$fixture/repository/scripts/vector-restore.sh"
 
-  # These are the three intentionally allowed categories from the Task 10 boundary.
-  printf '%s\n' 'historical omics_portal and Chirone record' \
-    >"$fixture/repository/docs/superpowers/plans/legacy.md"
-  printf '%s\n' 'historical pgvector rollout note' \
-    >"$fixture/repository/docs/superpowers/specs/history.md"
+  # These two migration fixtures remain intentionally outside the active runtime surface.
   printf '%s\n' 'id: generic' >"$fixture/repository/deploy/workspaces/psd.yaml.example"
   printf '%s\n' '# migrate PSD sessions from /home/chirone' \
     >"$fixture/repository/docker/session-migrate.sh"