create-ultimate 1.2.0 → 2.0.0

package/CLAUDE.md

@@ -0,0 +1,12 @@
+# create-ultimate — boundary
+
+Unlisted — sits above tier 5, may import anything below it. Its only real import is
+`@ultimat3/cli` (the sideways edge declared in `scripts/lib/tiers.ts`).
+
+| Rule | Detail |
+|---|---|
+| Scope | argv in, `dispatch({ argv: ['new', ...] })` out. Nothing else. |
+| Templates | none here — they live in `@ultimat3/cli/templates` |
+| Prompts | never; every choice is a flag with a default |
+
+Commands: `bun test`, `bunx tsc --noEmit -p tsconfig.json`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-ultimate",
-  "version": "1.2.0",
+  "version": "2.0.0",
   "description": "bunx create-ultimate myapp — scaffold an Ultimate monorepo",
   "license": "MIT",
   "type": "module",
@@ -22,6 +22,7 @@
   "files": [
     "src",
     "!src/**/*.test.ts",
+    "CLAUDE.md",
     "README.md",
     "LICENSE"
   ],
@@ -33,6 +34,6 @@
     "test": "bun test"
   },
   "dependencies": {
-    "@ultimat3/cli": "1.2.0"
+    "@ultimat3/cli": "2.0.0"
   }
 }

package/src/bin.ts

@@ -2,14 +2,16 @@
 // `bunx create-ultimate myapp`. Delegates to `x new` so there is exactly one scaffolder: a second
 // copy of the templates is a second thing to keep in sync, and it would drift by the first release.
 
+// `writeLine`, not `process.stdout.write`: paired with the `process.exit` below, that combination
+// truncates at the 64KB pipe buffer — and `bunx create-ultimate app` into an EXISTING directory
+// emits one conflict finding per scaffolded file, which is exactly the payload that grows.
+import { writeLine } from '@ultimat3/cli';
 import { createApp } from './index';
 
 const code = await createApp({
   argv: Bun.argv.slice(2),
   cwd: process.cwd(),
-  write: (line) => {
-    process.stdout.write(`${line}\n`);
-  },
+  write: writeLine,
 });
 
 process.exit(code);