Warnings, failures and limitations

Warnings preserved:
1. Supplied recovery warning LEGACY_ID_HISTORY: the historical archive contains earlier reused working IDs w3, w4, w5, w6, w7, w8 and w9; new revisions preserve this history and never reuse an ID.
2. Reply encoder environment warning: "TERM environment variable not set." The encoder still exited 0 and wrote all four reply artifacts; the warning is preserved verbatim in logs/encode-reply.log.
3. The supplied offline.cjs mechanism is a process-level guard, not an operating-system sandbox and not proof of tool-level isolation.

Failures / unsuccessful attempts:
- No supplied verification, recovery, amendment validation or reply encoding command failed in this trial.
- One host orchestration call displayed no immediate stdout even though its captured encode-reply.log showed a successful exit 0. This was a presentation/orchestration anomaly, not a receiver or encoder failure, and the captured log is included.

Limitations:
- Supplied implementations, not an independent reimplementation, performed CVP2 decoding, USL1 recovery, Reed-Solomon/transport validation, frozen Carrier chain validation, canonical application-grammar validation and reply round-trip validation.
- The independent Python checks cover hashes, byte counts, recovered JSON counts, binding-path cross-resolution, checked-head metadata, amendment pins/alias reuse and reply-file/report hash consistency. They do not decode CVP2 or USL1 and do not validate semantics.
- Hash agreement demonstrates artifact consistency, not authenticated authorship.
- Checked concept status authenticates the selected frozen record, not the truth or acceptance of the new role assignment or clause.
- No current political, legal or factual claims were externally verified because browsing and external contact were prohibited.
- The encoded replacement remains a proposal only. No original clause was modified, no outside action was taken, and no affected person or institution is represented as accepting it.
