docs: PROOF-NEEDS reconciliation 2026-05-30 + profile-doc cleanup#118
Merged
Conversation
Adjacent housekeeping found while waiting on #117 CI. **PROOF-NEEDS.md** — adds RECONCILIATION 2026-05-30 banner at the top of the file (above the existing 2026-05-27 block per the reverse-chrono convention). Closes the "verifier L1-L6 + L13-L16 coverage on emitted wasm" long-tail item flagged by the 2026-05-27 banner as "in progress on PRs #76 / #77 in a parallel session": - proposals 0001 + 0002 `[accepted]` 2026-05-30 → ADR-0002 + ADR-0003 - `verify_regions_from_module` (PR #107), `verify_capabilities_from_module` + `verify_access_sites_from_module` (PR #109) shipped behind `unstable-l2` / `unstable-l15` - L13 cross-module + L15-C remain open (proposals 0003 + 0004 `[draft]`) - WasmCert-Isabelle / byte-equality / parser round-trip remain unchanged (external dependencies / blocked on emitter+parser) Historical reconciliation blocks (2026-05-26, -27, -18) preserved unchanged. **Profile docs (spec/{ARG,CRG,FRG,TRG}-PROFILE.adoc)** — fixes the literal file-extension typo `0001-*.md` / `0002-*.md` (files are `.adoc`, not `.md`) so the link references are accurate. Also: - `CRG-PROFILE.adoc` row 53 description rewritten — the verifier's feature gates no longer "pre-stage" a proposal; the carrier ABIs are accepted and the verifier passes have shipped. Also updates pinned `wasmparser` / `wasm-encoder` version 0.250.0 → 0.251.0 to match `Cargo.toml`. - `FRG-PROFILE.adoc` row C1, `ARG-PROFILE.adoc` row C, and `TRG-PROFILE.adoc` row M5: add an inline "→ ADR-0002 + ADR-0003" pointer next to the 0001/0002 references and surface 0003/0004 as the current `[draft]` RFC corpus. No source-code changes.
🔍 Hypatia Security ScanFindings: 83 issues detected
View findings[
{
"reason": "Action perpolymath/standards/.github/workflows/governance-reusable.yml@main\n needs attention",
"type": "unpinned_action",
"file": "governance.yml",
"action": "pin_sha",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in boj-build.yml",
"type": "missing_timeout_minutes",
"file": "boj-build.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in c5-regenerate.yml",
"type": "missing_timeout_minutes",
"file": "c5-regenerate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in cargo-audit.yml",
"type": "missing_timeout_minutes",
"file": "cargo-audit.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in codeql.yml",
"type": "missing_timeout_minutes",
"file": "codeql.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adjacent housekeeping found while waiting on #117 CI. Two unrelated
issues bundled because they're both stale-reference cleanup found in
the same audit pass:
PROOF-NEEDS.md — the 2026-05-27 reconciliation banner listed
"verifier L1-L6 + L13-L16 coverage on emitted wasm" as "in
progress on PRs docs(proposals): 0001 multi-producer carrier sections for L2–L6 and L15 (Refs #34) #76 / feat(verify): pre-stage typedwasm.regions codec behind cargo feature unstable-l2 #77 in a parallel session". The arc has
closed. Adds a new `RECONCILIATION 2026-05-30` block at the top
(above the existing 2026-05-27 block) per the reverse-chrono
convention. Historical banners preserved unchanged.
Profile docs (`spec/{ARG,CRG,FRG,TRG}-PROFILE.adoc`) — all
four reference `docs/proposals/0001-.md` / `0002-.md` (wrong
extension — files are `.adoc`, not `.md`). This is a literal
link-resolution bug, not a status update. Also rewrites
`CRG-PROFILE.adoc` row 53 (verifier capability description was
pre-acceptance era) and fixes pinned wasm-tools version 0.250.0 →
0.251.0 to match `Cargo.toml`.
Why filed separately from #117
#117 was scoped to the load-bearing config files (README, CHANGELOG,
STATE.a2ml, PRODUCTION-PATH, spec doc, Cargo.toml). PROOF-NEEDS +
profile-doc cleanup are adjacent finds, not scope-creep. Per memory
[[feedback_amend_swallows_parallel_staged]] avoiding amend on an
auto-merge-armed PR; separate auditable change.
Test plan
🤖 Generated with Claude Code