License, redistribution, provenance and executable-tooling scope

Retain every original LICENSE, NOTICE, INTEGRATION-NOTICE and license material in
the byte-preserved distribution. Its license records designate original EZA work
and new integration/verification tooling as Apache-2.0, subject to the rights the
publisher holds. Third-party materials keep their own terms. No general trademark
license, endorsement, patent clearance or new license interpretation is asserted.
The original author named in NOTICE is Montrel Hutto (Eziah AI / Eziah Accord).
Original implementation/review artifacts and integration tooling disclose AI
assistance. The fresh-Linux evaluator identifies itself as a Claude Code session.
This publication wrapper was also prepared with AI assistance.

Online package only: dependency locks and attribution/license text are included;
nine wheels, installed runtimes, VM images and native libraries are not included.
The original packaging audit recursively inspected 47 historical archives;
its recorded no-wheel/no-native-library conclusion is bound by this distribution's
verified inventory. Historical source/test tools remain inside frozen archives.
Do not confuse archived failed/earlier experiments with the active quick-start.

Unresolved bundled-wheel redistribution review remains real. The preserved
records/LICENSE-REVIEW files flag rpds-py native archery/rpds notice coverage,
cryptography OpenSSL/Rust coverage, and cffi/libffi provenance/notice coverage.
Those records describe the quarantined offline wheel option. This online-only
package does not distribute those binaries and does not claim that review is
resolved. Do not publish the parent developer-trial-001 directory, quarantines,
installed venv or an offline bundle under this release's clearance.

The top-level historical NOTICE points to licenses/STATUS.md in its original
release layout. In this wrapper that retained file is found after extraction at
release/EZA-001-P3-CONTINUITY-001/licenses/STATUS.md. Attribution is preserved;
no sealed file has been edited to repair a historical relative reference.

Executable tooling: privileged Python setup, sealing, launcher, acceptance,
export and cleanup programs are shipped as reviewed operator inputs. They are
outside the frozen CONTINUITY manifest and inside the developer inventory and
new publication signature scope. One AI-operated trial exercised the documented
installation/acceptance/export path; destructive cleanup was not exercised and
no comprehensive independent code security audit is claimed. Syntax/hash success
alone is not evidence of safe root execution on arbitrary hosts.

Publication follow-through: the owner must confirm the existing public trust
anchor remains under their control, supply a fresh signature for this corrected
manifest (the preceding staging signature was verified), verify downloads on a
clean recipient system and provide a working developer-results intake.
No live URL availability, current revocation status, service intake, or external
license source was queried during this offline gate. Preserve the external
evaluator attribution and review any personal/build paths before public release;
this gate does not change or redact authenticated historical evidence.