EZA-001 Developer Trial Package 001 — online installation, integration v1
READY FOR A FIRST INSTALLATION ATTEMPT, SUBJECT TO SEPARATE TRIAL AUTHORIZATION.
No fresh-reader installation or Linux run has been performed for this package.

EXPERIMENTAL: synthetic objects only. Two authenticated principal UIDs, two
separate delegate UIDs, two protected local synthetic objects, fifteen lifetime
terminal authorization workflows per principal. Refusals and explicit closures
consume slots. No production credentials, network effects or external actions.
Interruptions after pending publication can permanently close the entire domain.
No migration, witness repair, replenishment, domain reconstruction or recovery.

Start with INSTALL.txt, then WALKTHROUGH.txt and ACCEPTANCE.txt. Every privileged
command is labeled ROOT. CLEANUP.txt preserves results before any deletion.
Reading these files does not authorize executing the installation/trial.

Layout:
  release/EZA-001-P3-CONTINUITY-001/  exact frozen candidate, 148 files
  integration/*_v1.py               new operator setup/launcher and socket clients
  verification/*_v1.py              new read-only oracle, bounded walkthrough and
                                    isolated temporal fixture
  dependencies/                    nine-package locks and attribution/license text;
                                    NO wheels, installed runtimes or native binaries
  records/                         packaging checks, scope, provenance and history
  verify_v1.py                      package/frozen inventory verification only
  SHA256SUMS, SHA256SUMS.sha256      exact distributable inventory and companion pin

Only this directory is distributable. Its parent is INTERNAL packaging evidence
and contains quarantined wheels and historical archives. Do not distribute it.
No bundled-wheel redistribution clearance is claimed. The offline option remains
deferred. Developers obtain the exact wheels themselves from official PyPI's
files.pythonhosted.org HTTPS endpoints with pip's mandatory hash verification.

Frozen candidate identity and MANIFEST.json are unchanged:
  EZA-001-P3-CONTINUITY-001
  SHA-256 1b0837e15ed2743be13feb2de577b914ebced614e4184231ffb55570b22eba88
The new integration scripts are outside that manifest. Their integrity is covered
by this package's SHA256SUMS, not by the frozen release identity. No new signature
or independent validation is implied. The frozen Apache-2.0 LICENSE/NOTICE and
licenses/ directory are retained; new original integration code is Apache-2.0.

Verify from this directory, without root, installation or network:
  python3 -I -B verify_v1.py --expected-inventory DIGEST_FROM_THE_HANDOFF
Use the inventory digest supplied independently with the handoff, not just its
companion file. Integrity is not publisher authentication; this is unsigned.
Keep verification output outside the sealed package directory.

Scope: parent ENVELOPE-001 Linux evidence used Ubuntu 24.04.5 aarch64, CPython
3.12.3, SQLite 3.45.1 and pip 24.0. CONTINUITY-001 independent temporal verification
was on macOS. This derivative and these new tools have NOT been validated on
Linux. Metadata/pip download checks establish dependency selection and hash-lock
operation, not binary execution, installation success or production readiness.
Read records/SCOPE.txt and records/AUDIT.json before transferring the package.
