Repository navigation
Validate final fork lifecycles and record review gates - #30
Draft
mtwilliams wants to merge 1 commit into
Draft
mtwilliams wants to merge 1 commit into
mtwilliams wants to merge 1 commit into
Conversation
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.
Completes the integration ledger and lifecycle diagnostic for the fork-only stack. The final soak checks golden scores through 100,000 ordinary calls, 1,000 alternating file/memory load-disposal cycles, and 100,000 managed bounded calls per runtime. The harness now discards results with Enum.each: an earlier collecting comprehension retained an accumulator and distorted memory observations. Temporary native lifetime counters confirmed reclamation and were removed; no production native implementation changed in this PR.
Corrected local results: bounded RSS ranged 102.8–104.2 MB on runtime 1.17.3 and 105.3–106.5 MB on 1.24.4; process counts stayed at 124 at every sample. Every call matched golden scores. These are synthetic CPU diagnostics, not leak guarantees for other models/providers. Exact byte counts and reproduction are in docs/integration.md.
The ledger records review order #2–#30, 216 suite checks (two optional ResNet cases excluded), constructor/environment/logging/bootstrap gates, scheduler measurements, fresh-VM upgrades, unsigned task commits, and ancestry-preserving merge guidance. API-25 per-run profiling and measurement-dependent GPU/NN primitives remain explicitly deferred; upstream/shared-package work stays outside scope.
Stacked on #29. Integration branch codex/ortex-integration combines the stack for source, all seven precompiled consumers, and complete package validation. The current combined stack additionally includes ownership fix #31; exact validation is recorded below. No release tag, upstream write, or Hex publication is part of this change.
Final combined validation is green at
a4cef8490858d89b7827ef6e62ba652107434373oncodex/ortex-integration:Review in stack order #2–#31. Preserve ancestry with merge commits, or rebase/retarget the remaining stack after squash/rebase merges. The worktree is clean. Fresh VM required for native resource upgrades. No upstream writes, release tags, or Hex publication were performed.