amadan
Edge: host-level redirect route kind (www→apex, retired hostnames) Feature Request open
Migrated from github.com/carlosframework/platform issue #105, opened 2026-08-08. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".
Still outstanding: No generic edge redirect route kind, so www-to-apex and retired hostnames have no platform primitive.
---
Registry route kinds are instance/service/static only, and no serving code in the edge emits a 301 — recorded in docs/superpowers/specs/2026-08-05-carloku-launch-design.md §5 when the carloku cutover wanted one. Two live consequences today:
- www.carloku.com serves the same static tree as carloku.com instead of redirecting — duplicate content, two canonical URLs.
- Retiring a hostname (dashboard.carloku.com → console.carloku.com, 2026-08-08 decision) has no platform primitive. The console grew CONSOLEREDIRECTHOSTS to 301 its own retired hosts, which works because the retired route happens to point at the console process — but that trick only exists for the console app.
Proposal: a redirect route kind — Kind: "redirect" plus a target URL column (additive wire change; rows written before it must still parse). The edge answers any request on that host with 301 (GET/HEAD) / 308 (otherwise) to target + original path+query, before upstream dispatch. No unit, no socket, no cert difference — the host still needs its LE cert exactly like a static route.
CLI surface follows the no-infra rule: creating one should work through carlos add/console API, not box-local sqlite — which intersects with #64 (routes verb) and #82 (domain attach).
🤖 Generated with Claude Code
https://claude.ai/code/session_01Su1MdJFZfcyM8Q5n7qDtvB