Closeout records gap-reporting PR #16 as statement-enforcement delivery instead of #19 #33

Static provenance defect in unmerged PR #32

Reviewed head: 1b1ab50181de8e0dcde7841348af867d43653a11 (still open when rechecked).
Affected record: pm-ado-5w3m.toon, plus its appended close history and close_reason.

The canonical goal is to independently measure and enforce the statement-coverage threshold, preserving the other coverage dimensions and rejecting a meaningful below-threshold fixture.

Reproduction by inspecting the proposed tracker change

1. Read the record at the reviewed head. It sets completed_at to 2026-10-04T12:58:08Z and resolution/actual_result/close_reason to PR #16, merge fc8289f54e3e6c0e7da78588c88e05faf531770d, head e71531111b916e69ad0098f483fd30e658b211cc.
2. Inspect Certify pm-ado on PM CLI 2026.10.4 and consolidate pending dependency updates #16's final description and patch. That certification created/documented the statement-coverage gap and explicitly left independent statement enforcement open; its green checks did not deliver this goal.
3. Inspect PR #19. It adds independent statement instrumentation and enforcement, failed-threshold fixtures, and receipts. It merged at 2026-10-08T01:19:51Z, merge f297a71431debfe2e00adb8dd1b02874e6dadfe2, head 119b225ec6f84bf8c53ee6c953dba0980ddc6f1a. The item's retained October 7 comments also describe that later implementation.

Expected versus actual

Expected: closeout uses the PR that satisfies the current item's acceptance criteria and records that delivery's verified timestamp, revision and check evidence.
Actual: it records the earlier gap-reporting PR as delivery, dating completion four days before the actual merge and attaching unrelated head-check evidence.

The implementation does exist in #19; this report does not claim statement enforcement is currently missing. The defect corrupts durable delivery provenance and completion chronology in the proposed closeout.

Regression acceptance

• Select Enforce independently measured statement coverage #19's delivery evidence for this item, after verifying its checks, rather than treating Certify pm-ado on PM CLI 2026.10.4 and consolidate pending dependency updates #16's mention of the item as delivery
• Reconcile completed_at, resolution, actual_result, close_reason and the corresponding proposed close-history evidence consistently
• Add a closeout regression where an earlier merged PR introduces/describes an unresolved issue and a later merged PR satisfies it; reject the earlier PR as delivery
• Preserve prior historical evidence and distinguish offline implementation acceptance from any still-pending live Azure acceptance

Scope: static comparison of immutable tracker and delivery PR patches, not a rerun of implementation tests or live Azure services. All-status issues/PRs, current PM records and #32 discussion were checked before filing. The existing September changelog-heading thread is a separate defect.