ci(linux-kvm): make the lane gate-ready — changes filter, aggregator, apt retries by norrietaylor · Pull Request #698 · gominimal/minimal

norrietaylor · 2026-07-10T00:34:13Z

What

PR5 of the CI refactor (#687). Off main, independent of the mac stack.

Converts the KVM lane to the always-triggered pattern so it can become a required check after a soak:

Trigger-level path filter → changes job (dorny/paths-filter, SHA-pinned v3.0.2, pull-requests: read). Same path list, now evaluated inside the workflow; workflow_dispatch runs everything. The header documents why trigger-level paths: must never return: a required context skipped by one stays "Expected" forever and wedges the PR.
New if: always() aggregator ci-linux-kvm-success — green when the e2e passed or was path-skipped, red only on failure/cancellation. It joins the ruleset after the lane soaks green (admin step in feature: CI refactor — clear build/test phases, three gating targets #687); until then the lane stays advisory exactly as today.
Evidence-backed apt retries (scripts/ci/retry.sh, 3×10s): mining ~200 runs per VM lane found zero failures in the artifact/libkrun/gvproxy fetches but a consistent transient class in apt — the only main-branch KVM failure in the window (run 28897380911) and both of its manual re-runs died in Install build dependencies, and the mac artifacts job failed twice in Install protoc. Those three call sites (KVM deps, setup-rust protoc, mac-artifacts protoc) are now retried; fetches stay un-retried.

Verification

actionlint — no new findings (one pre-existing SC2012 carried over verbatim). This PR triggers the lane itself (always-triggered now), so its own run exercises the changes-gate, the retried apt step, and the aggregator.

🤖 Generated with Claude Code

Summary by CodeRabbit

CI Improvements
- Improved Linux/KVM test workflow efficiency by running only when relevant changes are detected.
- Added reliable status reporting for the Linux/KVM test lane.
- Enabled prebuilt test binaries to run consistently across different environments.
Bug Fixes
- Improved executable discovery for end-to-end tests when build and test paths differ.
- Improved installation reliability for required protocol-buffer tooling in CI.

… apt retries Converts the KVM lane to the always-triggered pattern (#687): the trigger-level path filter moves into a `changes` job (dorny/paths-filter, SHA-pinned, pull-requests: read), the e2e gates on its output (workflow_dispatch runs everything), and a new `if: always()` aggregator — ci-linux-kvm-success — reports success when the e2e passed OR was path-skipped and red only on failure/cancellation. The context joins the required checks after the lane soaks green; until then the lane stays advisory exactly as before. Retries apt installs, the one step class with recorded transient failures in lane history: the sole main-branch KVM failure (run 28897380911) and both of its manual re-runs died in "Install build dependencies", and the macOS artifacts job failed twice in "Install protoc". scripts/ci/retry.sh wraps those three call sites (KVM deps, setup-rust protoc, mac-artifacts protoc); fetches stay un-retried — zero recorded failures. Refs: #687 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

coderabbitai · 2026-07-10T00:34:29Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 39a2da2f-051b-4ea2-9e33-ac96f11f8903

📥 Commits

Reviewing files that changed from the base of the PR and between 90df500 and 627fb0b.

📒 Files selected for processing (3)

.github/actions/setup-rust/action.yml
.github/workflows/ci-linux-kvm.yml
.github/workflows/ci-macos.yml

🚧 Files skipped from review as they are similar to previous changes (1)

.github/workflows/ci-linux-kvm.yml

📝 Walkthrough

Walkthrough

Changes

CI resilience and KVM test execution

Layer / File(s)	Summary
KVM change detection and runner setup `.github/workflows/ci-linux-kvm.yml`, `.github/actions/setup-rust/action.yml`, `.github/workflows/ci-macos.yml`	The KVM workflow moves change filtering into a `changes` job, gates build execution, and consolidates privileged package installation commands. Protobuf installation uses the same shell wrapper in shared Rust and macOS setup.
KVM build and test packaging `.github/workflows/ci-linux-kvm.yml`	The build job stages `minvmd`, initramfs, hash-suffixed test harnesses, and the linked libkrun prefix into the uploaded `testbed` artifact.
Staged harness execution `scripts/ci/run-testbin.sh`, `.github/workflows/ci-linux-kvm.yml`, `crates/minvmd/tests/*_e2e.rs`	The KVM test job resolves and executes staged harnesses from `testbins.json`; E2E tests select `minvmd` through `MINVMD_BIN` with a Cargo-path fallback.
KVM status aggregation `.github/workflows/ci-linux-kvm.yml`	An always-running aggregator combines change-detection, build, and test outcomes into the lane result.

Estimated code review effort: 4 (Complex) | ~45 minutes

Sequence Diagram(s)

sequenceDiagram
  participant changes
  participant build-linux
 
8000
 participant test-kvm
  participant run-testbin.sh
  participant testbins.json
  participant minvmd
  changes->>build-linux: Gate KVM build on relevant changes
  build-linux->>test-kvm: Provide uploaded testbed artifact
  test-kvm->>run-testbin.sh: Request target harness execution
  run-testbin.sh->>testbins.json: Resolve hash-suffixed binary
  run-testbin.sh->>minvmd: Execute staged E2E harness
  minvmd-->>test-kvm: Return test result

Possibly related issues

gominimal/inbox#269 — Covers the KVM CI refactor involving change filtering, artifact separation, aggregation, and runtime binary selection.
gominimal/minimal#687 — Describes the artifact-based KVM build/test pipeline and workflow gating implemented here.

Possibly related PRs

gominimal/webapp#145 — Uses a similar dorny/paths-filter changes job to gate downstream CI work.
gominimal/minimal#466 — Also changes the KVM pipeline around libkrun prefix handling.
gominimal/minimal#685 — Introduces the shared Rust setup action updated here.

Suggested labels: github_actions

Suggested reviewers: twitchyliquid64, jtnkminimal, bryan-minimal

Poem

I hop through workflows, tidy and bright,
Staging test binaries just right.
With minvmd paths found at runtime,
KVM tests march in perfect time.
Green aggregator, carrots in view—
CI leaves a happy trail for you! 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately points to the Linux KVM CI lane refactor, including the changes filter and success aggregator.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{Comment @coderabbitai help to get the list of available commands.}

Remove scripts/ci/retry.sh and unwrap its three call sites (KVM build deps, setup-rust protoc, ci-macos artifacts protoc). One recorded apt transient in lane history does not justify carrying retry machinery; if apt flakes recur we can reintroduce it with fresh evidence. Refs: #687 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

norrietaylor · 2026-07-10T04:53:10Z

Dropped the apt retry wrapper per review discussion (627fb0b): scripts/ci/retry.sh deleted, its three call sites (KVM build deps, setup-rust protoc, artifacts protoc) unwrapped to plain installs. One recorded apt transient doesn't justify carrying the machinery — we'll cross that bridge with fresh evidence if flakes recur.

…e toolchain pin Two fallouts f 8000 rom this PR's own run: - clippy 1.97 flags for_kv_map at checkouts/src/lib.rs:287 - iterate git_remotes.values_mut() instead of discarding the key. The one-time lint surfacing is the point of pinning. - the native lane's changes filter and the mac lane's trigger paths did not include rust-toolchain.toml, so this PR's own lanes skipped: a toolchain bump must re-run every Rust lane. The KVM lane's filter gains the same entry on the #698 branch (its trigger section is rewritten there; touching main's copy would conflict). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

rust-toolchain.toml joins the KVM changes filter: a rustc bump must re-run every Rust lane. Applied here post-#698-merge (the filter's file was rewritten there). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Cycle 2 across the three siblings: [machine] and on_oom owned by BRES alone, BRES limits scoped to enforced hosts, volumes keyed by project (arch AT21) with an access mode and a hold that survives stop and resume, the type-noun verb aliases (BOX-148), ram_reserved against a resolved auto ram (BRES-015), and the BRES/#698 overlap recorded as an open question. BOX: 24 refusal and flag cases that were splits of a parent behaviour are now indented sub-bullets of that parent, tier and verify lines kept; references point at the parent. 99 top-level requirements. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

…mal#1697) * docs(specs): add BOX, the local-first box spec from inbox#731 One record, one spec, one grammar for every session and task on a stock install: 146 EARS requirements across the box record and lifecycle, the Box Spec in minimal.toml and its deterministic expansion, the min box grammar with one-release aliases, memory admission, and the un-enrolled local provider. T1 property tests on expansion, type constraints and names; T2 Kani harnesses on the record state machine and admission arithmetic; the three local Box Provider API requirements wait on gominimal/arch#45. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): link BOX open questions to gominimal/arch#97–gominimal#100 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): fix box id entropy, rename events, detach stdout, name lookups Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): split BOX into three siblings and apply review cycle 1 BOX keeps the record, the Box Spec and the grammar (122 requirements, ids stable with gaps). Resources move to 26-spec-box-resources (BRES, 13 requirements, T2 admission harnesses intact) and Box Volumes to 27-spec-box-volumes (BVOL, 8 requirements). The dash goes to an amendment of 07-spec-min-dash-tui, the local Box Provider API waits on gominimal/arch#45, and the test-suite meta-requirements are carried by every tier/verify line. Review cycle 1: resume hooks, the bare `min stop` alias window, the projection field set per Gatehouse 6.3.2, `min box spec self` as a nesting non-goal, the brokered-secret enforcer, the generality claim, stopped-record exit codes, a `detached` event, `min provider list --all` (BOX-147), and the first slice. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): review cycle 2 and fold split cases under their parents Cycle 2 across the three siblings: [machine] and on_oom owned by BRES alone, BRES limits scoped to enforced hosts, volumes keyed by project (arch AT21) with an access mode and a hold that survives stop and resume, the type-noun verb aliases (BOX-148), ram_reserved against a resolved auto ram (BRES-015), and the BRES/gominimal#698 overlap recorded as an open question. BOX: 24 refusal and flag cases that were splits of a parent behaviour are now indented sub-bullets of that parent, tier and verify lines kept; references point at the parent. 99 top-level requirements. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): review cycle 3 across BOX, BRES and BVOL BOX-076 admits BVOL-011's volume items; the min shell ambiguity case sits under BOX-090; parent tier lines precede their sub-bullets; the network non-goal range is corrected. BRES-006 covers an omitted ram, BRES-016 adds the advisory-host creation warning arch requires. BVOL mounts at /volumes/<name> (open question for arch) and BVOL-012 keeps prune off held volumes. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): split the min grammar out of BOX into 28-spec-box-cli BOX now specifies the model only: the record, lifecycle, events, exec operations, the Box Spec and its expansion, and the un-enrolled path, with triggers stated as operations rather than verbs (60 requirements). BCLI carries the min box verb set, type nouns, shortcuts, exec flags, output schemas, exit codes, the one-release alias window, docs, and the host and provider commands (52 requirements), each binding to a BOX operation by id and carrying the BOX id it came from. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): consistency pass across BOX, BCLI, BRES and BVOL Exec client loss scoped to non-PTY, non-detached execs; a stopped box's "exists" mapped onto NET-013/015 with an open question for NET and GWI; min box rename bound (BCLI-058) and the alias table completed, with session destroy mapping to box rm --force so BEP-043 still fires; the stop, rm, prune, cp and events verbs bound to their BOX operations (BCLI-059 to 062); verbs removed from the model's remaining text; task end keyed on lifetime; a running record on daemon restart becomes stopped (BOX-154); detached output capture (BOX-155); legacy mode spellings named; stored exit codes stated; BRES-004's reservation cap takes arch's overcommit-policy value; BVOL's hold and bare-name decisions recorded as the owner's. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): review cycle 5: NET "exists" means running, stored signals NET-013/015 and GWI-005's "exists" now maps to the running state and "destroyed" to leaving it; a stopped box is neither kept running nor answers its name. A signal-ended stop stores the signal and min box wait returns 128 + signal (137 for a record the daemon restart marked stopped). The restart-to-stopped and host-stop-stops-boxes-first choices are recorded as the owner's; the bare-volume-name reason matches the record. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): read NET's destroyed as reaped; stopped names answer NODATA Per NET-128 and the networking design §7.1 a not-running box keeps its name in the zone and answers NODATA; NXDOMAIN starts at reap. Resume and name reuse need NET to register at resume as well as at finalise; the open question asks NET and GWI to confirm. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): answer NXDOMAIN at reap only for the last holder of a name A reused name follows its remaining holder (A if running, NODATA if not); own-address NODATA is put to NET as a question; resume cites BOX-025 and BOX-030. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): refuse resume while a running box holds the name NODATA applies while no running box holds a name; BOX-004's property covers resume; BOX-025 refuses a resume whose name a running box holds and BCLI reports it with exit 2 and a rename hint. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): consistency pass over the box specs, cycle 10 Accepted keys are arch's box.toml plus the additions this spec names; legacy mode spellings canonicalise into the spec and expire with the legacy tables; prune reaps only stopped or exited boxes matching all selectors; NET-015's stop list gains timeout, on_oom end_box and entrypoint return; resume applies to any pty_enabled box; the --network/--ingress overrides are the last expansion layer; provider aliases expire with the rest; secrets render as references in every output mode (BCLI-063); issue citations point at the arch#97/gominimal#98 comments that now carry the items. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): min box spec takes the override flags; volume hold ends on exit min box spec <entry> accepts --network and --ingress through the same last expansion layer as start, so the pre-flight render is what the daemon receives. A volume write hold is kept while a box is stopped and released when it reaches exited or is reaped (owner decision), so a task re-runs at once; resume from exited while another box holds the volume is refused with exit 5 (BVOL-013). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): overrides in the expansion properties; resume after volume removal The T1 properties for byte-identical and enrolment-invariant expansion range over command-line overrides too. A resumed box whose volume was removed while it was exited gets a fresh volume created and reattached by project and name. The name-conflict check on resume runs before the volume-hold check, so a resume meeting both exits 2. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): order the resume refusals: PTY check, name check, volume hold BVOL-013 applies only to pty_enabled boxes and runs after BOX-030 and BOX-025's name check; BCLI-007 and BCLI-009 cite that order. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): place the unsatisfiable-spec check in the resume refusal order BOX-025 states the full order once (PTY, name, spec, volume hold); BVOL-013 and BCLI cite it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): min session attach aliases the top-level min attach shortcut Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): the volumes first slice includes the single-writer refusal Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): qualify the fresh-volume claim on resume after removal Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): write the roles lines as prose, not a concatenation Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): an address that resolves to no box exits 4 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): close the arch consistency findings on the box specs Type constraints are checked against the expanded spec and a derived type may not loosen its parent (BOX-061, BOX-156). The flat egress keys the arch examples write get one release of hint-and-canonicalise grace (BOX-157). Rename refuses a held or reserved name (BOX-010) and name resolution is per host with a cross-host ambiguity refusal (BOX-005). Volumes drop the read-only mode until object storage lands and the expanded list is deduplicated by name (BVOL-014). OOM kills end the box per on_oom (BRES-017, BRES-018). min shell --new takes a suffixed name (BCLI-065), min session run is a usage error (BCLI-066), the attached exec id goes to stderr and min box show lists live execs (BCLI-067). BCLI-041 and BCLI-050 duplicated the alias table and are removed; BOX-021 drops the no-op stopped selector. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): settle the BRES split with the guest-memory epic BRES owns admission, the memory limit write, its read-only surface and exec-join (BRES-004 to BRES-009); inbox#698 keeps the guest size, swap, the cgroup2 mount and daemon reserve, pressure warnings, the shell banner and the min ls headroom line. Its S3b clamp rule gives way to BRES-004/005's refusal with figures. Closes the two clarification markers that named the overlap. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): move the resources spec to inbox#698 Resources now belong to gominimal/inbox#698, which will get a fresh BRES spec. BOX and BCLI cite that spec by id without requirement numbers. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): move BVOL and BCLI to their own PRs The volumes and CLI specs now land separately (docs/spec-box-volumes and docs/spec-box-cli) so the BOX model spec is reviewed on its own; both files are byte-identical on their new branches. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): date the BOX spec to its last revision Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): pin the BOX spec's arch link to a commit Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): align BOX-011 with BOX-154 and split BOX-152's event fields Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): apply the BOX arch-conformance review decisions Map the projection onto Gatehouse 6.3.2's field names with the defaults filled before canonicalisation and a base64url digest; scope BOX-001's host-side minting to the box_id; add the daemon's admission constraint check (BOX-160), record listing and reading (BOX-158, BOX-159) for the first slice, and per-value provenance (BOX-161); state the exec contract, every process in the box, and BOX-040's triggers; raise BOX-001 and BOX-072 to T1 and justify the T0 security requirements; name owners for attribute rules, runtime spec change, org types and the unenforced sections, which now warn at creation. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * docs(specs): limit BOX-160's admission check to the built-in root Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * docs(specs): drop the daily shortcuts from BOX's grammar non-goal BCLI no longer specifies min shell, min run, min attach or min ls; they are UX work layered on the grammar, so the non-goal names the long forms and the type nouns only. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): credit the OOM end to BRES and cite the DNS reading once Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): re-transcribe BOX's resume and task-run stories The epic now names min session attach, min box resume and min task run in S3 and S4 instead of the daily shortcuts. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): spell out BOX id ranges that span unused numbers Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): renumber the BOX spec to 29, clear of gominimal#1586 and gominimal#1988 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): settle BOX's first-slice type, parent and event reads The first slice records the type from the creating verb. A box created from outside any box has no parent. Events carry box, parent, timestamp and type, and BOX-162 reads the full retained stream and follows it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): record BOX's project root and bound exec to running boxes A box records its project root, which listing and reading return. An exec into a box not running is refused with exit 2, runs under the box's ceilings, and a detached exec closes stdin. Open questions cite gominimal/arch#112 (prune --stopped) and gominimal#113 (override layer). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): limit BOX expansion to sessions and tasks; log from start BOX-046 and BOX-063 expand only session and task entries and refuse the other four built-in types with exit 3 naming gominimal/inbox#678. BOX-155 logs a box's output from its start, attached or not. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): tabulate BOX-011's end data and tidy BOX's minor findings BOX-011's end data and BOX-076's added keys become tables. Timeout and exec client loss end with SIGTERM, a wait, then SIGKILL. The network non-goal points at Design reasoning, and the VM host is local-minvmd0. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): state BOX-001's type property for both creation paths Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): let a BOX exec carry its own timeout A BOX-149 sub-bullet ends an exec at its own timeout with BOX-150's sequence, records exec_exited with reason timeout, and keeps the box running. Design reasoning and the arch-gap open question record it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): date BOX to 2026-10-06 and mark O3 as moved to BCLI Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): cite gominimal/arch#114 for BOX's per-exec timeout gap Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): apply msample's five BOX findings BOX-063 refuses the four excluded types per entry, and BOX-145's vectors are the arch example's session and task entries. BOX-163 names a box at creation and refuses a running holder with exit 2 (gominimal/arch#122). Project file rules are left out like secret-store rules (arch#123). BOX-164 puts the record and log out of the box's reach. Expansion writes store references' upstream and inject into the spec for the projection. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): scope BOX-010's property to successful renames Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): cite BOX-151 for exec timeouts; add store rules to parity The exec-timeout sub-bullet cites BOX-151, which owns the end sequence. BOX-065 and BOX-142 take the client's [secret-store-rules] set as an input, since expansion now resolves store references from it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(specs): name the boxes crate in BOX's verify commands The sessions crate is being renamed to boxes before BOX is implemented, so that the crate holding the box domain types says box. Point BOX's ten `cargo nextest run -p sessions` checks at `-p boxes`. The test names are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CdRDynXbYoKR6dByN13KsD * docs(specs): re-pin BOX to arch 823f45f and adopt its rulings Re-pin the architecture link to gominimal/arch 823f45f, where every open question citing arch#97, gominimal#98, gominimal#99, gominimal#112, gominimal#113, gominimal#114 and gominimal#123 is merged, and turn those questions into citations. - BOX-163: refuse a held name only for a creation that asks for no fresh instance; a fresh instance is named <name>-<n> (arch#117). - BOX-071: project egress.deny_subnets as network.egress_deny_subnets (Gatehouse v1.26). - BOX-002 and the id-mint invariant: scoped to un-enrolled VM hosts; the STS mints on enrolled nodes (Gatehouse v1.27). - BOX-013 states the 10 s default grace; BOX-025's name refusal is exit 2 (arch#97 row 2). - BOX-165: the implicit [sessions.default] entry (arch#124), marked implicit by BOX-161 and covered by BOX-145's vectors. Three open questions remain: the NET/GWI reading (gominimal#2041), [params] delivery (arch#100) and exec_enabled, still proposed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CdRDynXbYoKR6dByN13KsD * docs(specs): move NET's sentences back to its Non-goals bullet Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CdRDynXbYoKR6dByN13KsD --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>

norrietaylor mentioned this pull request Jul 10, 2026

feature: CI refactor — clear build/test phases, three gating targets #687

Closed

17 of 19 tasks

norrietaylor added 3 commits July 9, 2026 18:23

Merge branch 'main' into ci/kvm-gate-ready

39775ce

ci(linux-kvm): split the monolith into build and test phases (#699)

62ae1aa

Merge branch 'main' into ci/kvm-gate-ready

90df500

norrietaylor mentioned this pull request Jul 10, 2026

ci: adopt nextest profiles; reshape the KVM lane to its end state #702

Merged

twitchyliquid64 approved these changes Jul 10, 2026

View reviewed changes

norrietaylor enabled auto-merge (squash) July 10, 2026 05:00

norrietaylor merged commit 58cc3d3 into main Jul 10, 2026
18 checks passed

norrietaylor deleted the ci/kvm-gate-ready branch July 10, 2026 05:01

norrietaylor added a commit that referenced this pull request Jul 10, 2026

Merge origin/main (post-#698) into ci/kvm-lane-reshape

de795f1

This was referenced Jul 10, 2026

fix(ci): run the path filter only on pull_request events #706

Merged

ci: flip every lane to always-trigger with in-workflow gates #712

Merged

build(deps): bump the github-actions group across 1 directory with 3 updates #725

Closed

norrietaylor mentioned this pull request Jul 16, 2026

ci(macos): darwin testbed — the mini stops compiling #779

Merged

gominimal-aw-bot Bot mentioned this pull request Jul 22, 2026

CI: macOS lane doesn't trigger on .minimal/minimal.toml, so guest-kernel bumps merge without a VM boot #897

Closed

mitodrummer mentioned this pull request Sep 25, 2026

docs(specs): add the local-first box spec (BOX) for inbox#731 #1697

Merged

mitodrummer mentioned this pull request Oct 16, 2026

Box — one record, one spec, one grammar for every session and task on a stock install #2236

Open

mitodrummer mentioned this pull request Nov 3, 2026

Box — one record, one spec, one grammar for every session and task on a stock install #2879

Open

Navigation Menu

Repository navigation

ci(linux-kvm): make the lane gate-ready — changes filter, aggregator, apt retries - #698

ci(linux-kvm): make the lane gate-ready — changes filter, aggregator, apt retries#698
norrietaylor merged 5 commits into
mainfrom
ci/kvm-gate-ready

Uh oh!

Reviews paused

Walkthrough

Changes

Sequence Diagram(s)

Uh oh!

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

Uh oh!

What

Verification

Summary by CodeRabbit

Uh oh!

Uh oh!

Reviews paused

Walkthrough

Changes

Sequence Diagram(s)

Uh oh!

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants