Repository navigation
feat: run the dispatch image that names the job's accounts - #224
Merged
sindredg merged 2 commits intoOct 28, 2026
Merged
Conversation
Four jobs on 2026-10-28 as a run set: two NetBox jobs that matched with a verdict under each account's name from one accepted call, a job with no collection that failed at the dispatch step before it ran, and a synthetic job. A lessons row, the run set's bar on the milestone 5 chart with a category for a job that failed before it ran, the worklog section, and the validation README's last run: 425 of 426, U.7 on a newer mesh agent release upstream (#225).
sindredg
marked this pull request as ready for review
October 28, 2026 15:45
sindredg
deleted the
feat/run-the-dispatch-image-that-names-the-accounts
branch
October 28, 2026 15:52
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.
Change
The template's three steps move to the dispatch image the pipeline pushed from
mainat b9de301, the first push after #222 merged. That image's dispatch step reads a NetBox job's accounts from the checks' verdicts and names them in the job line (ADR 0051).With it, the live run that shows the fix: the run set Accounts in the job line, a lessons row, its bar on the milestone 5 chart, the worklog section, and the validation README's last run.
Closes #221.
The milestone 5 outcomes chart changed (
docs/diagrams/test-outcomes-5.htmland its SVG): a new bar, and a category "Failed before the job ran" for the job with no collection. Waiting for a look before the merge.Validation
On the live system, 2026-10-28 15:00 to 15:40 UTC, from this branch at a4f3b32. Output kept outside the repository.
4e9cd3cb; the socket activeokline per image in one egress window; the templateconfiguredokfor the new digest, 0 denied;dispatch,compare, andrevokeon651992ddnb-10281500-a1, collected, then runverdictskeyed by both accountsnb-10281500-nocollect, no collectionfailed: no checks' verdicts for this job; no audit line; no worker linenb-10281500-a3, collected, then runmain=on the new digest651992ddsyn-10281500load_skillandtools__get_evidenceonlyG.8andW.9passG.8andW.9pass;U.7fails on a mesh agent release upstream, 1.104.4 against the pin 1.104.2 (#225)render.py --checkexit 0; linksNot verified: Goose refusing an output that leaves an account out, since both calls were accepted first; a case with more than two accounts. The first prompt grew to 3,796 tokens from 3,475, read in 309 seconds.
Risks and follow-up
U.7stays failed until the mesh agent pin moves (U.7 fails: the mesh VPN agent pin is 1.104.2 and upstream released 1.104.4 #225).