Housekeeping: CHG-0038 merged via #91 but never archived (still in .specsync/changes/ as "implementing")

[0xLeif]

Noticed during a peer-review pass on main @ 6a40258.

Per AGENTS.md rule 6, after an implementing PR merges its SpecSync change should be archived (specsync change archive <id> from a clean main-based checkout, small housekeeping PR), and accepted changes should not pile up in .specsync/changes/.

The archive routine covered CHG-0037 (#81), CHG-0039 (#94), and CHG-0040 (#96), but CHG-0038 (the change landed by #91) was skipped:

• .specsync/changes/CHG-0038-harden-adversarial-findings-... is still present on main
• its state.json still says "state": "implementing" (never even transitioned to accepted)
• specsync change list reports "No active SDD changes" (5.2.0 squash-merge evidence), so the archive preflight should pass; the change may need the acceptance step recorded first given the stale state field

Suggested fix: run the acceptance/archive flow for CHG-0038 from a clean main-based checkout and push it as a small housekeeping PR, same as the #94/#96 routine.

[0xLeif]

Codex claiming this ticket. I’ll handle the CHG-0038 acceptance/archive housekeeping from a clean main-based branch, verify the archive preflight, and open a small PR.

[0xLeif]

Codex verification completed successfully on main (build, 63 tests, smoke, plugin validation). The pinned SpecSync 5.2.0 lifecycle then blocked the stale-ledger closure: change accept correctly refused to reapply already-canonical REQ-aps-cli-023 and left the change in verifying; change archive requires accepted. I reverted the transient evidence, left the checkout clean, and released the claim. This needs a SpecSync-supported audited stale-acceptance/archive path or maintainer guidance before another agent retries.

[0xLeif]

Codex claiming this ticket. I’m auditing CHG-0038 from clean origin/main in branch leif/issue-100-chg0038; I’ll use the pinned SpecSync 5.2.0 lifecycle and release the claim if the canonical evidence path remains blocked.

[0xLeif]

Codex releasing the agent:codex claim: no safe housekeeping PR is possible with pinned SpecSync 5.2.0.

Reproducible audit from clean origin/main (644ea11) in isolated branch leif/issue-100-chg0038:

• specsync --version -> 5.2.0; specsync change status CHG-0038-... -> implementing, next verify.
• fledge lanes run verify passed all 5 steps: build, 65 tests, parallel tests, smoke, and plugin validation.
• specsync change verify CHG-0038-... passed and moved the change to verifying, next accept.
• specsync change accept CHG-0038-... --actor "Codex" --note "Merged implementation from PR #91; verified on origin/main." rejected with the exact error: cannot add existing block REQ-aps-cli-023.
• specsync change archive --help documents archiving an accepted change; after the rejection the change remained non-accepted. The transient verification evidence was discarded, leaving the isolated worktree clean and the ledger back at implementing.

The 5.2.0 help exposes no supported stale-implementing transition or accept-without-reapplying-existing-deltas path. I did not hand-edit state or force archive. No PR opened; maintainer/SpecSync guidance is required for an audited stale acceptance path.