AGENTS.md post-push step references retired systemctl service, should be k3s rollout #16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-20T07:25:48Z - https://github.com/coilysiren/repo-recall/issues/221
Problem
AGENTS.mdline 49 (Release + post-push section):That post-push step is stale. repo-recall is Kubernetes-only on kai-server now (
infrastructure/deploy/repo-recall.yml: three containers per pod, tailscale sidecar, tailnet-only). There is norepo-recall-update.serviceto systemctl-start.Fix
Rewrite the post-push step to:
brew outdated->brew upgrade coilysiren/repo-recall/repo-recall->brew services restart repo-recall. (Mac is the staging-shape consumer of the new release, ref coilysiren/session-lattice#21 cabling.)docker.yml) and a k3s rollout. Document the actual rollout command (coily ops kubectl rollout restart deployment/repo-recall -n repo-recallor whatever the canonical wrapper is). Cross-linkinfrastructure/deploy/repo-recall.ymlso the next reader knows where the manifest lives.Why it matters
The agent will literally try to run the systemctl command on every push. Quiet failure mode (systemctl returns 5/non-existent unit, agent shrugs and moves on) means prod-on-kai-server doesn't actually update.