Public: anyone can read this; nobody can change it.
coldstart-assert e2e: own the canary under an org (fix E3 — apps must be org-owned) #164
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
The app-E2E's E3 (dispatcher bootstraps the canary → prime PR) fails on a fresh platform: The e2e generates the canary under the plat user, but createapp now enforces org ownership (the org-is-the-unit model, mcp 0.39.7). The dispatcher refuses the user-owned app, retries once, gives up → no prime PR → E3 fails.
shipped merged
Sign in to join this conversation.
new above
offline
The app-E2E's E3 (dispatcher bootstraps the canary → prime PR) fails on a fresh platform:
The e2e generates the canary under the
platuser, butcreate_appnow enforces org ownership (the org-is-the-unit model, mcp 0.39.7). The dispatcher refuses the user-owned app, retries once, gives up → no prime PR → E3 fails. This is not Azure-specific — it's the sharedcoldstart-assert.sh --e2econtract, so the nightly k3d e2e would fail identically against the current platform.Fix:
E2E_OWNERis now the app-owning org (defaulte2e-apps), created via the Forgejo API before generate (idempotent); the template still lives underE2E_TEMPLATE_OWNER(plat). All app-path references (generate owner, PR polling, NS, prodHost) use the org; the template path uses the template owner.Proven live on a germinated Azure platform before shipping: org created (201) → canary generated (201) →
opened prime PR repo=e2e-apps/orgtest pr=1→run queued role=builder(create_app succeeded, builder building). E3 → E4 confirmed working.🤖 Generated with Claude Code