Residual spec coverage from #1506: 1 undelivered integration point(s)
Residual spec coverage (auto-filed by the spec-coverage gate #9914)
The workflow for #1506 (closed) landed and merged its primary mechanism, but the spec-coverage gate (#8930) flagged a partial delivery: 2/3 of the integration points named in the parent were addressed and 3/3 of its acceptance criteria were delivered. The parent has been closed per the issue-lifecycle policy; this follow-on tracks the remaining scope so it is not silently dropped.
Parent issue: #1506 (closed)
Landing workflow: 1506-matrix-chat-warm-up-creates-a-s4dd8bf73-v1
Scored change: 4bbf61ea11910cf43daa259bbbbcaed1327c4dd7..634cfead22d4dce8d1995374e5618c6855a408eb
Landing merge: 82ace6625446caad6e2aa60724bffdeae231f860 (where the scored change was integrated; it need not carry the scored diff)
Undelivered integration points
apps/blog/components/hooks/use-matrix-chat-drawer.ts— declared as:apps/blog/components/hooks/use-matrix-chat-drawer.ts- no account creation on warm-up
Each was named in the parent's spec but has no corresponding diff surface in the landed change.
For the reviewer: verify first
Filed todo for this project's tech lead to triage before anything is dispatched. The gate does not distinguish deliberately-deferred from missed, and most residual-coverage issues are false positives: check each item against the current integration branch (not only the landed diff), the parent issue and its discussion. Close this issue naming where each item is delivered (file:line or commit) or why it does not apply; rewrite it to the items that are really missing and still wanted. Record the verdict with aidev loop residual <iid>.
Refs #9050, #8930, #15599.
Part-Of: #1506 (closed)