Residual spec coverage from #440: 1 undelivered integration point(s)

Residual spec coverage (auto-filed by the spec-coverage gate #9914)

The workflow for #440 (closed) landed and merged its primary mechanism, but the spec-coverage gate (#8930) flagged a partial delivery: 1/2 of the integration points named in the parent were addressed and 1/1 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: #440 (closed) Landing workflow: 440-haf-system-suite-test-blocks-r-s5e0d19f2-v1 Scored change: e6b84f31930c804c7ba144a45ff8adba2b40e224..a19b72b81bfeab50ab60abb7b5f609e19bda4cd6 Landing merge: 842ae01c265e59c64837fc9a83075c17fc101b55 (where the scored change was integrated; it need not carry the scored diff)

Undelivered integration points

  • .aidev/known_failures.txt — declared as: .aidev/known_failures.txt: only with a stated cause

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: #440 (closed)