Restore TFTMAC continuity and adopt cumulative small gains - #10
Merged
flashls1 merged 5 commits intoSep 11, 2026
Merged
Conversation
flashls1
changed the title
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
1 participant
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.
Restores the missing live OvernightLab install/launch seams after PR #9, reconciles current project authority, records the post-merge loss boundary for ignored derived campaign files, and seals the surviving Sept. 10 native capture database identities.
Also adopts the clarified cumulative optimization doctrine: continuous useful 60 FPS remains the ultimate target, but individual candidates no longer need an arbitrary +5% weighted-FPS gain to be worth retaining. Small repeatable net improvements can be classified PROMISING, confirmed, promoted as the next DEV-B8-WIN-## baseline, and compounded. Neutral/inconclusive/losing candidates are logged, rolled back, and the pass moves on. HOME_RUN remains the label for large broad wins, and correctness/material-regression vetoes remain intact.
The executable CombatBenchmarkAnalysis and native tests now enforce this policy. Full local production validation passes with 112 native tests. No new gameplay/performance candidate was run by this doctrine change.