Render parity scoreboard docs from release-hub facts - #318
Merged
Merged
Conversation
Refresh generated fact-marker contents only after the registry advanced; release 1.0.1 remains independent. Earlier a744bee rendering is retained in the parent commit.
Bring the PR up to date so the strict required-status rule applies to the current base. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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
1 participant
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.
Docs-only update: README scoreboard, Why PineForge and lane evidence render from canonical release-hub tokens. Main is explicitly measured 2026-10-03 at engine 700c5d2: 7,949 excellent / 40 strong of 7,989. Release 1.0.1 still grades 7,905 excellent / 84 strong until the next release.
Supervisor fixes: table format pipes escaped, backticks emitted inside markers, handwritten hub link uses blob/main, hard lane restored first. The 309 corpus + 700 closed = 1,009 hard-lane probes and 17 excluded anomalies are tokens. Historical inventory is independent of future main population rebinds. Commit messages name deleted sentence origins for the doc-reverts gate.
Current head: 3769703 (main #316, #317, #319 and #321 merged in; the strict required-status rule needs an up-to-date branch. Both merges were clean; main's README changes were ABI declaration counts, not parity figures.)
Tree: f25104c76ed74b63834a280946bec6cb71dcce5e
Exact-tree gates, re-run at this head after the release hub squash:
lab remote preflight,docs: passed; preflight exit 0, 44 stages, 0 advisories; docs passed, 0 Doxygen warnings.
lab verify record via diff: pineforge/verify SUCCESS posted at this head (docs-only basis: preflight+docs on tree f25104c7, 2 files since main f6fdc03).
lab verify parity via diff: pineforge/parity SUCCESS posted at this head; no engine behavior diff.
No sweep performed; against main only README.md and docs/pages/contributing-llm.md change.
lab facts render/check against the landed release hub (squash d9e56f5e3c89b55f7d21a0f346c726619abf88e5, raw facts sha256 28c96b44823001e9305f6eaff9813c53ca067ef8b227499d1fe457e66ac6b501): 51 markers, 0 files changed, 0 drift.
GitHub markdown API: no visible pf fragments.
Workflow #92 and release hub #20 have landed; land after web #26. If engine main moves again before this lands, the branch goes BEHIND and the two statuses no longer apply to the new head: merge main, re-run the exact-tree gates and re-post verify and parity. Nothing merged here.