create-zerotal 1.7.4 → 1.7.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-zerotal",
-  "version": "1.7.4",
+  "version": "1.7.5",
   "description": "Create a new Zerotal application",
   "license": "MIT",
   "maturity": "stable",

package/src/index.ts

@@ -182,6 +182,14 @@ async function main(): Promise<void> {
     dim(`# then open http://localhost:3000/admin`);
   }
   log('');
+  // Discoverability without a dependency. `@zerotal/arch` exposes the app's own
+  // routes, schema and docs to a coding agent over MCP, and it is genuinely
+  // useful — but it is `beta`, and putting a beta package in every template would
+  // undercut the maturity rule the packages gate enforces. `arch:install` also
+  // writes `.mcp.json` and instruction files into the project, which is an
+  // opinion about someone's toolchain and should stay their choice.
+  log(`${c.gray}  Agent tooling (optional): bun add -d @zerotal/arch && bun zt arch:install${c.reset}`);
+  log('');
   log(`${c.gray}  Docs: https://zerotal.dev${c.reset}`);
   log('');
 }

package/src/scaffold.ts

@@ -13,7 +13,7 @@ export type Template = 'minimal' | 'api' | 'admin' | 'flow' | 'react' | 'vue';
 // "^1.1.0" found for specifier "zerotal"` — the first thing anyone trying the
 // framework saw. `scaffold.test.ts` now asserts the two agree, so CI fails rather
 // than the user's install.
-export const ZT_VERSION = "^1.7.4";
+export const ZT_VERSION = "^1.7.5";
 
 export interface ScaffoldOptions {
   name:     string;