Repository navigation
chore(tooling): retain selected Cargo list output - #77
Draft
undergroundrap wants to merge 4 commits into
Draft
undergroundrap wants to merge 4 commits into
undergroundrap wants to merge 4 commits into
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.
Successful guarded Cargo listings currently discard their merged decoded output, leaving compilation and explicit lock-wait notices unavailable for inspection after the run. Retain the existing successful WO22 B01 and WO23 M07 listing output in two optional report-only JSON files inside the existing phase-diagnostics directory.
The sink is configured before admission and runs after accepted listing/list-end, outside the existing list/capture spans. It preserves requests, arguments, targets, native capture, negative causes/exits, refusal, restoration, cleanup and credits. Output/argv are cloned; files use fixed names, create-new/no overwrite and a262144-byte serialized UTF8 cap each. Missing, unsafe, partial or failed diagnostics remain unavailable and do not change validation. Added I/O remains enclosing cost. No workflow, Cargo request, timer, target or correctness gate is changed.
The maintained phase controls include the corrected actual-boundary Measure-Object admission and an exact syntax/evidence dependency closure. Independent source review accepted the exact three-file candidate. One separately approved source-selected closed-control run was independently accepted for44 cases,325 ordered assertions,12 returned source pins and79 returned modeled case calls. Six diagnostic payloads and four adjacent-route calls were internally asserted; raw payload/argv/output/guard/adjacent records are not returned. These results establish neither operational/native filesystem behavior nor Full/platform/PowerShell5.1 execution or speedup.
This draft proposes one ordinary automatic hosted Windows/Ubuntu Full PR cycle under a separately approved exact-candidate three-file adoption/publication ruling and hosted-Full-in-lieu-of-local-Full exception. Those approvals are required before publication; hosted results are pending. No external Full invocation of the325-assertion helper has been identified. Retained Cargo Compiling/Blocking/Finished messages may guide a later attribution decision; absent messages are unknown and rounded durations cannot precisely allocate CPU, lock wait, startup or capture overhead. No speedup is claimed.