chore(openspec): archive cli-core-upgrade-p6

[Drswith]

Summary

Archive completed OpenSpec change cli-core-upgrade-p6 after its implementation PR (#711, merge 285e5df) landed on main. Living specs already carry the accepted self-upgrade, runtime-boundaries, compatibility-contract, and product-readme deltas from that merge, so this PR only removes the completed change folder from the working tree.

Also adds a one-line keep comment under src/lifecycle/ so classify sets run_test_matrix=true and test (macos-latest) actually runs (protect-main requires it; pure openspec PRs would otherwise skip macOS).

Linked Artifacts

• OpenSpec: cli-core-upgrade-p6
• Issue: refactor(upgrade): route plan/check/apply through in-repo Core (P6) #711

Validation

• bun run openspec:validate
• bun run memory:check
• bun run lint
• bun run format:check
• bun run typecheck
• bun run test (if behavior changed)

bun run test is not applicable for behavior: the only src/ edit is a one-line keep comment with no runtime effect. Full CI matrix (including macOS) is expected after this push.

Release Intent

• Release: not applicable - OpenSpec archive closure only

Release Summary

• Not applicable - OpenSpec archive closure does not produce a release entry. P6 changelog framing is already covered by the refactor(upgrade): route plan/check/apply through in-repo Core (P6) #711 commit override.

Docs Updated

• openspec/...

Scope Check

• I did not add a new ad hoc root-level Markdown file.
• I updated the relevant issue, ADR, spec, runbook, or captured the missing doc work as follow-up.
• I did not silently expand project scope without recording it explicitly.

Closure Check

• Working tree was clean before archive closure started.
• Branch was pushed and this PR is the active delivery artifact.
• OpenSpec change is already archived or queued for agent-driven archive closure.
• Release is not applicable, delegated to release automation, or verified.

Notes

• Generated by bun run openspec:archive-closure -- cli-core-upgrade-p6. Spec deltas were already synced into openspec/specs/ by refactor(upgrade): route plan/check/apply through in-repo Core (P6) #711, so this run used --skip-specs. The generated openspec/changes/archive/2026-09-06-cli-core-upgrade-p6/ directory was removed rather than committed, matching docs(openspec): archive the stop-advisory-ci-schedules change #682, chore(openspec): archive fix-upgrade-unresolved-latest-crash #707, and chore(openspec): drop working-tree archive history #708.
• Product-path keep comment in src/lifecycle/uninstall-postcondition.ts is only to satisfy protect-main's required test (macos-latest) without changing protect-main or workflow YAML.
• No YAML. No SDK. No CLI behavior changes. Shelved OpenSpec changes (release-one-line-delivery, release-pr-skip-human-heuristics, windows-ci-advisory-merge-gate) are untouched.

  

[Drswith]

Duplicate of #712 (same archive scope). Keeping #712 as the review target.