🐛🧑‍💻 - Dogfooding progress cards remain active after native issue closure #482

Is there an existing issue for this?

• I have searched the existing issues.

Which actions are affected?

Issue, Pull Request, Commits

Which platforms are affected?

macOS, Windows, Linux

Description

After native merge of PR #479 into develop, issue #478 is closed as completed, retains branched, has 100% and Project Done. Its owned branch-sync card was correctly retired in place. However, its canonical progress card still displays "Progress: 96% — in progress", an active "Current status" and a next action to verify work. The existing card is #478 (comment).

Expected: verified native closure marks the existing owned progress card as historical, keeps its identity/link and last estimate, and makes closure/current next action unambiguous. Closing an issue must not invent an implementation assessment, CI evidence or a new model-derived percentage. Completed, not-planned/duplicate and unavailable/race outcomes must be accurate. Reopening permits a fresh normal progress assessment. Foreign/malformed cards and historical timeline notifications must remain untouched.

Reproducing the issue

1. Run normal progress assessment for admitted work, producing an owned schema-1 progress/work card.
2. Merge its linked PR or close the issue manually while the last model estimate is below 100%.
3. Compare native closed state, current labels/project and the card's active wording.
4. Issue 🐛🧑‍💻 - Dogfooding retire synchronization advice for terminal work #478 currently reproduces the mismatch after PR [#478] 🐛 - Dogfooding retire synchronization advice for terminal work #479, without changing the source or running an agent.

copilot Version

master / develop 94ef181, package 3.3.1

Relevant Log Output

Native closure: 2026-10-13T10:28:46Z; progress card last update: 2026-10-13T10:09:13Z; source head 968580b.

Additional context and comments

Dogfooding acceptance: same card/link, native closure with fresh ownership/body/issue fences, bounded read/update-only cleanup, no model/branch/label/configuration effects, quiet replay, and fresh presentation after reopening. Document the distinction between native closure and historical estimated implementation progress. Windows coverage remains ordinary Node/workflow coverage; Codex on Windows service runners stays unsupported.