Repository navigation
Preserve selected workday authority across unrelated graph progress - #663
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 workday can now start from an unchanged selected root when another project advances the team's execution graph. Freshness compares the selected node, Decision, source, effort and priority while the original full graph cursor remains sealed in the immutable preflight receipt.
Work authority
Contributor mode (select one):
Plan
Reproduce the earliest owning freshness failure, change only its semantic comparison, retain actual authority denials, and qualify through the ordinary full Actions path before runtime adoption or a new native attempt. The live problem response did not expose its per-comparison diagnostics: the exact cause of either historical start remains unproven. The focused regression independently proves this defect.
Changes and commits
Verification
Test-first: 1 failed /26 deselected, workday_preflight_stale with demandSetDigest diagnostic. Complete red log SHA256 e3a314348d691292f9a06cf5f581d4377631f7d38d926a9c6eabefd045f70b6d.
Focused selection/public-start invocation: 46 passed across 3 files before moving the added integration case into its existing suite for architecture-policy compliance; 28 selection tests and the moved integration case then passed at their final locations. Stored-cursor tampering remains an integrity denial.
Strict npm run build:dist passed. npm run check:file-lengths (including architecture policy) and git diff --check passed. Initial policy failures (504/501-line test and 11-file directory) were corrected by using the existing helper and suite; no limit changed.
Full API unit/integration/native TreeDX+PostgreSQL prerequisites and component scene qualification: Pending ordinary Actions. Local controlled SQL/HTTP coverage is not native TreeDX, live model execution, settlement, physical teardown or release proof. No local scene was launched.
I ran the narrowest relevant package verification and documented any checks that could not be run.
Risk and rollback
The change removes an observation cursor from semantic admission freshness. All selected authority facts and signed receipt bytes remain checked. Previously issued receipts remain immutable; an older digest may require a fresh preflight after adoption. No issued assignment or deadline changes. Roll back through an ordinary revert PR of 6fc2795, qualify it, then adopt through supported trsd. Preserve unrelated services and all retained leases.
Completion summary
Implementation and focused checks complete; full qualification, normal expected-head merge, exact runtime adoption and a successful real Deployment retry remain pending. SDK Architect performed a useful request-changes/correction/approval loop; its Writer later failed on a mutating completion-verification command, and that separate workday closed normally. No active SDK workday is being hot-swapped. Ordinary simulated releases remain 0; implementation ratio stays 0 team/20 coordinator until another actual merge.
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 claim is supplied.
Submission checklist