The pilot reads this section as instructions, and V1 (8318605) moved
premises underneath it while the tag it points at stayed still.
- A-E1: passing at v0.5.0a2 is not a promise DEFAULT's bytes never move.
The expectation is anchored to the upstream axis; DEFAULT also tracks
commons' ingest-spec axis, and V1 moved that one.
- A-E1: the runner reported the MAF wrapper has the same shape as
po-claude's (three positional args, no `profile`), and re-exports the
library symbol, so the two profile calls have somewhere to land.
- A-E1: our empty-diff span covers our examples/ only; the runner holds
a fourth golden set we cannot pre-measure.
- A-E5: the `:164`/`:144` literals still describe the tag but no longer
`main`; dated rather than swapped.
- A-E5: re-run-in-place was recorded as undecided. It is decided, and
was already true at the tag — measured by reading v0.5.0a2, not
inferred from main.
- GA table: two rows rest on "DEFAULT is byte-stable", which V1 ended.
Plus the input the release-exposure report must carry — a value-literal
`generated` predicate fails OPEN against the O2 form, so byte-clean
goldens are not evidence a consumer is unaffected.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X974G3Z7yXzdXK2nHnm11h
Kjell Tore Guttormsen
fcb6e4c2c9