Ship a secure-default neutral install and hostile-input release proof

Problem/Motivation

The released stack can require hand wiring and contains permissive omissions. A repeatable install must prove the classified OSS trust floor without W&L-specific hostnames, default-off enforcement, empty scope bypasses, or unbounded reads.

Proposed resolution

Provide tenant-neutral configuration overlays, separate operator and public-agent trust roles, and an install verifier that runs the complete hostile-input north-star proof.

Acceptance criteria

• A clean supported install contains no W&L hostnames or tenant-specific secrets.
• Governed OAuth/scope enforcement, active policy, finite budgets, source mediation, keyed evidence,

and required companion components are enabled and verified.

• Operator and public-agent trust roles are distinct.
• The verifier attempts an allowed draft plus denied publication, a mass read, a configuration change,

and a live-content edit.

• Prompt-injection risk is recorded as a managed residual; the release does not claim it is solved by

model safety or rate limits.

• Upstream workflow evidence records the exact versions/configuration tested.
• Missing or permissive prerequisites fail the verifier.

User interface changes

Provide an operator-readable verification result with exact failed prerequisites and evidence IDs.