Skip to content

Add release 1.4.0 facts and refresh active provenance - #42

Merged
luisleo526 merged 1 commit into
mainfrom
rel/1.4.0-facts
Oct 8, 2026
Merged

luisleo526 merged 1 commit into
mainfrom
rel/1.4.0-facts

Conversation

@luisleo526

@luisleo526 luisleo526 commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Add the registry-derived 1.4.0 scoreboard and refresh active provenance to the accepted engine b3192bfc / codegen bfc4ddce pair. Grade counts remain 7,983 excellent and 6 strong out of 7,989, with no below-strong grades or engine errors. All earlier release snapshots and the historical inventory are unchanged.

Depends on the workflow mapping commit 07ae0e5d5eba6689fc4552acfe01e397cd9d1aba landing first. Reproduce with the campaign exporter using that commit's campaign/facts/releases.json; the resulting facts file is 77,230 bytes, SHA-256 788e57fab67d3c946fc7e3a0a3ac34b3d2c25cbb6a0f5b72687955bc4f8832b6.

From a checkout of mapping commit 07ae0e5d5eba6689fc4552acfe01e397cd9d1aba, reproduce with:

lab facts export --releases campaign/facts/releases.json --out ../pineforge-release/facts/facts.json

Two independent exact-head reviews approved; one independently repeated the registry export byte-for-byte. Existing validation and Python checks remain required. This facts change creates no release tag; the source URL intentionally anticipates the tag under the established release order. Existing facts automation may wake on merge; its protected dispatch controls are unchanged, and consumer release versions must remain 1.3.0 until both release tags exist. The larger facts file is included in the pending MCP merge-tree tests.

Co-Authored-By: Codex <noreply@openai.com>
@luisleo526
luisleo526 marked this pull request as ready for review October 8, 2026 00:01
@luisleo526
luisleo526 merged commit d5d21f1 into main Oct 8, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant