feat: implement and release the hello-recovery environment pack

[Brad-Edwards]

Goal

Create the first deliberately tiny first-party environment pack at environments/hello-recovery/. This issue bootstraps the catalog implementation selected by RAESystem/hub#10 without creating a second copy in Hub, LilRAE, an adapter, or a backend repository.

Ownership and boundaries

• Accountable pack owner: @Brad-Edwards.
• Catalog owner owns admission, review, release, pack-level rehearsal, support, and archival.
• Use the released raes-env-packs format, validation, release, provenance, trust, and compatibility contracts; do not redefine them here.
• Keep simulator/backend realizations and backend-native evidence in their adapter or backend repositories.
• Preserve source history, authorship, original repository/path/commit/tree, licensing, and evidence references for any extracted reusable material.
• Use one-way authority transfer: after extraction, no competing editable pack copy remains in the originating repository.

Pack scope

Model one small service with one dependency, one observable failure, and one bounded recovery objective suitable for the Hub quickstart and LilRAE onboarding. Keep the scenario intentionally small enough to inspect end to end.

Implementation

• Add complete source and assets under environments/hello-recovery/.
• Add repository governance and review ownership appropriate to a curated catalog.
• Pass raes-pack-check and static raes-pack-validate checks, plus RAES SDL compile/plan checks.
• Record provenance, license, safety review, compatibility, associated-artifact identity, and release.yaml metadata.
• Publish immutable, identity-verifiable release views using the upstream release contract.
• Coordinate the LilRAE compatibility proof and handoff tracked in test: qualify the canonical environment pack end to end lilrae#10.

Acceptance criteria

• The pack validates and releases through released raes-env-packs tooling.
• The pack card is complete and names ownership, compatibility, provenance, trust, and support status.
• A released artifact can be acquired cleanly and its identity verified.
• The scenario compiles/plans under RAES and completes its defined rehearsal.
• Hub and consumer repositories link to this authority rather than storing pack bytes.

References

• RAESystem/hub#10
• RAESystem/hub#11
• test: qualify the canonical environment pack end to end lilrae#10
• RAESystem/env-packs

[doublewhy]

Naming-decision hold (2026-08-13): pack authoring may remain as private/name-neutral design notes, but implementation, immutable identity selection, catalog publication, and downstream release claims are paused pending the public/technical naming decision. Do not publish pack bytes or create a new public identity during the hold.

[doublewhy]

Scope update: implement and test hello-recovery under the current internal identity; rename later if needed. Pack validation, inventory generation, deterministic bytes, and downstream fixtures may proceed. Defer only publishing the immutable catalog artifact/new durable identity and any breaking public contract.