Evidence and claim boundaries

Frozen source: exact EZA-001-P3-CONTINUITY-001, 148 files, independently pinned
manifest 1b0837e15ed2743be13feb2de577b914ebced614e4184231ffb55570b22eba88.
Original IDENTITY, MANIFEST, LICENSE, NOTICE and all historical files are unchanged.
Inherited reproduction commands/test verdicts are historical. Use this package's
INSTALL/WALKTHROUGH/ACCEPTANCE instructions for this first developer attempt.

Prior environment evidence: ENVELOPE-001 parent Linux qualification on Ubuntu
24.04.5 aarch64, kernel 6.8.0-142-generic, Python 3.12.3, SQLite 3.45.1, pip 24.0,
2 vCPU/about 1.9 GiB RAM/no swap. CONTINUITY-001 independent temporal verification
was macOS/Python 3.12.14/SQLite 3.53.1, explicitly not Linux socket lanes.
Parent evidence does not transfer a PASS to the derivative or these wrappers.

Packaging validation: candidate byte/inventory preservation; metadata and wheel
hashes previously verified against PyPI; active dependency closure; real pip
cross-target DOWNLOAD checks; new Python syntax/static review; six mocked framing/pure JSON checks; distribution audit.
No new integration code has been run against protected state, no VM was touched,
no fresh identities were created and no downloaded code was installed/executed.

New integration v1 supplies deployment glue only: fresh fixture provisioning,
root socket ownership handoff after service-UID listening, four existing frozen
lanes, bounded delegate framing/result binding checks, immutable principal client
wrapping, read-only oracle, isolated synthetic clock fixture, export and cleanup.
The frozen enforcement implementation and authority semantics are unchanged.
The clock fixture patches only in-memory test instrumentation in a NEW isolated
domain and is not loaded by the running service or exposed on its lanes.

Restrictions remain: trusted OS/root/service/clock/storage; finite allocations;
synthetic local objects; no production credentials, external effects, UTC
attestation, whole-host rollback defense, power-loss proof, witness repair,
migration or return-value recovery. Post-publication uncertainty can close a domain
permanently. Restart success means quiescent continuity, not crash recovery.

All historical packaging failures/outputs are kept in the INTERNAL parent tree.
HISTORY.json records the earlier integrity pins. They are not bundled here because
the internal tree contains third-party wheel binaries and old blocked archives.
No old local path, account, runtime or VM is a prerequisite for these instructions.
