Prepare the held Release Please 1.1.0 approval PR

[ben-ranford]

Outcome

Prepare the final Release Please PR for 1.1.0 after the v1.1 implementation train lands, and leave that release PR open and unarmed for the maintainer to approve. This issue does not authorize a tag or publication.

Evidence and bounded scope

The current manifest records 1.0.0-rc.2; Release Please is configured for RCs. The pinned action supports preparing PRs independently of publication through the existing skip-github-release: true input. Upstream Release Please supports a one-shot Release-As: 1.1.0 commit footer. See version strategy and manifest guidance.

Acceptance checks

• Land a separate preparation PR last in the implementation train: remove RC-only versioning options and preserve the root Go package, adapter exclusion, pinned action and no-publication action input.
• Preserve the actual released manifest value in the preparation PR; let Release Please update it in the final release PR.
• Update the RC-only configuration test and annotated version documentation so both the real RC baseline and held stable release target are represented truthfully. Preserve GA evidence requirements and the tag workflow.
• Preserve Release-As: 1.1.0 in the final preparation squash commit body; verify the actual merged commit.
• Verify Release Please opens or updates exactly one 1.1.0 release PR containing the expected manifest, changelog and annotated documentation changes.
• Validate all ordinary PR checks and review gates on that final head; leave the release PR OPEN, with no queue label or auto-merge.
• Verify no v1.1.0 tag, GitHub Release or release assets were created. Report existing GA/Lopper evidence blockers separately from ordinary PR CI.

Dependencies and boundaries

Depends on the completed v1.1 implementation train in #38, including #77. Existing #2/#3 and immutable published Lopper parity/rollback evidence remain stable-release prerequisites. No substitute stable 1.0.0 release, root dependency/Go-floor changes, adapter graduation, visibility change or Lopper/Homebrew work. The maintainer retains approval of the final Release Please PR.

Scope firewall

A review item belongs here only if it directly prevents these acceptance criteria and is an incremental correction in the stated preparation/configuration surface. Do not weaken a GA gate to make ordinary PR CI green or absorb unrelated release infrastructure work.