reqtrail 0.2.0 — the boundary

One construction site, now enforced rather than intended: the exact request is a
private value and the public view is derived from it by a single function.
inspect consumes that pair; run will be the second consumer. Nothing is sent
— there is still no transport.

reqtrail resolve <file> [--request <id>] [--json]
reqtrail ui <file> [--request <id>]

Breaking, if you parse --json: prepared is now projection. The
document is otherwise byte-identical to 0.1.0. schemaVersion stays 1 — it
versions the workspace file, not the output.

Node 22+. Zero runtime dependencies.

Pre-registered in BOUNDARY-PREREGISTRATION.md, results in
BOUNDARY-EVIDENCE.md, including two predictions that were wrong. The
derivation is proven; that the exact request matches the wire is not, and cannot
be until something sends. Sending arrives in 0.3.0.