feat(yawning-titan): add the example environment pack and researcher workflow

[Brad-Edwards]

Objective

Provide one validated YAWNING-TITAN environment pack and a no-code researcher workflow for the selected case.

Scope

• Add environments/yawning-titan-reference/ from the published raes-env-packs template.
• Include pack identity, the canonical SDL, provenance/licensing/safety review, compatibility claims, associated-artifact identity where applicable, source-ledger references, and clear participant/operator/evaluator boundaries.
• Integrate the adapter into the repository's installed researcher command so a clean environment can inspect identities, validate the pack, run one episode or seeded batch, and retain a portable artifact inventory.
• Provide a reference build, automated rehearsal, and matching researcher walkthrough.
• Keep runtime implementation selection and simulator-native configuration outside pack semantics.
• Mark draft, built, or golden only according to evidence actually produced.
• Keep the pack out of the Python wheel; publish it as versioned repository/release content.

Acceptance criteria

• raes-pack-validate and raes-pack-release check pass.
• A clean installed environment can acquire the immutable pack, run the documented short path, and validate its outputs.
• Build, tests, and walkthrough use the same scenario, controls, agent, objective, and evaluator.
• Participant, operator, evaluator/restricted, native-source, and public artifact boundaries pass leak checks.
• Provenance covers all upstream sources, exclusions, generated content, and redistribution decisions.
• The command rejects mismatched pins/digests, unsafe output reuse, unsupported controls, and invalid participant bindings before execution.
• The pack defines no RAES semantics and RAESystem/env-packs receives no scenario content.

Shared command reference

• feat(cli): add a researcher-facing run and evidence command with CybORG support #20

[Brad-Edwards]

RAESystem/hub#10 has now established the federated catalog boundary for reusable example packs. Pack source belongs in an appropriate catalog repository (with RAESystem/reference-packs as the first-party curated catalog) under environments/<pack-id>/, using a history- and provenance-preserving one-way transfer. This adapter repository retains simulator realization and backend-native evidence, then consumes the released pack identity; it should not retain a competing editable pack copy. The upstream format, validation, release, provenance, trust, and compatibility contracts remain owned by RAESystem/env-packs.