docs+config: propagate proposals 0001/0002 [accepted]+ADR status across stale references#117
Merged
Merged
Conversation
…ss stale references Companion to PRs #115 (acceptance flip) and #116 (ADR promotion). Sweeps the remaining files that still carried `[draft]` / `[review]` proposal status or referenced now-closed cross-repo gating issues. - README.adoc — proposal status flipped to `[accepted]` + ADR links; added 0003/0004 to the forward-looking section; rewrote the verifier-pass status sentence (was "gated on proposal 0002's acceptance"; now reflects PR #109 having shipped). - CHANGELOG.md — new Unreleased section "Multi-producer carrier ABI: proposals 0001 + 0002 accepted, promoted to ADRs (2026-05-30)" covering PRs #110-#116, the seven closed issues, and the producer- side gates that remain. - crates/typed-wasm-verify/Cargo.toml — feature-flag comments updated to reflect post-acceptance state (codec + verifier passes shipped; feature gates retained while Phase 3 stabilisation open). - docs/PRODUCTION-PATH.adoc — proposals 0001/0002 flipped to `[accepted]` with PR pointers (#107 codec, #109 verifier passes); added 0003/0004 to active-design-work list. - spec/type-safety-levels-for-wasm.adoc — wire-section status column updated for `typedwasm.regions` / `typedwasm.capabilities` / `typedwasm.access-sites` (each now reads `[accepted]` + ADR reference; codec entry-point lists added verifier passes). Tail references section updated to enumerate all four proposals with current status. - .machine_readable/6a2/STATE.a2ml — capabilities-by-level entries flipped from 30→100 (carrier ABI accepted); rewrote critical-next-actions to remove now-closed cross-repo review gates and surface the new downstream producer-codegen gates; rewrote [carrier-abi] section to record accepted-date / acceptance-pr / adr-pr for both proposals + added [draft] entries for 0003/0004; updated long-tail-open-after note to reflect the L2/L3-L6/L15 carrier-backed enforcement now landed. No source-code changes; docs + machine-readable state only. Profile docs (spec/{ARG,CRG,FRG,TRG}-PROFILE.adoc) left alone — those are point-in-time audit snapshots, not config.
3 tasks
hyperpolymath
added a commit
that referenced
this pull request
May 30, 2026
## 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: 1. **PROOF-NEEDS.md** — the 2026-05-27 reconciliation banner listed \"verifier L1-L6 + L13-L16 coverage on emitted wasm\" as \"in progress on PRs #76 / #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. 2. **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 - [ ] CI green (docs-only; no source changes) - [ ] PROOF-NEEDS structure preserved (reverse-chrono banner ordering) - [ ] Profile-doc link references resolve to actual \`.adoc\` files 🤖 Generated with [Claude Code](https://claude.com/claude-code)
🔍 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
Companion to #115 (acceptance flip) and #116 (ADR promotion). Sweeps the
remaining files that still carried
[draft]/[review]proposal statusor referenced now-closed cross-repo gating issues.
Files changed
What was deliberately left alone
`spec/{ARG,CRG,FRG,TRG}-PROFILE.adoc` — these are point-in-time audit
snapshots, not config. They mention the proposals as the live RFC
corpus, but rewriting audit history adds more noise than signal.
Test plan
🤖 Generated with Claude Code