Repository navigation
spec(tri/lab): vps queue dispatch argv law (#13970) - #14023
Merged
Merged
Conversation
gHashTag
enabled auto-merge (squash)
November 15, 2026 20:06
Contributor
gHashTag
disabled auto-merge
November 15, 2026 20:18
This was referenced Nov 15, 2026
Contributor
PR DashboardGenerated at: 2026-11-15 20:24:39 UTC
Summary
Seal Status
|
… (Refs #13970) Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Contributor
PR DashboardGenerated at: 2026-11-15 20:46:58 UTC
Summary
Seal Status
|
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.
Closes #13970
Adds the VPS agent-loop queue dispatch as an argv law in
specs/tri/lab/dispatch.t27, next to the existing lab dispatch law. Until now the two commands of that route (stage copy, then one rename into the pending queue) lived only in prose.vps_queue_argv(out, cap, step, host, name, dir) -> usizewrites one command as newline-separated words and returns the number of bytes written.VQ_STAGE(0) is the stage copy,VQ_MOVE(1) is the rename intoqueue/pending. Any other step returns 0.-, not starting with-; the directory is non-empty, does not start with-and holds no byte <= 32.capor the buffer, the builder returns 0, so a cut command is never run.vps_queue_refusal(step, host, name, dir)names the bad field (step:,name:,host:,dir:), empty when the input is accepted.lab-node.Existing functions and tests of the spec are unchanged (spec diff: 1 file, +128 lines, 0 removed).
Seals
Five seals are resealed from the CI artifact of Seal Coverage dispatch run 43757257273 (head
2d685d37e0), byte for byte, in commit0a4bcc2ee5:lab_TriLabDispatch.json(the spec itself): 6 passed of 6, vacuous 0.t27os_T27OsNodeMarket.json,t27os_T27OsNodePilot.json,t27os_T27OsNodeRunner.json,t27os_T27OsNodeRunnerTickArgv.json: the importers whose closure records this spec.ci_GitlabLane.jsonalso records this spec in its closure and is not resealed here:specs/ci/gitlab_lane.t27did not compile at that head, and its seal is already stale on master (#14010).Evidence
Lab node, through the agent-loop queue, compiler build
/root/t27-m13-final:955f018d19(first attempt)14f5b6c4a1(spec head)The lab node's compiler build is older than master and could not count vacuous passes; that number (0) comes from the CI seal above. Spec Guards on this PR reports
specs/tri/lab/dispatch.t27: head 0, base 0.Reds inherited from master
spec-guards: 203 stale generated-code hashes on this head (run 43759736395), the same 203 as master atbde874c770(run 43759027776), Spec Guards has been red on master since #3435, and two PRs merged past it #3440.coverage(run 43759736545):ci_GitlabLane.json(seals: reseal - ci_GitlabLane.json stale on master after #13996 #14010),t27b_T27bGoldenSpec.jsonandt27b_T27bMiddleEnd.json(seals: reseal - t27b_T27bGoldenSpec.json and t27b_T27bMiddleEnd.json stale on master after #14002 #14028, after t27b: first-iteration peel — bench_audit to GCC -O2 parity; pass telemetry; golden_spec SSOT update #14002). No seal of this PR is listed.scan:runs/ref_full.txtandruns/ref_full_b.txtfrom t27b: first-iteration peel — bench_audit to GCC -O2 parity; pass telemetry; golden_spec SSOT update #14002 carry a home path; red on master atbde874c770(run 43759027654), ci: scan red on master - runs/ref_full.txt and runs/ref_full_b.txt carry a home path #14030.t27b-native-ratchet: t27b-native-ratchet red: graph_transition trap site 45 vs 46 #13504.Written by a free-tier pane (glm-4.5-flash) from a brief; the diff was read in full by the orchestrating session before this PR was opened. The seal commit is the CI artifact, committed by the orchestrating session.
🤖 Generated with Claude Code