PUBLIC.2 PUBLICATION CHANGES — NO EXPERIMENTAL CHANGE

Prepared separately from pinned public.1. Original Release 220, public.1 and all
historical workspace evidence remain unchanged. Four maintenance files are omitted;
the other fourteen files in the established eighteen-file disclosure set receive
identity projections and, for lineage, updated publication context. Source digests
and projection digests are separate in PROJECTION-INVENTORY.json. Exact unchanged
original files remain in PRESERVED-BYTE-PROVENANCE.json.

All PUBLIC2-OPAQUE-* labels are explicitly synthetic; no label claims to be a
historical identifier. Native journal MESSAGE, numeric authority-role IDs, relevant
process/unit/invocation/ticket bindings, ledger rows, receipts, authority state and
protected effects remain intact. Projected file hashes differ and the old signature
does not authenticate them. No independently signed redaction attestation exists.

Full saved maintenance replay is no longer publicly reproducible. Preserved older
reports are historical assertions, not a new public maintenance PASS. The five-case
native conclusion and manual/scope/same-tick/isolation boundaries are unchanged.

New/rewritten publication metadata, projection inventory, lineage/retrieval records,
disclosure summary, instructions and offline verifier identify public.2. Roles in
MANIFEST.json and PUBLIC-PATH-ROLES.json distinguish original bytes, projections,
historical unsigned reviews and new unsigned publication material. Every changed
inherited record except the new manifest is in PROJECTION-INVENTORY.json; manifest
derivation identities are in the external RELEASE-BINDING.json to avoid recursion.

New publication material and projections use Apache-2.0 within the owner's recorded
rights; LICENSE/NOTICE are unchanged. No external dependency rights are relicensed.
No experiment, software installation, signing, publication or indexing occurred.
