dewctl 0.6.2 → 0.6.3

package/examples/AGENTS.md

@@ -93,10 +93,10 @@ in its dev version; there is no local preview.
 3. **Descriptions:** say what each thing is and what it's made of, in the style's words.
 4. **Style prompt:** set the prompt for the whole game, and the sky.
 
-After each step, upload. While the user runs `npm run dev`, every save uploads by itself and the page reloads;
-otherwise `npx dewctl dev` builds the game, uploads it and prints the link to play it on Dewdrop. Don't run both at
-once: they build into the same folder. Judge the look there, in motion, not from a still frame. The first second is
-plain and grey.
+After each step, upload with `npm run dev`: it builds the game, uploads it and prints the link to play it on
+Dewdrop. Upload when there is something to check, not after every edit. If the user runs `npx dewctl dev --watch`,
+every save uploads by itself, so don't upload as well: both build into the same folder. Judge the look there, in
+motion, not from a still frame. The first second is plain and grey.
 
 You can't see Dewdrop's frames. Ask the user specific questions ("Does the lantern glow?", "What does the sky look
 like?"), or ask for a screenshot. In the dev version, `dewdrop.evaluate` runs code in the game from the browser
@@ -108,8 +108,8 @@ at a time, so you know what each change did.
 
 - `dewdrop.json` connects the folder to the game: its name, the build command, the folder the build writes, and
   the thumbnail ([dewdrop.json](https://alpha.dewdrop.world/docs/dewdrop-json)).
-- `npm run dev` plays the dev version on Dewdrop and uploads it again on every save; `npx dewctl dev` uploads it
-  once. `npx dewctl status` shows both versions. Run `npx dewctl publish` only when the user asks: it puts the game
+- `npm run dev` uploads the game to its dev version on Dewdrop once; `npx dewctl dev --watch` uploads it again on
+  every save. `npx dewctl status` shows both versions. Run `npx dewctl publish` only when the user asks: it puts the game
   in front of players ([commands](https://alpha.dewdrop.world/docs/cli)).
 - `LOOK.md` is the agreed look. In a starter game, README.md says how the game works and why its look works.
   Read both first.

package/examples/starter/package.json

@@ -2,7 +2,7 @@
   "name": "my-game",
   "private": true,
   "type": "module",
-  "scripts": { "dev": "dewctl dev --watch", "build": "vite build" },
+  "scripts": { "dev": "dewctl dev", "build": "vite build" },
   "dependencies": { "three": "0.185.1" },
   "devDependencies": { "vite": "^8" }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dewctl",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "description": "Build and publish three.js games on Dewdrop.",
   "license": "MIT",
   "type": "module",

package/src/command.js

@@ -1,3 +1,3 @@
 // How the developer runs this CLI, for the commands its messages suggest: through npx when npx or an npm script
-// (`npm run dev`, which runs `dewctl dev --watch`) started it, else by name.
+// (`npm run dev`, which runs `dewctl dev`) started it, else by name.
 export const RUN=['exec','run','run-script'].includes(process.env.npm_command)?'npx dewctl':'dewctl';

package/src/main.js

@@ -97,8 +97,8 @@ async function main() {
   if(command==='init') {
     const config=await initProject(process.cwd(),flags.game,flags.template,process.stdin.isTTY&&process.stdout.isTTY?chooseTemplate:undefined);
     const run=RUN;
-    if(config.starter)console.log(`Set up ${config.game} here. Next:\n  npm install\n  ${run} login\n  npm run dev\nnpm run dev builds the game, uploads it to Dewdrop and prints a link to play it, then uploads again on every save; the game is created on Dewdrop the first time.${config.template==='blank'?'':'\nRead README.md: how the game works and why its look works.'}\nAGENTS.md tells coding agents how to work on the game, starting with agreeing its look with you.`);
-    else console.log(`Created dewdrop.json for ${config.game}. Next: ${run} login, then ${run} dev --watch. To make npm run dev play it on Dewdrop, set package.json's dev script to dewctl dev --watch.`);
+    if(config.starter)console.log(`Set up ${config.game} here. Next:\n  npm install\n  ${run} login\n  npm run dev\nnpm run dev builds the game, uploads it to Dewdrop and prints a link to play it; the game is created on Dewdrop the first time. Run it again to upload a change, or ${run} dev --watch to upload on every save.${config.template==='blank'?'':'\nRead README.md: how the game works and why its look works.'}\nAGENTS.md tells coding agents how to work on the game, starting with agreeing its look with you.`);
+    else console.log(`Created dewdrop.json for ${config.game}. Next: ${run} login, then ${run} dev. To make npm run dev upload it to Dewdrop, set package.json's dev script to dewctl dev.`);
     if(!config.starter&&config.buildScript)console.log(`Building for Dewdrop with npm run ${config.buildScript}, which must run vite build with the Dewdrop plugin in vite.config.js.`);
     if(!config.starter&&!config.buildScript)console.log('No build script is in package.json, so dewdrop.json builds with npm run build. Add one that runs vite build with the Dewdrop plugin in vite.config.js, or set "build" in dewdrop.json to your own command.');
     return;

package/src/project.js

@@ -156,7 +156,7 @@ export async function build(project, signal) {
   });
 }
 // The one project shape: a Vite project with the SDK's plugin, which builds for Dewdrop with `npm run build`
-// and plays there with `npm run dev`, which runs `dewctl dev --watch`. A directory holding none of the starter's
+// and uploads to its dev version with `npm run dev`, which runs `dewctl dev`. A directory holding none of the starter's
 // files gets a new game, depending on the SDK and this CLI from npm; one holding any of them has a game of its own
 // and gets dewdrop.json alone, so nothing of it is touched and no new game is left half written.
 const STARTER_FILES=['package.json','src','index.html','vite.config.js'];
@@ -166,7 +166,7 @@ const SDK_RANGE='^0.6.0';
 const CLI_RANGE=`^${JSON.parse(readFileSync(new URL('../package.json',import.meta.url),'utf8')).version}`;
 // The games a new one can start from: Blank, which ships with this CLI, and the starter games in the public
 // starter-templates repository, a folder each, at the commit this release pins.
-const STARTERS={repo:'DewdropLabs/starter-templates',commit:'578fc8e9280b7542ebb2772339da3d2e82f57647'};
+const STARTERS={repo:'DewdropLabs/starter-templates',commit:'32e121d3e9431c38ab24f8e3b92d3f65dc4f9c9d'};
 const TEMPLATES={
   blank:['Blank','a cube and a style prompt, the smallest game'],
   'golden-glide':['Golden Glide','flight over golden-hour countryside, in gouache'],