@mediamonks/canopy-cli 0.7.44 → 0.7.46

package/dist/docs/cli-members.md

@@ -1,12 +1,12 @@
 ---
 title: canopy members
-description: See who is on the project, add people as editors or viewers, and give them app roles.
+description: See who is on the project, add people as managers, editors or viewers, give them app roles, and hand the project over.
 ---
 
 `canopy members` manages the project's roster from a terminal: the same as
 the **Members** card under Settings → Access. See
-[Members and access](https://docs.canopy.website/platform/members-and-access) for what editors and
-viewers can do.
+[Members and access](https://docs.canopy.website/platform/members-and-access) for what managers, editors
+and viewers can do.
 
 ## Usage
 
@@ -17,7 +17,9 @@ canopy members add sam@monks.com --viewer --app-role approver
 canopy members set sam@monks.com --app-role approver --app-role reviewer
 canopy members set sam@monks.com --editor
 canopy members set sam@monks.com --clear-app-roles
+canopy members set sam@monks.com --manager
 canopy members remove sam@monks.com
+canopy members transfer sam@monks.com
 ```
 
 ## Arguments & flags
@@ -27,15 +29,20 @@ directory, or `--project <slug>`) and honor the global `--profile <site>`.
 
 - `list` prints everyone on the project and every pending invite, with their
   Canopy role and app roles. `--json` prints the same as JSON.
-- `add <email>` adds someone as an editor, or a viewer with `--viewer`.
-  Someone who hasn't signed in to Canopy yet gets an invite and joins at their
-  first sign-in. Owner only.
-- `set <email>` changes someone. `--editor` or `--viewer` changes their Canopy
-  role (owner only). `--app-role <slug>` sets their app roles, replacing what
-  they had (repeat it, or separate slugs with commas), and `--clear-app-roles`
-  takes them all away. Editors can change app roles.
+- `add <email>` adds someone as an editor, a viewer with `--viewer`, or a
+  manager with `--manager`. Someone who hasn't signed in to Canopy yet gets an
+  invite and joins at their first sign-in. The owner and managers can add
+  editors and viewers; only the owner adds managers.
+- `set <email>` changes someone. `--manager`, `--editor` or `--viewer` changes
+  their Canopy role: managers switch people between editor and viewer, and only
+  the owner makes or changes a manager. `--app-role <slug>` sets their app
+  roles, replacing what they had (repeat it, or separate slugs with commas),
+  and `--clear-app-roles` takes them all away. Editors can change app roles.
 - `remove <email>` takes someone off the project, or withdraws their invite.
-  Owner only.
+  The owner removes anyone; managers remove editors and viewers.
+- `transfer <email>` hands the project to one of its managers or editors.
+  You stay on as a manager. Owner only; it asks for confirmation unless you
+  pass `--yes`.
 
 `--app-role` takes slugs from [`canopy roles list`](https://docs.canopy.website/cli/roles). The default
 role needs no assigning: everyone has it.

package/dist/docs/cli-repo.md

@@ -1,6 +1,6 @@
 ---
 title: canopy repo
-description: Create, clone and set up the project's git repository on Canopy.
+description: Create, clone and set up the project's git repository on Canopy, or link a GitHub repository so its pushes deploy.
 ---
 
 `canopy repo` manages the project's git repository. A project has at most one: a
@@ -16,6 +16,10 @@ canopy repo create
 canopy repo clone <slug> [folder]
 canopy repo connect
 canopy repo delete [--yes]
+canopy repo link [<host>/<owner/name>] [--ref <branch>] [--staging-ref <branch>]
+canopy repo branches [--ref <branch>] [--staging-ref <branch>|none]
+canopy repo deploys on|off
+canopy repo unlink
 ```
 
 ## Arguments & flags
@@ -41,6 +45,25 @@ the global `--profile <site>` / `CANOPY_PROFILE`.
   type the slug.
   - `--yes` — skip that question.
 
+These set up [CI deploys](https://docs.canopy.website/guides/ci) from GitHub Actions. All of them are
+owner only (or a platform admin):
+
+- `link [<host>/<owner/name>]` — link a GitHub repository outside Canopy, so a
+  push to its live branch deploys the project. With no argument it links the
+  folder's `origin` remote. The host is github.com or this site's GitHub
+  Enterprise (`monks.ghe.com`), which is the default.
+  - `--ref <branch>` — the live branch (default `main`).
+  - `--staging-ref <branch>` — a staging branch, whose pushes deploy to the
+    staging channel only.
+- `branches` — change the live or staging branch, for a linked repository or a
+  Canopy one. `--staging-ref none` removes the staging branch.
+- `deploys on|off` — turn CI deploys on or off without unlinking. Off makes
+  runs skip the deploy with a warning. Deploy tokens are not affected.
+- `unlink` — remove the link.
+
+`show` also prints the repository CI deploys from, both branches and whether
+CI deploys are on.
+
 ## How it works
 
 Setting up a folder (`create`, `clone`, `connect`) does two things:
@@ -54,7 +77,9 @@ for a short-lived token that only works for this repository, keeps it in
 `~/.canopy` for up to an hour, and gets a new one when needed. `canopy logout`
 throws them away.
 
-Pushing doesn't deploy. Run `canopy deploy` for that.
+Pushing doesn't deploy by itself. Run `canopy deploy`, or set up
+[CI deploys](https://docs.canopy.website/guides/ci): a Canopy repository needs no link, but GitHub Actions
+are off on it until a platform administrator turns them on.
 
 ## Examples
 
@@ -84,4 +109,11 @@ canopy repo show --json
 }
 ```
 
+```bash
+canopy repo link --staging-ref develop
+```
+
+Links the GitHub repository this folder's `origin` points at: pushes to `main`
+deploy live, pushes to `develop` deploy to staging.
+
 Read the [git guide](https://docs.canopy.website/guides/git) for the bigger picture.

package/dist/docs/cli-token.md

@@ -3,12 +3,14 @@ title: canopy token
 description: Create, list, and revoke project-scoped deploy tokens for CI and push-to-main deploys.
 ---
 
-`canopy token` manages deploy tokens: standing `cnpy_` bearer credentials that can do exactly one thing — deploy one specific project. You reach for it when setting up CI (typically GitHub Actions deploying on every push to main) so the runner never needs a personal login.
+`canopy token` manages deploy tokens: standing `cnpy_` bearer credentials that can do exactly one thing — deploy one specific project. You reach for it when setting up CI other than GitHub Actions, so the runner never needs a personal login.
+
+GitHub Actions doesn't need a token: link the repository with [`canopy repo link`](https://docs.canopy.website/cli/repo) and pushes deploy with no secret. See [CI deploys](https://docs.canopy.website/guides/ci).
 
 ## Usage
 
 ```bash
-canopy token create --name "GitHub Actions"
+canopy token create --name "Buildkite"
 canopy token list
 canopy token revoke <id>
 ```
@@ -18,7 +20,7 @@ canopy token revoke <id>
 All subcommands resolve the project the usual way — `canopy.json` in the target directory, or `--project <slug>` to override — and honor the global `--profile <site>` / `CANOPY_PROFILE` for which site the token belongs to.
 
 - `create` — mint a new deploy token for the project. Owner only: editors get a clear error and should ask the owner.
-  - `--name <label>` — a label shown in the dashboard, e.g. `"GitHub Actions"`. Optional but recommended so you can tell tokens apart later.
+  - `--name <label>` — a label shown in the dashboard, e.g. `"Buildkite"`. Optional but recommended so you can tell tokens apart later.
 - `list` — show the project's deploy tokens: id, name, creation time, who created them, and when each was last used. Token values are never shown here.
 - `revoke <id>` — delete a token by its id (from `canopy token list`). Deploys using it stop working immediately.
 
@@ -28,17 +30,17 @@ All subcommands resolve the project the usual way — `canopy.json` in the targe
 
 The token belongs to the project rather than to whoever created it, so CI keeps working when that person leaves. It has no fixed expiry but stops working after 90 days without a deploy; `list` shows when each token was last used.
 
-To use it in CI, put the value in the `CANOPY_DEPLOY_TOKEN` environment variable — the CLI checks it before the login token, so `canopy deploy` works on a runner with no `canopy login`. For GitHub Actions, add it as the repo secret `CANOPY_DEPLOY_TOKEN` (`gh secret set CANOPY_DEPLOY_TOKEN`, or Settings → Secrets); pushes to main then deploy via the project's `canopy-deploy.yml` workflow.
+To use it in CI, put the value in the `CANOPY_DEPLOY_TOKEN` environment variable — the CLI checks it first, so `canopy deploy` works on a runner with no `canopy login`. In GitHub Actions a token wins over the linked repository, and keeps working while CI deploys are switched off.
 
 If a deploy fails with a rejected token, it was likely revoked — create a fresh one here or in the dashboard (Settings → Deploy tokens) and update the secret. Losing a token is never a problem: revoke the old id and mint a new one.
 
 ## Examples
 
 ```bash
-canopy token create --name "GitHub Actions"
+canopy token create --name "Buildkite"
 ```
 
-Prints a new `cnpy_` token once, with instructions for storing it as the `CANOPY_DEPLOY_TOKEN` repo secret.
+Prints a new `cnpy_` token once, to store as the CI's `CANOPY_DEPLOY_TOKEN` secret.
 
 ```bash
 canopy token list --project my-app

package/dist/docs/cli.md

@@ -63,9 +63,13 @@ has a full page per command.
 - `canopy ai models` — the AI models and `auto/*` aliases this site offers,
   with prices. Works from any directory; `--json` for agents.
 
-## CI / deploy tokens
+## CI deploys
 
-- `canopy token create` — create a project-scoped deploy token for CI.
+- `canopy repo link` — link the folder's GitHub repository (owner only): pushes
+  to `main` then deploy from GitHub Actions with no secret.
+  `--staging-ref <branch>` adds a branch that deploys to staging only.
+- `canopy repo deploys on|off` — pause or resume CI deploys without unlinking.
+- `canopy token create` — create a project-scoped deploy token for other CI.
   `--name "<label>"` to label it.
 - `canopy token list` — list the project's deploy tokens.
 - `canopy token revoke <id>` — revoke a token.

package/dist/docs/deploy.md

@@ -77,5 +77,6 @@ canopy open
 
 ## Deploying from CI
 
-For automated push-to-main deploys, use a deploy token instead of an interactive
-login — see `canopy docs ci`.
+For automated push-to-main deploys from GitHub Actions, link the repository with
+`canopy repo link` — no secret needed. Other CI uses a deploy token. See
+`canopy docs ci`.

package/dist/docs/index.json

@@ -69,8 +69,8 @@
         },
         {
           "slug": "ci",
-          "title": "CI and deploy tokens",
-          "summary": "Push-to-main deploys using a project-scoped deploy token, and why we recommend deploying from your own machine instead."
+          "title": "CI deploys",
+          "summary": "Deploy on every push from GitHub Actions with no secret — link the repository once. Deploy tokens for other CI."
         },
         {
           "slug": "git",
@@ -162,7 +162,7 @@
         {
           "slug": "platform-members-and-access",
           "title": "Members & access",
-          "summary": "Everything on Canopy sits behind Monks sign-in. Editors manage a project, viewers open it, and your app can hand out its own roles on top."
+          "summary": "Everything on Canopy sits behind Monks sign-in. Editors manage a project, managers also run its members list, viewers open it, and your app can hand out its own roles on top."
         },
         {
           "slug": "platform-feedback",
@@ -284,7 +284,7 @@
         {
           "slug": "cli-repo",
           "title": "canopy repo",
-          "summary": "Create, clone and set up the project's git repository on Canopy."
+          "summary": "Create, clone and set up the project's git repository on Canopy, or link a GitHub repository so its pushes deploy."
         },
         {
           "slug": "cli-template",
@@ -304,7 +304,7 @@
         {
           "slug": "cli-members",
           "title": "canopy members",
-          "summary": "See who is on the project, add people as editors or viewers, and give them app roles."
+          "summary": "See who is on the project, add people as managers, editors or viewers, give them app roles, and hand the project over."
         },
         {
           "slug": "cli-roles",

package/dist/docs/platform-deploys-and-rollbacks.md

@@ -27,9 +27,9 @@ the previous version keeps serving until the new one is complete.
   [deploy guide](https://docs.canopy.website/guides/deploy) for details.
 - **From the dashboard** — on the project's Overview tab, upload a new version
   by dragging in a zip, a folder, or loose files. No command line required.
-- **Automatically from CI** — create a project-scoped deploy token, add it to
-  your repository's secrets, and merging to `main` ships a new version on its
-  own. See [CI and deploy tokens](https://docs.canopy.website/guides/ci).
+- **Automatically from CI** — link the project's GitHub repository once
+  (`canopy repo link`), and every push to `main` ships a new version on its own,
+  with no secret. Other CI uses a deploy token. See [CI deploys](https://docs.canopy.website/guides/ci).
 
 The dashboard's deploy history shows every version with who published it and
 where it came from (CLI, dashboard, or CI).
@@ -90,4 +90,4 @@ Downloads are limited to the project's members; the deploy bundle is your
 source, not the public site.
 
 - [Deploying](https://docs.canopy.website/guides/deploy) — Build commands, canopy.json, and what canopy deploy does step by step.
-- [CI and deploy tokens](https://docs.canopy.website/guides/ci) — Ship a new version automatically on every push to main.
+- [CI deploys](https://docs.canopy.website/guides/ci) — Ship a new version automatically on every push to main.

package/dist/docs/platform-members-and-access.md

@@ -1,6 +1,6 @@
 ---
 title: Members & access
-description: Everything on Canopy sits behind Monks sign-in. Editors manage a project, viewers open it, and your app can hand out its own roles on top.
+description: Everything on Canopy sits behind Monks sign-in. Editors manage a project, managers also run its members list, viewers open it, and your app can hand out its own roles on top.
 ---
 
 Nothing on Canopy is reachable by the anonymous internet. Every project URL
@@ -25,9 +25,14 @@ nobody outside the team can touch its data or settings.
 
 Everyone on a project's roster has one Canopy role:
 
-- **Owner**: the person who created the project. Owners govern it: they add
-  and remove members, decide who is an editor or a viewer, change access
-  settings, and can delete the project.
+- **Owner**: the person who created the project, or who it was handed to.
+  Owners govern it: they add and remove anyone, make people managers, can hand
+  the project over, and can delete it. A project has exactly one owner.
+- **Manager**: everything an editor can do, plus running the members list
+  for editors and viewers. Managers add and invite people, remove them, and
+  switch them between editor and viewer, so the team isn't stuck when the
+  owner is away. They can't make or remove other managers, touch the owner,
+  or delete the project.
 - **Editor**: does the day-to-day work. Editors deploy, roll back, browse and
   edit data, and manage schedules, secrets and app roles. They can't delete
   the project or change who is on it.
@@ -42,7 +47,8 @@ Everyone on a project's roster has one Canopy role:
 
 Open the project's **Settings → Access** page and use the **Members** card.
 Start typing a name or email: colleagues who have signed in to Canopy before
-show up as suggestions. Pick **Editor** or **Viewer** and add them.
+show up as suggestions. Pick **Editor** or **Viewer** (or **Manager**, if
+you're the owner) and add them.
 
 Someone who has never opened Canopy can be added too. Type their full company
 email and choose **Invite by email**. They show up as **invited** and join
@@ -50,10 +56,22 @@ automatically the first time they sign in, whether that's opening the
 project's URL or running `canopy login`. Until then the invite grants nothing.
 Canopy doesn't send them a message, so let them know yourself.
 
-The owner can switch anyone between editor and viewer, remove people, or
-withdraw an invite from the same card. From a terminal,
+The owner and managers can switch people between editor and viewer, remove
+them, or withdraw an invite from the same card. Only the owner can make
+someone a manager or change a manager. From a terminal,
 [`canopy members`](https://docs.canopy.website/cli/members) does the same.
 
+## Handing a project over
+
+When the owner moves on, they can hand the project to someone else. Open
+**Settings → Danger zone → Transfer ownership**, pick one of the project's
+managers or editors, and confirm by typing the project's name. The new owner
+takes over at once, and the previous owner stays on as a manager. From a
+terminal, `canopy members transfer <email>` does the same.
+
+If the owner has already left, ask a platform admin: they can hand any
+project to anyone who has signed in to Canopy.
+
 ## App roles
 
 Many apps need their own permissions: "everyone can look, but only a few
@@ -81,7 +99,8 @@ client work, unfinished things you'd rather not demo by accident. Turn on
 live app is limited to the project's roster, editors and viewers alike:
 
 - Other Monks who open the URL get a "limited to its members" page instead of
-  the app.
+  the app. It names you as the owner, with a button to email you, so they
+  know who to ask for access.
 - The project still appears in the company list. It isn't hidden, just
   closed.
 - Platform admins can still manage the project in the dashboard, but they
@@ -92,7 +111,7 @@ live app is limited to the project's roster, editors and viewers alike:
 Turning it off again is the same toggle.
 
 > **Note:** Members-only gates the **live app**. Management pages (settings, data, deploys) are always for the
-> owner and editors only, whatever this toggle says.
+> owner, managers and editors only, whatever this toggle says.
 
 ## Platform admins and the Admin page
 

package/dist/docs/roles.md

@@ -9,7 +9,7 @@ reads them. Canopy never checks them for you.
 
 ## Two kinds of role
 
-- **Canopy roles** (owner, editor, viewer) are about the project itself: who
+- **Canopy roles** (owner, manager, editor, viewer) are about the project itself: who
   can deploy, see the data, change settings. Viewers can only open the app.
   See [Members and access](https://docs.canopy.website/platform/members-and-access).
 - **App roles** are your app's own labels, like `approver` or `admin`. They

package/dist/{docs-KmN6jD1S.mjs → docs-CtMrMpt1.mjs}

@@ -1,8 +1,8 @@
-import { t as version } from "./package-Bvly8-rB.mjs";
-import { r as siteConfig } from "./site-0i7wAJqg.mjs";
+import { t as version } from "./package-BdNHq8QV.mjs";
+import { r as siteConfig } from "./site-BL5Ik-yj.mjs";
 import { i as latestKnownVersion, r as compareSemver } from "./version-check-CcsA1QjI.mjs";
-import { n as agentHeaders } from "./api-Bl6SG8Oq.mjs";
-import { r as reportErrors } from "./ui-CLnICOne.mjs";
+import { n as agentHeaders } from "./api-DmJrIsE7.mjs";
+import { r as reportErrors } from "./ui-26ETk1n8.mjs";
 import { defineCommand } from "citty";
 import { existsSync, mkdirSync, readFileSync, readdirSync, writeFileSync } from "node:fs";
 import { homedir } from "node:os";

package/dist/{egress-C2amvqmE.mjs → egress-BM4EpLBh.mjs}

@@ -1,6 +1,6 @@
-import { l as resolveProject, o as projectDirArgs } from "./site-0i7wAJqg.mjs";
-import { a as apiRequest, f as withContext } from "./api-Bl6SG8Oq.mjs";
-import { a as unwrap, i as requireTty, r as reportErrors, t as formatDateTime } from "./ui-CLnICOne.mjs";
+import { c as projectDirArgs, d as resolveProject } from "./site-BL5Ik-yj.mjs";
+import { a as apiRequest, m as withContext } from "./api-DmJrIsE7.mjs";
+import { a as unwrap, i as requireTty, r as reportErrors, t as formatDateTime } from "./ui-26ETk1n8.mjs";
 import { defineCommand } from "citty";
 import * as p from "@clack/prompts";
 //#region src/egress.ts

package/dist/{feedback-B5-95neo.mjs → feedback-BXhbxyXI.mjs}

@@ -1,7 +1,7 @@
-import { t as version } from "./package-Bvly8-rB.mjs";
-import { f as tryReadCanopyJson, l as resolveProject, o as projectDirArgs, p as tryResolveProject, r as siteConfig } from "./site-0i7wAJqg.mjs";
-import { a as apiRequest, c as credentials, i as apiDownload, o as apiUpload, s as commonHeaders } from "./api-Bl6SG8Oq.mjs";
-import { r as reportErrors, t as formatDateTime } from "./ui-CLnICOne.mjs";
+import { t as version } from "./package-BdNHq8QV.mjs";
+import { c as projectDirArgs, d as resolveProject, h as tryResolveProject, m as tryReadCanopyJson, r as siteConfig } from "./site-BL5Ik-yj.mjs";
+import { a as apiRequest, c as credentials, i as apiDownload, o as apiUpload, s as commonHeaders } from "./api-DmJrIsE7.mjs";
+import { r as reportErrors, t as formatDateTime } from "./ui-26ETk1n8.mjs";
 import { defineCommand } from "citty";
 import { basename, extname, join } from "node:path";
 import { readFile, writeFile } from "node:fs/promises";
@@ -562,7 +562,7 @@ const watchCommand = defineCommand({
 		} else tryResolveProject({});
 		if (args.since && args.after) throw new Error("Pass --since or --after, not both (--after already says where to resume).");
 		if (args.since && Number.isNaN(Date.parse(args.since))) throw new Error(`--since must be an ISO time such as 2026-10-23T09:00:00Z (got "${args.since}").`);
-		const { apiUrl, token } = credentials();
+		const { apiUrl, token } = await credentials();
 		const controller = new AbortController();
 		const stop = () => controller.abort();
 		process.once("SIGINT", stop);

package/dist/index.mjs

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
-import { t as version } from "./package-Bvly8-rB.mjs";
-import { i as siteHeaderLine, n as setInvocationProfile } from "./site-0i7wAJqg.mjs";
+import { t as version } from "./package-BdNHq8QV.mjs";
+import { i as siteHeaderLine, n as setInvocationProfile } from "./site-BL5Ik-yj.mjs";
 import { a as notifyOfUpdate, o as runRefresh } from "./version-check-CcsA1QjI.mjs";
 import { defineCommand, runMain } from "citty";
 //#region src/index.ts
@@ -63,39 +63,39 @@ const main = defineCommand({
 		description: "canopy — create and deploy vibecoded projects"
 	},
 	subCommands: {
-		login: () => import("./login-CREcZfLH.mjs").then((m) => m.loginCommand),
-		whoami: () => import("./login-CREcZfLH.mjs").then((m) => m.whoamiCommand),
-		logout: () => import("./login-CREcZfLH.mjs").then((m) => m.logoutCommand),
-		create: () => import("./projects-BRG2HnBs.mjs").then((m) => m.createCommand),
-		init: () => import("./projects-BRG2HnBs.mjs").then((m) => m.initCommand),
-		projects: () => import("./projects-BRG2HnBs.mjs").then((m) => m.projectsCommand),
-		delete: () => import("./projects-BRG2HnBs.mjs").then((m) => m.deleteCommand),
-		rename: () => import("./rename-BGKa25Rq.mjs").then((m) => m.renameCommand),
-		dev: () => import("./dev-CUJKgaqJ.mjs").then((m) => m.devCommand),
-		deploy: () => import("./deploy-ExrIeX_m.mjs").then((m) => m.deployCommand),
-		promote: () => import("./deploy-ExrIeX_m.mjs").then((m) => m.promoteCommand),
-		staging: () => import("./staging-_2Js0Fkc.mjs").then((m) => m.stagingCommand),
-		rollback: () => import("./deploy-ExrIeX_m.mjs").then((m) => m.rollbackCommand),
-		download: () => import("./deploy-ExrIeX_m.mjs").then((m) => m.downloadCommand),
-		token: () => import("./token-7vSNuz-X.mjs").then((m) => m.tokenCommand),
-		egress: () => import("./egress-C2amvqmE.mjs").then((m) => m.egressCommand),
-		secrets: () => import("./secrets-BjbIi7Gp.mjs").then((m) => m.secretsCommand),
-		roles: () => import("./roles-BDZaN3vi.mjs").then((m) => m.rolesCommand),
-		members: () => import("./roles-BDZaN3vi.mjs").then((m) => m.membersCommand),
-		schedule: () => import("./schedule-BcqBspn3.mjs").then((m) => m.scheduleCommand),
-		feedback: () => import("./feedback-B5-95neo.mjs").then((m) => m.feedbackCommand),
-		db: () => import("./db-BJJGydgL.mjs").then((m) => m.dbCommand),
-		usage: () => import("./usage-DGGmTwjJ.mjs").then((m) => m.usageCommand),
-		ai: () => import("./ai-FBHTSCLZ.mjs").then((m) => m.aiCommand),
-		open: () => import("./open-Bpz4C2Sr.mjs").then((m) => m.openCommand),
-		browse: () => import("./browse-B8-0dweq.mjs").then((m) => m.browseCommand),
-		docs: () => import("./docs-KmN6jD1S.mjs").then((m) => m.docsCommand),
-		skill: () => import("./skill-DRLniv-I.mjs").then((m) => m.skillCommand),
-		upgrade: () => import("./upgrade-D_yrD7zp.mjs").then((m) => m.upgradeCommand),
-		logs: () => import("./logs-BnrNZvLc.mjs").then((m) => m.logsCommand),
-		mcp: () => import("./mcp-DZdMNTWr.mjs").then((m) => m.mcpCommand),
-		repo: () => import("./repo-DmFs6H9m.mjs").then((m) => m.repoCommand),
-		template: () => import("./project-template-715H_lnu.mjs").then((m) => m.templateCommand)
+		login: () => import("./login-2MW9sGJO.mjs").then((m) => m.loginCommand),
+		whoami: () => import("./login-2MW9sGJO.mjs").then((m) => m.whoamiCommand),
+		logout: () => import("./login-2MW9sGJO.mjs").then((m) => m.logoutCommand),
+		create: () => import("./projects-CnU3194_.mjs").then((m) => m.createCommand),
+		init: () => import("./projects-CnU3194_.mjs").then((m) => m.initCommand),
+		projects: () => import("./projects-CnU3194_.mjs").then((m) => m.projectsCommand),
+		delete: () => import("./projects-CnU3194_.mjs").then((m) => m.deleteCommand),
+		rename: () => import("./rename-BWvERJgA.mjs").then((m) => m.renameCommand),
+		dev: () => import("./dev-BvVlq9np.mjs").then((m) => m.devCommand),
+		deploy: () => import("./deploy-BnRQusjJ.mjs").then((m) => m.deployCommand),
+		promote: () => import("./deploy-BnRQusjJ.mjs").then((m) => m.promoteCommand),
+		staging: () => import("./staging-Dn8kH9cK.mjs").then((m) => m.stagingCommand),
+		rollback: () => import("./deploy-BnRQusjJ.mjs").then((m) => m.rollbackCommand),
+		download: () => import("./deploy-BnRQusjJ.mjs").then((m) => m.downloadCommand),
+		token: () => import("./token-DMCj88A-.mjs").then((m) => m.tokenCommand),
+		egress: () => import("./egress-BM4EpLBh.mjs").then((m) => m.egressCommand),
+		secrets: () => import("./secrets-BIn2RPoe.mjs").then((m) => m.secretsCommand),
+		roles: () => import("./roles-CrYf_8wk.mjs").then((m) => m.rolesCommand),
+		members: () => import("./roles-CrYf_8wk.mjs").then((m) => m.membersCommand),
+		schedule: () => import("./schedule-DvHSSzfR.mjs").then((m) => m.scheduleCommand),
+		feedback: () => import("./feedback-BXhbxyXI.mjs").then((m) => m.feedbackCommand),
+		db: () => import("./db-DpCMc0uz.mjs").then((m) => m.dbCommand),
+		usage: () => import("./usage-Bpz5B1N1.mjs").then((m) => m.usageCommand),
+		ai: () => import("./ai-CWPQiUft.mjs").then((m) => m.aiCommand),
+		open: () => import("./open-DcQSdfx5.mjs").then((m) => m.openCommand),
+		browse: () => import("./browse-BPLWhoFI.mjs").then((m) => m.browseCommand),
+		docs: () => import("./docs-CtMrMpt1.mjs").then((m) => m.docsCommand),
+		skill: () => import("./skill-vzcCD1b4.mjs").then((m) => m.skillCommand),
+		upgrade: () => import("./upgrade-8_pFNTo5.mjs").then((m) => m.upgradeCommand),
+		logs: () => import("./logs-dZMPTJLu.mjs").then((m) => m.logsCommand),
+		mcp: () => import("./mcp-CGmWkGN8.mjs").then((m) => m.mcpCommand),
+		repo: () => import("./repo-C7AXDtFZ.mjs").then((m) => m.repoCommand),
+		template: () => import("./project-template-Dw11151p.mjs").then((m) => m.templateCommand)
 	}
 });
 const quiet = process.argv[2] === "mcp" && process.argv[3] === "serve" || process.argv[2] === "repo" && process.argv[3] === "credential";

package/dist/{local-CIkL7tXP.mjs → local-C9Bi9f3y.mjs}

@@ -1,6 +1,6 @@
-import { r as apiDataRequest } from "./api-Bl6SG8Oq.mjs";
+import { r as apiDataRequest } from "./api-DmJrIsE7.mjs";
 import { a as realtimeRouter, c as META_COLUMNS, l as blobRouter, n as WORKER_ATTEST_HEADER, o as dbRouter, s as hasPrivateNames } from "./src-8vxOBOxW.mjs";
-import { a as rewriteApiPath } from "./dev-Cq98yblV.mjs";
+import { a as rewriteApiPath } from "./dev-BmKeIdMi.mjs";
 import { createRequire } from "node:module";
 import { existsSync, mkdirSync, readFileSync, readdirSync, rmSync, statSync, writeFileSync } from "node:fs";
 import { dirname, join, relative, sep } from "node:path";

package/dist/{login-CREcZfLH.mjs → login-2MW9sGJO.mjs}

@@ -1,6 +1,6 @@
-import { _ as setActiveProfile, b as getBakedProfile, g as readConfigFile, h as listBakedProfiles, m as clearAllProfileTokens, r as siteConfig, v as upsertProfileAuth, x as isProfileId, y as writeConfigFile } from "./site-0i7wAJqg.mjs";
-import { n as agentHeaders } from "./api-Bl6SG8Oq.mjs";
-import { n as openBrowser, r as reportErrors } from "./ui-CLnICOne.mjs";
+import { C as isProfileId, S as getBakedProfile, _ as listBakedProfiles, b as upsertProfileAuth, g as clearAllProfileTokens, r as siteConfig, v as readConfigFile, x as writeConfigFile, y as setActiveProfile } from "./site-BL5Ik-yj.mjs";
+import { n as agentHeaders } from "./api-DmJrIsE7.mjs";
+import { n as openBrowser, r as reportErrors } from "./ui-26ETk1n8.mjs";
 import { n as clearRepoTokenCache } from "./repo-credential-CNDRM-tG.mjs";
 import { defineCommand } from "citty";
 import { hostname } from "node:os";

package/dist/{logs-BnrNZvLc.mjs → logs-dZMPTJLu.mjs}

@@ -1,6 +1,6 @@
-import { l as resolveProject, s as projectFlagArgs } from "./site-0i7wAJqg.mjs";
-import { a as apiRequest, f as withContext } from "./api-Bl6SG8Oq.mjs";
-import { r as reportErrors } from "./ui-CLnICOne.mjs";
+import { d as resolveProject, l as projectFlagArgs } from "./site-BL5Ik-yj.mjs";
+import { a as apiRequest, m as withContext } from "./api-DmJrIsE7.mjs";
+import { r as reportErrors } from "./ui-26ETk1n8.mjs";
 import { defineCommand } from "citty";
 //#region src/logs.ts
 /**

package/dist/{mcp-DZdMNTWr.mjs → mcp-CGmWkGN8.mjs}

@@ -1,6 +1,6 @@
-import { t as version } from "./package-Bvly8-rB.mjs";
-import { c as projectUrl, d as stagingUrl, p as tryResolveProject, r as siteConfig } from "./site-0i7wAJqg.mjs";
-import { a as apiRequest, d as noticeRenamesOnly, l as currentSlug, t as ApiError } from "./api-Bl6SG8Oq.mjs";
+import { t as version } from "./package-BdNHq8QV.mjs";
+import { h as tryResolveProject, p as stagingUrl, r as siteConfig, u as projectUrl } from "./site-BL5Ik-yj.mjs";
+import { a as apiRequest, f as noticeRenamesOnly, l as currentSlug, t as ApiError } from "./api-DmJrIsE7.mjs";
 import { t as liveDevServer } from "./dev-server-file-Dk9pk4AR.mjs";
 import { defineCommand } from "citty";
 import { serveStdio } from "@modelcontextprotocol/server/stdio";

package/dist/{migrations-D8NqjC5I.mjs → migrations-BReMlGWP.mjs}

@@ -1,5 +1,5 @@
-import { f as tryReadCanopyJson } from "./site-0i7wAJqg.mjs";
-import { r as apiDataRequest } from "./api-Bl6SG8Oq.mjs";
+import { m as tryReadCanopyJson } from "./site-BL5Ik-yj.mjs";
+import { r as apiDataRequest } from "./api-DmJrIsE7.mjs";
 import { readFileSync, readdirSync } from "node:fs";
 import { join, resolve } from "node:path";
 //#region src/migrations.ts

package/dist/{open-Bpz4C2Sr.mjs → open-DcQSdfx5.mjs}

@@ -1,5 +1,5 @@
-import { c as projectUrl, d as stagingUrl, l as resolveProject, o as projectDirArgs } from "./site-0i7wAJqg.mjs";
-import { n as openBrowser, r as reportErrors } from "./ui-CLnICOne.mjs";
+import { c as projectDirArgs, d as resolveProject, p as stagingUrl, u as projectUrl } from "./site-BL5Ik-yj.mjs";
+import { n as openBrowser, r as reportErrors } from "./ui-26ETk1n8.mjs";
 import { defineCommand } from "citty";
 //#region src/open.ts
 /**

package/dist/{package-Bvly8-rB.mjs → package-BdNHq8QV.mjs}

@@ -1,4 +1,4 @@
 //#region package.json
-var version = "0.7.44";
+var version = "0.7.46";
 //#endregion
 export { version as t };

package/dist/{project-template-Cdr1uwwE.mjs → project-template-BPW_Dgxj.mjs}

@@ -1,6 +1,6 @@
-import { l as resolveProject, o as projectDirArgs } from "./site-0i7wAJqg.mjs";
-import { a as apiRequest, f as withContext } from "./api-Bl6SG8Oq.mjs";
-import { a as unwrap, i as requireTty, r as reportErrors } from "./ui-CLnICOne.mjs";
+import { c as projectDirArgs, d as resolveProject } from "./site-BL5Ik-yj.mjs";
+import { a as apiRequest, m as withContext } from "./api-DmJrIsE7.mjs";
+import { a as unwrap, i as requireTty, r as reportErrors } from "./ui-26ETk1n8.mjs";
 import { defineCommand } from "citty";
 import * as p from "@clack/prompts";
 /** Plain words for the API's template errors. */

package/dist/project-template-Dw11151p.mjs

@@ -0,0 +1,2 @@
+import { a as templateCommand } from "./project-template-BPW_Dgxj.mjs";
+export { templateCommand };