@foldspace_npm/harness 0.1.37 → 0.1.38

package/CLAUDE.md

@@ -516,6 +516,14 @@ save or publish:**
 <committed_paths, comma-separated>`, so your own save is not taken for
 someone else's.
 
+**None of this is said to the human.** No develop, lines of work, pulling,
+merging, conflicts, commits or branches - not in a status line, not when
+something goes wrong. When nobody else saved, say nothing. When someone did,
+one line: *"I brought in changes a teammate saved."* When a file had changes
+both here and in theirs, name the experience in their words: *"A teammate
+also changed the patient table; I kept theirs and put my change on top."*
+Updating the harness is *"updating the Foldspace tools"*, never pulling it.
+
 ## Done, and what you say at the end
 
 A first session is done when the customer has seen one experience answer from
@@ -551,15 +559,27 @@ you offer the second wave:
    again. If it works, invite them to try it in that window (a reload takes
    it off dev), and run `npx foldspace attach --daemon` before you build
    anything else. If `published` says this window cannot show dev, say so in
-   one sentence, attach again, and stop at step 1.
+   one sentence, attach again, and do not offer production yourself - but
+   publish it when the human asks (below).
 3. Once the dev check passed, ask before publishing for their users:
    *"Shall I publish it for your users?"* On a yes, publish to production. On a not yet, it stays on dev:
    say so in one line and carry on.
 
-Steps 2 and 3 need a site that loads this agent by itself. If you attached
-with `--bootstrap` or `--replace`, it does not yet: do step 1, keep attach
-running, and give the answer below for the rest - their site loading the agent
-is the step the Foldspace team does with them.
+**Publishing for their users is the human's call, not a step they earn.**
+When they ask for it - at any point, whether or not the dev check ran or
+could run - that is the yes: publish to production the way `repo_read`
+command `instructions` says, in that turn. Do not ask them to confirm again,
+and do not explain the process. When dev was not checked, one line as you
+publish: *"I couldn't check it on dev here, so it goes out as you tried it
+in the test window."* Only a refusal from the Foldspace tools stops it (below).
+
+Step 2 needs a site that loads this agent by itself. If you attached with
+`--bootstrap` or `--replace`, it does not yet: do step 1, keep attach
+running, and do not offer production yourself - their site loading the agent
+is the step the Foldspace team does with them. When the human asks for
+production anyway, publish it (above), and add one line: *"Your users will
+see it once your site loads the agent - that's the step the Foldspace team
+does with you."*
 
 A save refused because someone saved after you read is not final: pull again
 (**Several builders, one agent**), put your change on top and save. Any other refusal from the Foldspace tools

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@foldspace_npm/harness",
-  "version": "0.1.37",
+  "version": "0.1.38",
   "description": "Build and verify portable Foldspace action artifacts against a live app.",
   "type": "module",
   "bin": {