Repository navigation
Prepare GNN 5.0.1 with FEP 2.1.0 and refreshed manuscript - #281
Merged
Merged
Conversation
docxology
marked this pull request as ready for review
October 25, 2026 00:21
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.
Prepare GNN 5.0.1 with the accepted FEP_Formal 2.1.0 companion pin and regenerated manuscript outputs. Remove the unused bibliography entry whose dead link broke the strict tag documentation audit, update release metadata and README signposts, and retain the original immutable 5.0.0 observations. The 32-page manuscript and related outputs were regenerated through the full manuscript custody procedure.
The candidate is
855f385c2ea9a3a8ad1a6d8d17f25dea2153e1e2, treec81cb1848585e86c0feda51ec230f7abd3544dd5. Its only change from the reviewed manuscript successor K2 is the existing FEP pin, now pointing to accepted main96bf714d91c088e79b9dea54af0f9151f70de64f(FEP merged-main qualification).Validation binds all sixteen latest candidate workflow attempts and their applicable artifact reviews. CodeQL was retried once on the unchanged commit after GitHub stalled processing its successfully uploaded SARIF; the documented infrastructure-retry policy applies, and the first attempt and all other fifteen workflow attempts remain recorded. The comprehensive native profile independently qualifies Python 3.11, 3.12, and 3.13, with strict coverage above 80% in each environment. Installed-platform checks cover six platform/container roles. Full extras retains 9,623 passes, 26 explicit capability exclusions and ten source/log-bound subtest passes; warnings remain recorded. The GridWorld profile completed all 25 steps, with six backend executions and three explicit optional skips. Its executive summary used the declared rule-based fallback after an Ollama deadline.
A separate current-source nine-step native run exercised bounded file/step workers, three native executions, two numerical witness create/verify pairs, and the three offline DOM harnesses. Two actual FEP semantic CLI audits checked admitted finite filtering and passive Gaussian Kalman/Joseph evidence. Source-native execution, ordinary installed distributions, formal compilation, and authenticated execution remain distinct claims. Fresh merged-main and tag qualification and public release-asset parity follow this normal merge.