Alias routes carry no Version, so a canonical hostname can serve without X-Carlos-Version Issue open
Migrated from github.com/carlosframework/platform issue #126, opened 2026-08-09. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".
Still outstanding: Alias rows following no channel are never stamped with Version, so a canonical hostname serves with no X-Carlos-Version.
---
Found verifying the #110 rollout on tito. The tito console is one process behind three routes: carlos.tito.io (the channel-following row adoption moves and stamps), and console.platform.tito.io / console.bab.platform.tito.io (alias rows following no channel, Version forever empty). The canonical origin — console.platform.tito.io — therefore serves with no X-Carlos-Version header, while the legacy hostname carries the honest one.
Consequences: the header verification tell fails on exactly the hostname people are told to use, and a carlos deploy watch pointed at a canonical alias would time out headerless (same shape as #112 was for static routes).
Direction: alias rows could inherit the header from the row whose process they share (the addr/socket target identifies it), or adoption could stamp every route of the same (account, app, addr) group. Until then: verify tito console builds via carlos.tito.io or /proc/<pid>/exe, not the canonical host's header (recorded in memory).
🤖 Generated with Claude Code