# Carry-Forward Historical Scan

Date: 2026-05-16

Source Chunk: `chunk-000168-carry-forward-historical-scan-seeding`

## Scope

Scanned relevant completed chunks, active/completed work packages, and reports
for future-relevant unresolved findings in sections such as Carry Forward,
Pending Enforcement, Bad, Ugly, Lessons Learned, Root Cause, Drift Mechanism,
Policy Enforcement, Handoff, Next, Details, and QA Review.

The scan was conservative. It did not promote one-off debugging noise,
resolved-in-same-chunk findings, or items already covered by existing CFDs.

## Promoted Items

| ID | Type | Blocking | Source | Reason |
| --- | --- | --- | --- | --- |
| `cfd-0006` | compatibility | no | chunks 000160, 000163, 000167 | Runtime Action Panel is user-facing, while AdminRuntimeHealth and `/admin/health` remain compatibility names. |
| `cfd-0007` | warning | no | chunks 000152, 000159 | Backend e2e repeatedly requires `TEST_DATABASE_URL` or a test-named database. |
| `cfd-0008` | warning | no | chunks 000153, 000154, 000158, 000159, 000160 | Frontend initial bundle and Admin Health/Runtime Action Panel SCSS warning budgets recur. |
| `cfd-0009` | observation | no | chunks 000070, 000153, 000159 | UI browser review depends on pinned Playwright/Chromium guidance and managed server assumptions. |
| `cfd-0010` | follow_up | no | chunks 000141, 000142, 000143, 000167 | Runtime boundedness can degrade again after normal close/commit event bursts. |

## Duplicates

- Legacy Telegram TSV projection is already tracked by `cfd-0004`.
- Compatibility-only manual lifecycle mutation paths are already tracked by
  `cfd-0005`.
- Historical close_commit failed-then-success/reconciliation behavior is
  already tracked by `cfd-0001`.

## Ignored Or Resolved

- Socket.IO/live transport deferral was not promoted because the live transport
  package later completed through chunks 000146-000150.
- Earlier Playwright "not installed" findings from reports 000006 and 000008
  were superseded by later Docker/pinned Playwright guidance and represented by
  `cfd-0009`.
- UI foundation and auth bootstrap historical browser-smoke desires were not
  promoted separately because they are covered by the more current UI review
  and Playwright guidance.
- Broad filesystem taxonomy concerns were not promoted because this scan did
  not find a current actionable repeated finding that should block or direct
  the next package.

## Ambiguous Items For Operator Review

- Prisma migration-file convention gap appeared in chunk 000159. It is not
  seeded because this package did not establish whether it is repeated enough
  or still architecturally relevant. Revisit during future Prisma/database work.
- A deeper Runtime-originated event bridge may still be useful if
  backend-observed Socket.IO invalidation proves insufficient, but the current
  Socket.IO package is implemented and no fresh evidence shows missed Runtime
  Health updates. Revisit only if live invalidation misses backend-external
  Runtime changes.

## Current Carry-Forward Summary

After seeding, the registry contains ten items:

- Open blocking: 0.
- Open non-blocking: 8.
- Open by type: advisory 1, compatibility 1, pending_enforcement 2,
  warning 2, observation 1, follow_up 1.

Blocking enforcement remains intact. Non-blocking items are visible for humans
and machine-readable Runtime projections but do not block close/commit.