fix(code): App-project publishing key, route config; Kairo and Code E2E
Radin committed
- Author
- Radin · radin@coline.appOct 1, 2026 at 05:01
- Committer
- Radin · radin@coline.appOct 1, 2026 at 05:01
- Parents
- b81821d28aa8
fix(code): App-project publishing key, route config; Kairo and Code E2E
Found by the new Code app-project E2E (17/17 after these):
- The Code runtime reserves the COLINE_ env prefix, so storing the
publishing key as COLINE_API_KEY failed. It is now APP_PUBLISH_API_KEY
/ APP_PUBLISH_BASE_URL; Publish maps them onto the CLI's variables in
the shell for that one command (names only in the command text).
- Provisioning minted the API key before storing it, so any storage
failure leaked a live key. The key is revoked if storing fails, and
deleting an App project now revokes its key in the same transaction.
- The coline-app routes exported `runtime`, which Cache Components
rejects (it broke the build and every dev route).
New E2E, as package scripts:
- `pnpm apps:verify-kairo` (scripts/e2e/kairo-apps.ts): on GPT-6 Luna,
Kairo runs an installed app's job and turns "build me an app" into a
build_coline_app link; plus ranking with 150 installed tools. 12/12.
- `pnpm apps:verify-code-app` (scripts/e2e/code-app-project.ts):
provisioning, setup, preview config, agent instructions, the key's
scope, reuse and revocation, and Publish without a computer. 17/17.
Docs: public pages live at /apps/public/{workspace}/{app}; the full-stack
guide and readiness doc record what ran against the dev database and
what is still open.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>1 file changed+1−1