@solcreek/cli 0.4.22 → 0.4.23

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # @solcreek/cli
 
+## 0.4.23
+
+### Fixes / DX
+
+- **`creek init` help now lists what it creates** — creek.toml (project
+  name, build command/output, detected framework) plus a worker/index.ts
+  example when you add a database — so first-timers know what to expect.
+
+- **`creek doctor --json` prints a one-line summary to stderr** when a human
+  is watching, instead of only a wall of JSON. stdout stays pure JSON for
+  agents and pipes; CI / redirected runs stay silent.
+
+- **The two SQLite doctor findings cross-reference each other.** A project
+  with both better-sqlite3 and Prisma no longer reads as two unrelated
+  problems — each notes it's the same Cloudflare-Workers SQLite migration.
+
+- **`creek db/storage/cache attach --to` shows a value placeholder** in its
+  usage (`--to=<project>`) instead of a bare `--to`.
+
 ## 0.4.22
 
 ### Fixes / DX

package/dist/commands/doctor.js

@@ -55,6 +55,15 @@ export const doctorCommand = defineCommand({
         const ctx = buildDoctorContext(cwd);
         const report = runDoctor(ctx);
         if (jsonMode) {
+            // A one-line human summary on stderr so stdout stays pure JSON for
+            // agents/pipes, while a person who pipes this in a terminal isn't
+            // staring at a wall of JSON. Only when stderr is a TTY (a human is
+            // watching) — fully-redirected/CI runs stay silent.
+            if (process.stderr.isTTY) {
+                const { error, warn, info } = report.summary;
+                const counts = `${error} error${s(error)}, ${warn} warning${s(warn)}, ${info} info`;
+                process.stderr.write(`creek doctor: ${report.ok ? "ok" : "issues found"} — ${counts}\n`);
+            }
             jsonOutput({
                 ok: report.ok,
                 cwd,

package/dist/commands/init.js

@@ -11,7 +11,7 @@ import { ensureGitignoreEntries } from "../utils/gitignore.js";
 export const initCommand = defineCommand({
     meta: {
         name: "init",
-        description: "Initialize a new Creek project (or register a self-host creekd via --adopt / --hostkey-fingerprint)",
+        description: "Initialize a new Creek project — writes creek.toml (project name, build command/output, detected framework) and, if you add a database, a worker/index.ts example. Or register a self-host creekd via --adopt / --hostkey-fingerprint.",
     },
     args: {
         name: {

package/dist/commands/resource-cmd.js

@@ -80,7 +80,7 @@ export function createResourceCommand(opts) {
         meta: { name: "attach", description: `Attach a ${label} to a project under the given ENV var name` },
         args: {
             name: { type: "positional", description: `${label} name (as shown by \`creek ${cmdName} ls\`)`, required: true },
-            to: { type: "string", description: "Project slug to attach to", required: true },
+            to: { type: "string", description: "Project slug to attach to", required: true, valueHint: "project" },
             as: { type: "string", description: `ENV var name (uppercase, default: ${defaultBinding})`, default: defaultBinding },
             ...globalArgs,
         },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@solcreek/cli",
-  "version": "0.4.22",
+  "version": "0.4.23",
   "description": "CLI for the Creek deployment platform",
   "type": "module",
   "main": "./dist/index.js",
@@ -33,7 +33,7 @@
     "esbuild": "^0.25.0",
     "smol-toml": "^1.3.1",
     "ws": "^8.20.0",
-    "@solcreek/sdk": "0.4.10"
+    "@solcreek/sdk": "0.4.11"
   },
   "devDependencies": {
     "@testing-library/dom": "^10.4.1",