jss-format-v1.md and jss-seal-spec.md are pinned to upstream 0c45f29. Every other doc that cites upstream -- semantic-parity, upstream-bootstrap-spec, configuration-parity, upstream-harness, bootstrap-semantic-parity, opentelemetry, grafana-dashboard -- pins f29815c391fc2644f8a3dd36b899fb3697dd1ea6. Seven against two, with no explanation on either side. Nothing is known to be wrong: every constant in the file was checked against storage/segment.zig and matches -- magic "jss0", header_size 256, the four reader sanity caps (1<<18, 1<<20, 1<<20, 1<<30), 4096 events/block. Recorded that verification inline with its date. But this is a byte-exact wire contract, so an unexplained pin fork is worth resolving on purpose rather than inheriting. Deciding which commit is right means reading upstream at both, which cannot be done from this repository, so the discrepancy is flagged rather than guessed at. Also marks the segment/*.go paths and the docs/README.md 3.1-3.4 citation as upstream's, consistent with the other upstream specs. I passed jss-seal-spec.md first this session and missed the shared pin then. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>