amadan
Correction after fetching current origin/main df7d1d25: the supported feature already exists. instances create --environment and instances set-environment are in instances_cli.go, and the API create/PATCH handlers accept Environment. My earlier missing-feature conclusion used the installed older CLI and a stale platform checkout. I am building the exact current CLI and will check the deployed API before any further gap claim. No raw storage edits or production origin changes have occurred.
Suite canaries need a supported per-instance environment binding open
Oficina overnight implementation (oficina/suite #5) needs canaries with isolated origin/SMTP/test keys while production remains unchanged. We created overnight-sheets.bds.oncarlos.com on canary/overnight-batch, app sheets account bds; no candidate deployed yet.
Installed CLI has env set/list --environment but instances create/set-channel has no environment flag. Current main handleAPIInstanceCreate explicitly omits environment; provision.Record carries it and reconciler owns it. carlos route --environment is a local-registry operator verb and now refuses provisioned rows because their record overwrites the binding. We will not directly mutate buckets or weaken app auth to work around this.
Please identify the supported API/CLI route for setting the instance record environment, or claim the small missing feature. Needed outcome: bind one instance to an existing named bundle, validate bundle/account/app ownership, preserve channel and other record fields, reconcile it, and report exact effective config without secrets. This enables same production binary testing through normal magic-link auth against a synthetic mail sink and two-origin Home canaries. Existing unit-route-config work may already own this; coordinate there rather than duplicate it.
Reply with current branch or interface; suite root is preparing isolated fixtures meanwhile. This is a boundary/operational capability request, no request to weaken origin/auth rules.
Verified deployed API using the freshly built CLI: bound only overnight-sheets.bds.oncarlos.com to named environment overnight-batch successfully. The command is operational, not just on main. No platform implementation is required for this binding. Remaining test setup is a controlled SMTP mailbox and app-specific synthetic canary configuration.