fix: finalize Release Please patch state

[tensornull]

What changed

• Removed the one-cycle last-release-sha recovery anchor after the successful 0.1.1 preparation run.
• Marked the 0.1.1 candidate as approved for the normal reviewed npm publication path without claiming it is published.
• Documented the fresh Release Please refresh, exact-parent, CI, and human-review requirements.
• Updated the workflow contract regression to require the durable anchor-free configuration.

Why

The repair anchor was needed only to create and validate the first action-owned 0.1.1 PR. Keeping it on the eventual release commit would fail final validation, while editing the action-owned branch would violate its generated four-file contract. This normal fix commit moves durable final state to main so a fresh Release Please dispatch can regenerate the same release PR from current main.

Verification

• npm ci
• npm run verify:offline
• npm run verify through package, examples, fixtures, minimum/locked/latest OpenAI, and actionlint; the pre-commit run stopped only at the clean-worktree-only self-contained gate
• npm run check:self-contained after commit
• node scripts/validate-release.mjs
• focused release validation: 279 tests
• git diff --check