Theme Release Assurance offline evidence

This directory holds preregistrations and results for offline technical replays. They exercise only the static and install/build mechanics already present in the unpublished source CLI. Public repositories are benchmark inputs, not Compify pilots, customers, partners, endorsers, or product-validation evidence.

Every replay pins source commits, freezes its denominator before inspection, retains failures, separates lexical/install/build evidence, and publishes exact checksums. Absence of a supported lexical observation is unknown, never proof that a story is unaffected. A digest proves byte equality only; it is not a signature or third-party attestation.

These replays may falsify technical feasibility. They cannot satisfy the owner, real-destination, payment, activation, repeat, renewal, or PMF requirements in product-market-fit.md.

Raw JSON/JSONL/checksum artifacts are retained as repository files rather than web documentation pages. Review them in the pinned Git history; the rendered index summarizes their bounded conclusions without implying that Fumadocs serves arbitrary evidence files.