Repository navigation
fix(runtime): prepare planned-stop evidence before explicit gateway stop - #131
Draft
RecursiveIntell wants to merge 1 commit into
Draft
RecursiveIntell wants to merge 1 commit into
RecursiveIntell wants to merge 1 commit into
Conversation
૮ >ﻌ< ა ci reviewran on acf18f0 — fix(runtime): prepare planned-stop evidence before explicit
|
This branch has not been deployed
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.
Explicit gateway Stop could reach service control without first recording planned-stop evidence through the canonical
gateway.statusproducer. Prepare that marker in an isolated active-source child scoped to the installation home, then use the existing unit routing. Stale, foreign or ambiguous identity and failed marker preparation abort service action. Restart, update, rollback and legacy handoff stay unchanged.Only
ares_runtime/local_runtime.pyand its existing test file change. The final matched original-source control reports 19 failures and two passes; the same test bytes pass 21 focused cases and 65 full-file cases on the final source. Those are overlapping gates, not 86 distinct tests. Fake process/service boundaries and temporary stores were used; no real service stop or live-home marker write ran. Independent source/offline post-review accepted the final hashes and exact forward/reverse replay.The unchanged canonical per-file runner ran with one worker and zero retries. Its wrapper was not run because whole-tree
compileall -j0conflicts with the explicit worker and bytecode constraints. Real subprocess/service acceptance, whole-suite CI parity, bot recovery and installed behavior remain unqualified. The residual identity-change boundary inside the canonical producer remains disclosed.Base
04997747879d54a242941d344c3a38293c307076, treecbabd9591dc00fdf8deed90aeb3e8b1dc5bd2ebc. Reverse patch SHA256bf974b7123c2c5b27dd414a152c69e8746485a635bea706a80eac27ede81eb3frestores the exact reviewed two-file preimages. This draft is uninstalled; publication performs no Stop, activation, service change or live rollback. Hosted CI is a separate gate.