carlos / platform Public

Static release promoted to edge never adopted on the box (bam/yste-2026-report v2) Issue open

claude agent, operated by paul@keymail.dev driven by paul@keymail.dev session 681d5313 · claude-code/2.1.284 · DOCS-T1

A static release promoted to edge is never adopted on the box.

App yste-2026-report (account bam, static, host yste-2026-report.bam.platform.tito.io, carlos-tito-ie).

carlos deploy --console https://carlos.tito.io --app yste-2026-report --account bam --kind static --version v2 … <dir> → shipped yste-2026-report v2, promoted yste-2026-report v2 -> edge at 2026-10-07T16:49:35Z.
carlos channels and carlos releases agree: edge = v2.
The deploy's own watch timed out on HTTP 401 (the app is gated, which is expected and known).
On the box, 25+ minutes later: /data/static/bam/yste-2026-report/ holds only v1 and current -> v1 (that symlink was last touched 2026-10-07 13:33, before the promote). No v2 directory was ever written.
journalctl -u carlos-edge since the promote has adoption lines for other apps (bae/titogo/canary/...: channel has no release yet) and nothing for bam/yste-2026-report.
v1 (shipped 2026-10-04 11:05) was adopted fine.

The deploy output says "a static route re-checks its channel about every 60s". Expected: current -> v2 within a couple of minutes. Actual: never adopted.

Asked: why the edge's release adoption skips this route, and a fix so a promoted static release lands. We are not copying files onto the box by hand.

claude agent, operated by paul@keymail.dev driven by paul@keymail.dev session 681d5313 · claude-code/2.1.284 · DOCS-T1

Happened again, and it does resolve eventually but slowly: v2 (promoted 2026-10-07 16:49Z) was being served by 2026-10-09, but not 25 minutes after the promote. v3 promoted 2026-10-09 to edge; 7 minutes later current -> v2 still, no v3 directory on the box.