[harlan-zw]

❓ Type of change

• 📖 Documentation

📚 Description

Follow-up to #29. The triage ledger and the 2026-08-16 check-in both still said
"undeployed" for three fixes that have since shipped and been verified in
production, and the dead-letter row's exit conditions are now met.

The evidence, all read back from production after the deploy rather than inferred
from a green pipeline:

Check	Before	After
Repositories parked at next_offset = 200	6	0
Registry batch failures	6 and 6	0 and 0
Dead-letter rows	596, climbing ~12/hour	598, frozen

github/awesome-copilot settled at 430 indexed skills and posthog/posthog at
276, both past the wall that had held since 2026-08-12. The two largest reached
offsets the old ceiling made unreachable, sickn33 at 2,250 of 6,341 and
jeremylongshore at 1,500 of 5,598, then completed and released their progress
rows.

Only the dead-letter row is marked resolved. The other three rows are marked
deployed with their exit conditions still open, because the staleness fix, the
rejected-jobs split, and the skipped-run classifier all need the next nightly
report or the next check-in archive to actually demonstrate anything. Marking
those resolved now would be recording an intention as a result.

The check-in also gains a Resolution section covering the two defects that
surfaced during delivery and that the check-in itself had missed: a typecheck
failure my local run swallowed through a pipe, and the hookTimeout flake.

🤖 AI disclosure: Harlan Agent Kit modified this description. My AI open-source policy.