chore(openspec): archive inspect-provider-version-fallback

[Drswith]

Summary

Archive completed OpenSpec change inspect-provider-version-fallback after its implementation PR (#738) merged, syncing the accepted agent-version-probing deltas into openspec/specs/.

Living specs now require:

• list / inspect / info / resolve / doctor to display the provider-reported version when PATH is present and the live --version probe yields none
• installed / inPath to stay on PATH presence, so a provider-only version does not mark an agent installed
• failed probe stdout/stderr still cannot become version evidence unless a provider observation supplies an installed version

Product-path KEEP hangs on existing src/compatibility/agent-inspection.ts so classify still sets run_test_matrix=true (protect-main requires test (macos-latest)). It does not restore src/lifecycle/. No YAML / SDK / release-core.yml / protect-main edits.

Linked Artifacts

• Issue: [Bug]: Agent version shows "unknown" when --version probe fails even though the provider reports the exact installed version #734
• OpenSpec: inspect-provider-version-fallback
• Discussion: follow-on to implementation PR fix: show provider version when agent --version probe fails #738

Validation

• bun run openspec:validate
• bun run memory:check
• bun run lint
• bun run format:check
• bun run typecheck

bun run test is not applicable for behavior: the only src/ edit is a keep comment on existing src/compatibility/agent-inspection.ts with no runtime effect. Local suite on this head: 2191 passed, 5 skipped. CI on 0b4f0d7 completed green, including test (macos-latest), test (ubuntu-latest), and test (windows-latest).

Release Intent

• Release: not applicable - OpenSpec archive closure only

Release Summary

• Not applicable - OpenSpec archive closure does not produce a release entry. The user-facing provider-version display fix already shipped in fix: show provider version when agent --version probe fails #738.

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 -- inspect-provider-version-fallback --apply-specs. fix: show provider version when agent --version probe fails #738 did not apply living specs, so this archive used --apply-specs rather than --skip-specs.
• The generated openspec/changes/archive/2026-09-08-inspect-provider-version-fallback/ directory was removed rather than committed, matching chore(openspec): archive fix-upgrade-unresolved-latest-crash #707, chore(openspec): archive cli-core-upgrade-p6 #712, chore(openspec): archive cursor-version-probe-targeting #720, chore(openspec): archive lifecycle-engines-core-internal-l3 #726, chore(openspec): archive lifecycle-barrel-core-internal-l4 #728, and chore(openspec): archive windows-bun-residual-shim-lifecycle #737. Git history remains the archaeology.
• Product-path keep comment hangs on still-existing src/compatibility/agent-inspection.ts so classify sets run_test_matrix=true. It does not restore src/lifecycle/.
• Did not touch YAML, release-core.yml, protect-main, SDK surfaces, --json, aliases, exit codes, state v2, or receipts.
• Did not start Track agent-catalog support backlog #134.
• Did not touch active or shelved changes release-one-line-delivery, release-pr-skip-human-heuristics, restore-managed-update-and-resume-releases, or windows-ci-advisory-merge-gate.
• Archive closure still waits on merge of this PR.