fix(manifest): the egress blocker named a premise the measurement falsified
`scope_planned.blockers` for secret egress read "19 entries … 25 at different cut points" — one table cut at two granularities, waiting on a reconciliation of two ports. `docs/secret-egress-divergence.md` (2d9ee9c, corrected in4a6f6ff) measured otherwise: they are ports of two different source tables in the same source repository, so reconciling the ports was never going to close it. Replaced with the three measured, independent reasons: no id space on the commons side (seed A carries name+pattern only, and a fixture names labels); match semantics disagree (first-match-wins against finditer over all 25 — one label against two on the Bearer+JWT witness); membership diverges both ways and is inherited from two different seeds, so re-measuring either port cannot close it. Only the first is the outgoing question; the other two stand whatever the answer. Two hand-carried numbers in the retired text corrected in place: aws-access-key-id was not the one clean 1:1 (2/19 byte-identical, AWS not among them — the guard anchors with \b), and `GitHub Token` maps to three guard ids, not four, leaving ghu_ and ghr_ uncovered. `scope_planned.$comment` said "a distinct unresolved question" — singular — and is amended alongside. Measured here, not transcribed: `entry_points_by_scope.scopes` carries no entry for signatures/secret-egress.json at all. Recorded as a standing requirement, not as a fourth reason. No id string is proposed; checked against both outgoing coord messages of 2026-08-13. No case, no signature table and no other data file touched. conformance/manifest.json 0.5.0 -> 0.5.1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016inh17NCrQpWN3mrghfJgT
This commit is contained in:
parent
4a6f6ffc16
commit
4356caa689
2 changed files with 56 additions and 3 deletions
File diff suppressed because one or more lines are too long
Loading…
Add table
Add a link
Reference in a new issue