PRD-28: the 1.0 release

[DurthVadr]

Version 1.0.0, the 0.2.0 compatibility layer removed, the 1.0.0 release note, and the 1.0.0 release evidence from a live smoke pass on this tree (60f75ce, evidence commit on top).

Not taggable yet, by design. docs/compatibility.md keeps one PENDING_RELEASE_EVIDENCE marker, on the GitHub Copilot CLI row: Copilot CLI 1.0.83 on this machine answers every prompt with Error: Access denied by policy settings before any hook runs (real and isolated COPILOT_HOME alike), so PRD-28 R2 cannot be walked. release.yml refuses v1.0.0 until that row is filled. Everything else is done.

R8: removed

src/shim_guard; the shim-guard-hook script (module-name = "shim_cli"); SHIM_GUARD_CONFIG (→ SHIM_CONFIG), SHIM_GUARD_STATE_DIR (→ XDG_STATE_HOME), SHIM_GUARD_SESSION_DIR (→ TMPDIR) — the last two had no SHIM_* successor, so none was invented; both shim-guard marketplace entries; launcher case 2; the old-script checks in ci.yml and release.yml. Kept: settings, ledger and Copilot-file migration; shim install rewriting the 0.2.0 line. Doctor on a 0.2.0 hook: FAIL hook installed in the 0.2.0 shape, which 1.0 does not run; run shim install <client>., coverage 0 of N, exit 2.

Smoke pass (every screen quoted in docs/compatibility.md § 1.0.0)

Journey	Result
J1 Claude Code 2.1.263, marketplace plugin, only /usr/bin/python3 3.9.6	IBAN prompt reported; JSON epoch intact; .env masked and the model says the placeholder is not in the file; summary with the bare-numbers line; doctor no version WARN
J2 package on 3.9-first PATH	--python 3.12 installed 1.0.0 with shim and shim-hook only; install previews; card prompt reported, safe prompt silent
J3 upgrade from 0.2.0	No module named 'shim_guard' on the old line; doctor FAIL with the command; shim install fixes all three; doctor clean
J6 shim watch on a subscription	spend ... API-key equivalent, this session is on a subscription, not a bill; spend_basis: subscription
J7 Codex 0.151.0 marketplace plugin	Blocked under enforce, Completed under observe; shim watch -- codex refused with its sentence
J8	0 % / 7 % / 0 % / 0 of 8; corrupted settings fail closed with the command; no Python fails open with a sentence
J9	revert keeps unrelated hooks and keys; uninstall leaves only settings files
R2 Copilot	blocked by account policy (above)

Found by the smoke pass

• Shipped as 0.3.3 (release: 0.3.3, the Codex plugin hook inspects prompts again #27): the Codex plugin hook never inspected a prompt in 0.3.1–0.3.2 (Codex sets CLAUDE_PLUGIN_ROOT too); a custom pattern added on a 0.2.0-migrated config never applied.
• In this PR: shim ledger show told a person whose ledger was on to turn it on; doctor printed a second, wrong FAIL for an unparseable settings file.

Requirements

R1 version (naming contract) · R4 evidence section, marker gate · R5 README warning without "alpha" (test_the_readme_does_not_call_1_0_alpha), test count and hook figures re-measured · R6 docs/releases/1.0.0.md five sections + Verified; PRD-13/16/17/20 named by feature as 1.1 candidates · R7 smoke pass above · R8 test_no_shim_guard_module_script_or_variable_remains, test_doctor_fails_a_020_hook_that_1_0_does_not_run, test_no_shim_guard_plugin_remains, migration tests.

To release

1. Enable Copilot CLI for the account; walk R2 (shim install copilot, safe prompt, synthetic email repeated verbatim, forced hook error fails open); move TESTED_COPILOT_VERSION and the row's tested: phrase together; replace the marker with the quoted screens.
2. Merge; git tag -a v1.0.0 -m "shim v1.0.0" && git push origin v1.0.0; approve release and pypi.

Deviations to discuss

• PyPI classifier 3 - Alpha → 5 - Production/Stable.
• Codex trust in the smoke pass was granted per invocation (--dangerously-bypass-hook-trust), not persisted through the UI.
• Not merged ahead of the Copilot row, although PRD-28 R7 allows main to carry 1.0.0 with the marker: the Claude marketplace installs from main, so merging would show directory users a 1.0.0 plugin while PyPI says 0.3.3.

🤖 Generated with Claude Code