Repository navigation
fix: preview retained acting continuation through canonical graph - #664
Merged
Merged
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.
Outcome
A simulation continuation previews the failed actor after a completed, reviewed prefix through the canonical execution graph. Successful products and review chronology remain attached to their original lineage.
Work authority
Contributor mode (select one):
Plan
Reproduce zero selection after normal closure, reuse existing canonical source/lineage/review interpretation for a read-only prospective simulation workday, then qualify the exact candidate before supported adoption and continuation. No completed Architect replay, stale retry, forced-ready edit, copied product or plan reapproval.
Changes and commits
Verification
Test-first:1failed/28deselected; complete red log SHA256e08f65c3425b747e762529eb27704dbfef93e50b7452702be012fadf6deb6911.
Local30selection unit passed, logd3f318db3c9b16394ef5628b1bebbe0f15b8b73b382b729f2eb7fc9f94a08eb6; existing public-service/SQL suite18passed, log8b900663f33b0162b9357c010fb88306ded28fe7f74a62e454211ea5267a0551.
Focused canonical SQL projection:1passed/15filtered, loga1bdc10d720d53f9c74fb7d2346c5eb4d8a8b0e8cb39d9637223bddb6efac131. Source endpoints and historical statuses/results are controlled fixture inputs; this is not genuine TreeDX/model/charge/settlement/physical-cleanup proof.
npm run build:dist passed, loga6db69154dfbcb0b066a2a62e57de2c396aac5ca20fb0244d69e7f05d0e4c063. npm run check:file-lengths including architecture passed, log201613fce20dd9d2ba19e8c38449fc001a519deb969302a570ca23d59ef88404. git diff --check passed.
Initial fixture missing-inbox migration and compiled20% planning mismatch failures retained and corrected with existing migration/intended allocation0; no assertion, deadline or allowance weakened.
Full exact-candidate API/real PostgreSQL/native TreeDX prerequisites and coded component qualification: Pending this original Actions run. No local scene or changed-runtime coaching launched. Local focused checks are additional evidence, not full prerequisites.
I ran the narrowest relevant package verification and documented any checks that could not be run.
Risk and rollback
Prospective projection must retain exact source custody, lineage, profile and review-cycle denials. It writes no graph/workday state; creation still revalidates authority. Roll back through an ordinary revert PR of58dc771ffdd5de2addc1a281cc9c55f29389a0c4, qualify and adopt through supported trsd. Preserve prior snapshots, products, reviews, estimates, deadlines, failures and unrelated development selections.
Completion summary
Focused regression, SQL coverage and minimum implementation are complete. Full qualification, normal expected-head merge, supported adoption and actual native MCP Writer continuation remain pending. Retained corrected/approved Architect product147d852a279b38f58184ce7e494b6dc59784fdb2 is not integrated. Ordinary simulated releases remain0. API663 merged normally; its adoption is separate and in progress.
AGPL committer authorization
The trusted base workflow checks the provider-authenticated PR author against the repository allowlist. No credential, spoofed identity or per-PR approval attestation is supplied.
Submission checklist