Repository navigation
docs: render the active scoreboard from the facts tokens at pineforge-release 03b8dcc - #337
Merged
Merged
Conversation
…-release 03b8dcc Re-render the marked README values against the hub's canonical facts at 03b8dcc (the squash of release hub #27): the active scoreboard is pineforge-parity-baseline-20261004-engine-6b77f061 (engine 6b77f06, codegen 285ac035), 7,970 excellent / 19 strong of 7,989 graded, none below strong. Release scoreboards keep their own numbers. Only values inside pf markers change. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Bring the PR up to date so the strict required-status rule applies to the current base. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
luisleo526
added a commit
that referenced
this pull request
Oct 5, 2026
* docs: release notes and version scoping for v1.2.0 CHANGELOG: the Unreleased section becomes 1.2.0 (2026-10-05), a minor release that adds the compiled execution-capabilities extension to the C ABI (PF_CAPABILITIES_API_VERSION, strategy_capabilities_api_version, strategy_capabilities_receipt). One bullet per change since v1.1.0 with its PR (#328, #330, #331, #332, #333, #334, #335, #336, #337, #338 and the session-clock change, written #VCP until its PR number exists), the recipe additions under State hashes (#328, #330, #335; domain tags and epoch unchanged), Report keys (docker/run_json.py is byte-identical to v1.1.0's, so no key changes) and Migration. Version scoping: README, install and public-contract pages name v1.2.0 and codegen 1.2.0; "since the next release" and "fixed on main" in the capabilities guide and the runner guide become 1.2.0 and 1.1.0 (#325). Lines that state what an earlier release shipped stay. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> * docs: 1.2.0's grades from the facts tokens, #339, and codegen's license - CHANGELOG: the session-clock change is #339 (merged as 52292db), in place of the #VCP token of 3082fbd; the "What a script author sees" bullet of 3082fbd now states release 1.2.0's grades (registry baseline pineforge-parity-baseline-20261005-engine-52292db9: 7,970 excellent / 19 strong of 7,989, none below strong) instead of the main scoreboard at 6b77f06. - README: the release sentence names 1.2.0 and renders releases[1.2.0], and the main scoreboard renders the same baseline, from pineforge-release facts/facts.json at 0c2f6838 (the facts export for the 1.2.0 release). - README, LEGAL.md, docs/pages/index.md: pineforge-codegen is under the PineForge Source License 1.1 from its release 1.2.0; releases up to 1.1.0 keep the PolyForm Noncommercial terms they shipped with. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> --------- Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
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.
Re-renders the README's marked scoreboard values (and the ones in docs/pages/contributing-llm.md) from the release hub's canonical facts at pineforge-release 03b8dcc8c6f0d60531309bf0abbb3fcad749ec55, the squash of release hub #27. Only values inside
pfmarkers change; no handwritten text moved.Active baseline: pineforge-parity-baseline-20261004-engine-6b77f061 (engine 6b77f06, codegen 285ac035, promoted 2026-10-04T21:11:07Z): 7,989 graded, 7,970 excellent (99.76 %), 19 strong (0.24 %), 0 below strong, 0 engine errors. The README showed 7,951 / 38 (engine 7b59662). Release grades (v1.1.0 and v1.0.1) keep their own baselines.
Docs-only, so no sweep: README.md and docs/pages/contributing-llm.md, 13 lines. Head 49619e7 is one commit on main 6b77f06 (0 behind).
Gates:
lab facts renderandlab facts checkagainst the raw facts file pinned to the hub commit: PASS, 51 markers, 0 drift.lab facts check --github-render(GitHub's own markdown renderer, plain Markdown mode): zero visiblepf:fragments.lab remotepreflight + docs on a clean checkout of this head: preflight exit 0 (ci_preflight, 44 stages, 0 advisories), docs exit 0 (0 Doxygen warnings); the host's tree 16f84556f54ec16f925fc5953ea463f2d12d56d6 is this head's tree.lab verify record --via diff:pineforge/verifysuccess posted at this head (docs-only basis: preflight+docs on tree 16f84556, 2 files since main 6b77f06).lab verify parity --via diff:pineforge/paritysuccess posted at this head (no engine behaviour change: 2 files since 6b77f06, docs 2).If engine main moves 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. Release hub #27 has landed.
🤖 Generated with Claude Code