docs: label first-party cutover and validation ledgers as v2.0.0-era records or refresh them #554

Goal

Prevent readers from taking the v2.0.0 GA-era ledgers as the current state of the ecosystem.

Background

Several documents and data files describe the v2.0.0 cutover and have not been updated for v2.1.0 or the surrounding releases:

• docs/first-party-cutover.md:43-44 ("Current state") and first-party-cutover.yaml:18,30 cite Base v1.8.0 and the base-v1.8.0 bottle release. Base v1.9.0 was published 2026-09-08.
• docs/consumer-validation-status.md:3 says "Last validated: 2026-09-02", before the v2.1.0 release (2026-09-08), and its matrix records only v2.0.0 pins. The demo repository's scheduled canary now also covers v2.1.0.
• integrations/compatibility.yaml:2 (framework_release_line: v2.0.0) and examples/reference-apps/release-evidence.yaml:2,8 (release_line/candidate.ref: v2.0.0) name the GA line without saying they are fixed to the GA baseline.
• docs/discovery/awesome-bash.md:8,28 still gates on "the v2.0.0 release" and has every checklist item unchecked even though the v2.0.0 asset has existed since 2026-08-15.
• integrations/package-managers/registry.yaml and docs/integrations.md keep bpkg/Basher/Basalt as planned-after-v2-ga; GA has passed, so the status should say which remaining gate (maintained update path) is open.

Some of these are intentionally historical and are checked by scripts/first-party-cutover check; they should say so explicitly instead of reading as current.

Scope

• For each item decide: historical record (add an "as of v2.0.0 GA" header) or live status (refresh).
• Refresh consumer-validation-status.md with the date and the v2.1.0 canary evidence, or mark it as a point-in-time ledger.
• Update the awesome-bash gate/checklist and the package-manager registry wording to the post-GA state.
• Keep scripts/first-party-cutover check and the related BATS tests green.

Acceptance Criteria

• Every ledger/data file states whether it is historical or current and the date/release it describes.
• No document implies Base v1.8.0 or the v2.0.0 pin is the latest.
• Discovery and package-channel wording reflects that GA has shipped and names the actual remaining gate.
• ./tests/validate.sh passes.

Validation

scripts/first-party-cutover check, ./tests/validate.sh.

Project Fields

• Status: Backlog
• Priority: P2
• Area: Docs
• Size: S
• Issue type: Task
• Assignee: codeforester
• Milestone: v2.2.0

Agent Assignment

Assignee: @codeforester. Found during the pre-release documentation walkthrough of 2026-10-07 at the origin/main heads of base-bash-libs (454aabc) and base-bash-libs-demo (5e598be). No repository content was changed by the review.