docs(lilrae): define the RAES scenario mapping and evidence-capture contract

[Brad-Edwards]

Objective

Define the RAES scenario mapping and evidence-capture contract for the accepted LilRAE integration boundary before adapter implementation starts.

Scope

• Keep SDL and environment-pack semantic authority in RAES; do not define adapter-owned SDL semantics.
• Identify the accepted integration scenario and inventory every action, outcome, observation, availability, termination, stochastic-control, evaluator, and lineage datum exposed by the native LilRAE boundary.
• State which data is available, unavailable, lossy, redacted, or withheld.
• Define the data required to reproduce the selected workflow and perform its equivalence evaluation.
• Make every SDL/task evidence requirement explicit at field/artifact granularity.
• Map each requirement to the native source and the backend-manifest capability the future adapter must publish.
• Record all impossible or lossy mappings before implementation begins.

Acceptance criteria

• The accepted scenario and task define every required capture artifact and field needed for reproduction and equivalence testing.
• Every requirement has native-source traceability and a planned manifest declaration.
• Unavailable and lossy data are explicit and cannot be represented as satisfiable.
• The contract is sufficient for implementation and admission tests to prove requirement-to-capability-to-artifact closure.
• No adapter implementation begins against an implicit or incomplete data-capture contract.

Dependencies

• design: publish the LilRAE adapter-facing integration boundary lilrae#12