@mediamonks/canopy-cli 0.7.5 → 0.7.7

package/dist/{projects-D2fDeWNU.mjs → projects-C9TBoiW7.mjs}

@@ -30,10 +30,9 @@ const TEMPLATES = [
 	},
 	{
 		id: "worker",
-		label: "React SPA + backend Worker",
-		hint: "adds Hono handlers in worker/ — Phase 2 preview",
-		needsInstall: true,
-		hidden: true
+		label: "React SPA + backend worker",
+		hint: "spa plus server-side handlers in worker/ — for secrets, schedules, external APIs",
+		needsInstall: true
 	}
 ];
 function templatesRoot() {
@@ -134,7 +133,7 @@ const createCommand = defineCommand({
 		if (scaffold && !args.template && process.stdin.isTTY) {
 			const id = unwrap(await p.select({
 				message: "Template",
-				options: TEMPLATES.filter((t) => !t.hidden).map((t) => ({
+				options: TEMPLATES.map((t) => ({
 					value: t.id,
 					label: t.label,
 					hint: t.hint
@@ -142,7 +141,6 @@ const createCommand = defineCommand({
 			}));
 			template = TEMPLATES.find((t) => t.id === id) ?? template;
 		}
-		if (template.hidden) p.log.warn("Per-project Workers are not deployable yet (Phase 2) — `canopy deploy` publishes the frontend only for now.");
 		const targetDir = resolve(slug);
 		if (scaffold && existsSync(targetDir)) throw new Error(`Directory ./${slug} already exists — remove it, or use --no-scaffold to only register.`);
 		const spin = p.spinner();
@@ -241,7 +239,7 @@ const initCommand = defineCommand({
 			if (!args.template && process.stdin.isTTY) {
 				const id = unwrap(await p.select({
 					message: "Template",
-					options: TEMPLATES.filter((t) => !t.hidden).map((t) => ({
+					options: TEMPLATES.map((t) => ({
 						value: t.id,
 						label: t.label,
 						hint: t.hint
@@ -249,7 +247,6 @@ const initCommand = defineCommand({
 				}));
 				template = TEMPLATES.find((t) => t.id === id) ?? template;
 			}
-			if (template.hidden) p.log.warn("Per-project Workers are not deployable yet (Phase 2) — `canopy deploy` publishes the frontend only for now.");
 			scaffoldTemplate(template.id, targetDir, {
 				name: project.name,
 				slug

package/dist/skill/canopy/SKILL.md

@@ -75,10 +75,12 @@ canopy docs            # list all topics
 canopy docs deploy     # print one topic
 ```
 
-Available topics include: `getting-started`, `cli` (full command reference),
-`deploy`, `dev`, `data`, `ci`, `troubleshooting`. Always prefer `canopy docs`
-and `canopy <command> --help` over guessing flags — they are the source of
-truth and never go stale.
+The listing is grouped by section: guides (`getting-started`, `deploy`, `dev`,
+`data`, `ci`, `troubleshooting`, …), platform feature pages (`platform-*`), a
+per-command CLI reference (`cli-<command>`, plus `cli` for the one-page
+overview), and the SDK reference (`sdk-*`). Always prefer `canopy docs` and
+`canopy <command> --help` over guessing flags — they are the source of truth
+and never go stale.
 
 ## Command map (quick orientation — see `canopy docs cli` for detail)
 
@@ -94,6 +96,8 @@ truth and never go stale.
 - Roll back: `canopy rollback`
 - Open the live site: `canopy open`
 - Manage data: `canopy db pull | snapshot | snapshots | restore | migrate`
+- Work bug reports & feedback: `canopy feedback list | show | comment | status | report`
+  — see `canopy docs platform-feedback` for the triage and reporting loops
 - CI credentials: `canopy token create | list | revoke`
 
 ## Custom tables & migrations (devs; Drizzle recommended)
@@ -133,10 +137,10 @@ Prefer **`spa`** the moment either is true — which covers most real projects:
 - **The app will grow.** `spa` is Vite + React + TypeScript, giving components,
   routing, and state a real home; `static` has no build step to organise into.
 
-Use **`worker`** (`--template worker`; hidden from the picker) only when you
-need server-side backend code — e.g. calling an external API with a secret the
-browser can't hold. Per-project Workers are a Phase 2 preview (frontend deploys
-now; `worker/` is picked up once the platform supports it).
+Use **`worker`** when you need server-side backend code — e.g. calling an
+external API with a secret the browser can't hold, or running scheduled jobs.
+It's `spa` plus Hono-style handlers in `worker/`; `canopy deploy` publishes
+the frontend and the worker together.
 
 Non-interactive: `canopy create "My App" --template spa`. **When unsure between
 `static` and `spa`, pick `spa`.**
@@ -149,3 +153,8 @@ Non-interactive: `canopy create "My App" --template spa`. **When unsure between
 - **Deploys are public.** `canopy deploy` makes a version live. Confirm before
   deploying unless the user clearly asked you to.
 - Keep the CLI current: `canopy upgrade` (this also refreshes this skill).
+- **A `canopy` command itself failing?** First rule out user error (re-read
+  `canopy docs troubleshooting` and the command's `--help`). If the platform
+  really misbehaved, check `canopy feedback mine` for a duplicate, then file it:
+  `canopy feedback report "<what happened>" --command "<the command>" --error "<output>"`
+  — it reaches the platform team directly (no `--project` needed).

package/dist/{skill-12Ga-2UT.mjs → skill-DRTg-mJR.mjs}

@@ -1,4 +1,4 @@
-import { t as version } from "./package-yVoO2pq4.mjs";
+import { t as version } from "./package-BNiOibhj.mjs";
 import { n as reportErrors } from "./ui-CpdtK7mt.mjs";
 import { defineCommand } from "citty";
 import { cpSync, existsSync, mkdirSync, rmSync, symlinkSync, writeFileSync } from "node:fs";

package/dist/templates/worker/AGENTS.md

@@ -5,9 +5,6 @@ A Vite + React single-page app plus a per-project backend Worker on
 projects. Everything is served behind company login; there is no
 infrastructure to manage and none should be added.
 
-> On GCP, `canopy deploy` publishes the frontend **and** the `worker/`
-> backend (Cloud Run). Cloudflare WfP upload is still Phase 2.
-
 ## Canopy skill
 
 The full SDK reference (auth, db, blob, ai) and platform guardrails ship as an

package/dist/templates/worker/README.md

@@ -4,14 +4,10 @@ A [Canopy](https://dashboard.thanarie.dev) project — Vite + React with a
 backend Worker (`worker/`). Live (behind company login) at
 https://{{slug}}.thanarie.dev after the first `canopy deploy`.
 
-> Per-project Workers are a Canopy Phase 2 capability: `canopy deploy`
-> publishes the frontend only for now — `worker/` deploys automatically once
-> the platform supports it.
-
 - `npm install` — once, then:
 - `canopy dev` — develop locally against the live platform (real data!)
 - `canopy dev --local [--pull]` — offline sandbox with local data instead
-- `canopy deploy` — build and publish `dist/`
+- `canopy deploy` — build and publish the frontend and the `worker/` backend
 - `AGENTS.md` — project guardrails and skill setup for coding agents
 
 Push-to-main deploys are prepared in `.github/workflows/canopy-deploy.yml`

package/dist/{upgrade-Du6U0xjp.mjs → upgrade-BDaM4M6Y.mjs}

@@ -112,7 +112,7 @@ const upgradeCommand = defineCommand({
 		const spec = `${PACKAGE_NAME}@${args.version ?? "latest"}`;
 		const command = pmCommand(pm);
 		const cmd = installArgs(pm, spec);
-		const { skillInstalled } = await import("./skill-12Ga-2UT.mjs");
+		const { skillInstalled } = await import("./skill-DRTg-mJR.mjs");
 		const refreshSkill = skillInstalled(process.cwd());
 		console.log(`Upgrading via ${command}: ${command} ${cmd.join(" ")}`);
 		await run(command, cmd);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mediamonks/canopy-cli",
-  "version": "0.7.5",
+  "version": "0.7.7",
   "description": "Canopy CLI — create, develop and deploy Canopy projects.",
   "bin": {
     "canopy": "./dist/index.mjs"