Repository navigation
Use canonical FEP_Formal consumers and pin the qualified companion main - #290
Merged
Merged
Conversation
docxology
added a commit
that referenced
this pull request
Oct 29, 2026
Retain the bound website server when shutdown precedes serving-thread entry. Select the released FEP checkout contracts and run their provisioned Python and source CLI with offline pinned uv inside the existing envelope. Adapt the scoped website fix from e7cad53 (PR #290), retaining the reviewed paired runtime helper and companion pin. Manuscript custody and fresh current-pair qualification follow this Source commit.
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.
Use canonical FEP_Formal imports, commands and configuration throughout the active Lean consumer and bridge instructions. Verify companion-runtime discovery, interpreter identity and source ownership; retain strict cancellation/failure behavior and explicit compatibility with older pinned layouts in custody tooling. Preserve the deprecation information with exact path/diagnostic/full-line terminology exceptions; real-filesystem controls reject copied or altered statements.
Fix the real website startup/shutdown race exposed during comprehensive native CI. Capture the bound HTTP server in the serving thread instead of reading an instance reference that shutdown can clear. A real-socket subprocess reproduces the deadlock before the fix and passes afterward; all 270 website tests and the manuscript evidence controls pass. Original failed hosted evidence remains retained. No manuscript counts or outputs were rewritten after that source edit; strict token/prose/render-custody checks remain current.
Complete the coordinated source-pair refresh after all content changes. FEP PR231 retained the new Q7 source/native checkpoint for the exact website source change and merged at 605315652e96cb91c229babe7316b84400f6fd54. Fresh main run40794936894 completed successfully with all22 role contexts,15 wheel cells,4098 split Python cases, source-bound168-topic native evidence and the scoped render artifact. Its five original archives were retained and matched to GitHub SHA256 digests. The final GNN commit changes only .github/fep-lean-pair.json to that qualified FEP main.
At final head b2ea2d7, the real custody controls and all six local Python3.14 installed/status/finite/continuous/final/q7-source stages pass with unchanged environment/source bookends. Token/hydration and diff checks also pass. Earlier qualification included80 runtime/executor/cancellation controls,27 manuscript-evidence cases,26 terminology controls and strict repository/documentation gates. Full final-head hosted pairing on Python3.11/3.12/3.14 and every required native/platform/repository check must pass before merge; fresh GNN merged-main qualification remains separate.
Pair checks establish source custody and freshness with native_claim_ready:false. The retained FEP/GNN native checkpoint keeps its exact source/compiler scope. No new generated-runner execution, scientific, publication or package-release claim follows. GEO_INFER requires its own qualified core merge followed by a separate GNN pin-only PR.