feat(lilrae): implement and qualify the optional LilRAE adapter

[Brad-Edwards]

Outcome

If LilRAE's accepted integration decision identifies a distinct translation boundary, the adapters repository implements, tests, documents, and releases that adapter through its normal profile conventions.

Scope

• Consume only public RAES and LilRAE interfaces.
• Translate the accepted adapter-facing action, observation, capability, and failure surfaces.
• Publish an adapter manifest and honest capability/loss disclosures.
• Compose RAES conformance with adapter-specific contract and integration tests.
• Document installation, compatibility, trust assumptions, and troubleshooting.

Non-negotiable evidence-capture requirements

• Begin implementation only against the approved scenario mapping and evidence-capture contract from docs(lilrae): define the RAES scenario mapping and evidence-capture contract #89.
• Capture every SDL/task-required datum available at the accepted LilRAE boundary.
• Publish a truthful field/artifact-level manifest backed by the implemented capture paths and native boundary capabilities.
• Derive evidence-satisfaction claims from the artifacts and fields actually emitted; do not use hardcoded references, unconditional capabilities, compatibility fallbacks, or adapter-specific bypasses.
• Fail closed before execution when any required datum is unsupported, unavailable, lossy beyond the authored contract, or unverifiable.
• Preserve enough portable evidence to trace each run to its actions and outcome and recompute every declared equivalence measure.

Acceptance criteria

• Work starts only after design: publish the LilRAE adapter-facing integration boundary lilrae#12 accepts a distinct adapter boundary.
• Work starts only against the approved capture contract in docs(lilrae): define the RAES scenario mapping and evidence-capture contract #89.
• The adapter does not own SDL or environment-pack semantics.
• The adapter does not duplicate LilRAE lifecycle, readiness, rollback, teardown, or evidence ownership.
• Unsupported and lossy translations are explicit and tested.
• Every admitted capture requirement maps end to end from the authored contract through a manifest capability and implemented capture path to actual emitted artifact fields.
• No hardcoded capability or evidence-satisfaction claim exists in the LilRAE path.
• Admission fails closed when any required capture is missing or unverifiable.
• The release is independently installable and versioned in this repository.
• If the LilRAE decision selects direct conformance with no adapter, close this issue as not planned.

Non-goals

• Blocking the canonical LilRAE quickstart.
• Adding a wrapper solely for repository symmetry.