Repository navigation
[Meta] Autodeploy lane on vela — merged main reaches the daemon without an operator - #756
Merged
unohee merged 1 commit intoSep 28, 2026
Conversation
This was referenced Sep 26, 2026
…out an operator (AGT-4182) Salvaged from draft PR #756: re-applied onto current main (was 178 commits behind), package-lock.json churn dropped. Adds decideAutodeployGate (pure checklist over ledger state + container age + build SHA) with contract tests, plus the host vela-autodeploy.sh / vela-build.sh runtime.
unohee
force-pushed
the
swarm/AGT-4182-meta-autodeploy-lane-on-vela-merged-main
branch
from
September 28, 2026 05:39
4d9f737 to
d1e56b5
Compare
unohee
marked this pull request as ready for review
September 28, 2026 05:39
unohee
deleted the
swarm/AGT-4182-meta-autodeploy-lane-on-vela-merged-main
branch
September 28, 2026 05:50
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.
Summary
Salvaged from a draft left by a failed autonomous run (original body said "execution failed 4 times … very likely incomplete"). Re-applied onto current
main(branch was 178 commits behind); thepackage-lock.jsonchurn (npmlibcfield removal, unrelated to the feature) was dropped.What it does — an autodeploy lane so a merged
mainreaches the daemon without an operator:src/ops/velaAutodeployGates.ts:decideAutodeployGate— a pure checklist (build SHA already current / ledger has active runs / container inside the rate-limit window) returningdeployorskip+ reason. Kept in TypeScript so CI can lock the skip reasons without SSHing to the host.src/ops/velaAutodeployGates.test.ts,src/ops/velaAutodeploy.script.test.ts: contract tests over the decisions and the shell steps.vela-autodeploy.sh,vela-build.sh: the host runtime..gitignore,ARCHITECTURE.md.Verification (on current main)
npx tsc --noEmit→ cleannpx vitest run src/ops/velaAutodeployGates.test.ts src/ops/velaAutodeploy.script.test.ts→ 9 passed / 7 skipped (skips require host SSH, by design)main:src/ops/velaAutodeployGates.ts,vela-autodeploy.sh,vela-build.shdo not exist onmain.Notes