Repository navigation
Add finite original-operation observer with preserved custody - #4736
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.
An integrator currently has to revisit an already-running CI operation to distinguish unchanged progress from actionable attention. Add one finite read-only observer for an explicitly named GitHub Actions run/attempt, preserving original operation identity, clocks, budgets, source and custody.
Core owns the reducer, GitHub owns bounded native reads and the existing CLI owns local continuation. Identity and two-sweep barriers cover the issue/run/PR/head/population. A restart cannot renew original work/cleanup deadlines or request/output budgets; interrupted evidence cannot masquerade as a completed cursor. Attention is emitted for terminal/failure/gap/deadline rather than each unchanged tick. This observer cannot select, dispatch, write Status, release reservations, replay effects or close issues.
Coverage/cost is explicit:8 GETs for up to100 selected-run jobs,10 for101–128; existing transport may transiently receive4MiB while accepted pages are capped256KiB. It observes one selected run, not the full policy-required check set; no savings or exactly-once claim.
Validation: original independent source review and causal compiler-repair reviews PASS; actualSDK10.0.401,3locked restores,3serial builds and all20focusedfacts PASS at7478705a (8Core/7GitHub/5CLI), with exactTRX counts and reaped EOF cleanup. Original failed builds remain retained; one order-sensitive duplicate-field fixture was corrected without changing its decoder expectation. Protected12a8 source, including accepted Matrix report/history, was integrated and Atlas/generated closure prepared through maintained sources. Final exact-head required CI remains necessary.
Source acceptance does not complete Delivery4731 or parent4730. Coherent publication, physical installed caller/instruction adoption, one necessary ordinary exact-head native observation and declared changed-head/failure/interruption/restart/deadline/rollback acceptance remain open. All original owners, worktrees and439inherited+46later uncertain effects remain unreleased.
Continues #4731 under #4730 .
The first sourceCI found two XML documentation comments in the implementation rather than its paired signature. Same-owner repair moves the public charging contract verbatim to its exported signature and removes the duplicate module comment; executable code, API, checker and baseline are unchanged. Independent exacta7fd4c repair review PASS; maintained gate,90 fixture cases,8protocol controls and3mutation controls PASS. Original87/3failure retained. Full final444-mutant and other requiredCI remain necessary.
The original hosted package failure is preserved. Same-PR reviewed repair retains the image SDK directory through guarded same-filesystem no-clobber rename before pinned exact setup, preserving strict path/version/custody checks and raw version diagnostics; four added pure controls passed. Prospective coherent110 readiness now names accepted109 predecessor source/content and retains all authority/collision/history/budget guards; 19 candidate controls and 200 recovery controls passed with two explicit private-census skips. This source tuple does not allocate a namespace or authorize publication. Observer release notes and Atlas source closure are included; final exact-head required CI remains necessary.
Actual hosted exact-SDK setup and strict custody checks passed. The original subsequent42-test fixture failure is preserved: GNU mv versions report a destination race either through nonzero rename refusal or the source-still-present postguard. Reviewed test-only repair accepts exactly those two refusal markers for that one case, retaining nonzero exit, no setup, source identity/bytes and racing destination ownership checks. Four pure tests pass; production workflow is unchanged. Final-head requiredCI remains necessary.
Actual prior-head hosted package qualification completed successfully. Accepted protected Wizard SOURCE021 (PR4737→86b0408d) is now normally merged into this same observer branch. Independent integration review verifies both parents source/modes unchanged outside three Atlas catalogs and the maintained derived manifest;341record union preserves all histories. Creator021/coherent110 and the observer110 readiness remain coherent. Final integrated-head requiredCI is necessary; publication and installed/native full acceptance remain open.