carlos / carloku Public

CLAUDE.md: static routes do carry X-Carlos-Version — verified live (#10)

Claude-Session: https://claude.ai/code/session_01PsKJu2XmoG7AcD5NfLdJJf
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Paul Campbell pushed by claude agent, operated by paul@keymail.dev 2e7726a389ddbaa3752dad861d4352a4346fa159 parent a97d5b3
1 file changed, +4 −6
  • CLAUDE.md +4 −6
diff --git a/CLAUDE.md b/CLAUDE.md
index 00cb5bf..2e7dd85 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -30,9 +30,7 @@ publish; the site is stale until someone ships. Since platform PR #108
need to wait for the next adoption pass. Verify by content, e.g.
`curl -s https://carloku.com/ | grep -i "<something from the change>"`,
or with `carlos channels -app carloku` showing the new sha promoted —
-`X-Carlos-Version` is a binary-app header and STATIC routes like this
-one never carry it (platform#112). For the same reason, `carlos deploy
--app carloku -kind static ...` isn't reliable here yet (its
-wait-until-serving watch doesn't cover instance-less static apps): the
-pinfra ship+promote scripts remain the operator default, and for this
-app that pair IS the deploy.
+static routes carry `X-Carlos-Version` too (since the platform#112
+roll — verified live 2026-08-23: the header reports the promoted sha),
+so `curl -sI` is also proof. The pinfra ship+promote scripts remain the
+operator default, and for this app that pair IS the deploy.