staysfixed 0.7.0 → 0.7.1

package/CHANGELOG.md

@@ -4,6 +4,21 @@ All notable changes to this project are recorded here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the version
 numbers follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.7.1] — 2026-08-30
+
+Found by installing 0.7.0 from npm into an empty folder and running it the way a
+stranger would, which is the only way this was ever going to be found.
+
+### Fixed
+
+- **`init` asked for a build step on a script that runs straight from source.** A
+  plain Node command-line tool is recorded as "not built", because there is
+  nothing to build — and that was read as "it has not been built yet". So a fresh
+  install told its owner to go and name the command that builds a file sitting
+  right there, in the same breath as offering to run it. Being sent shopping for
+  nothing is the fastest way to make somebody stop reading the page, and this
+  project's README promises it never happens. A test holds it shut.
+
 ## [0.7.0] — 2026-08-30
 
 The release where the front door was found to be locked.
@@ -81,6 +96,11 @@ printed, which is the only way this kind of mistake is ever found.
 - **It reported Docker as present because the command was on the path**, on a
   machine where Docker Desktop was shut and nothing it promises would have worked.
   It asks the engine for its version now.
+- **It said an iPhone app "cannot be done here at all" on a Mac with Xcode and
+  three simulator runtimes on it.** The real reason was that this repository has
+  no iPhone app in it, which is not a limit of the machine. Those two reasons are
+  two different sentences now, and the object carries
+  `surfaces[].notInThisProject` so an agent can tell them apart too.
 - No probe in `doctor` uses a shell variable or a loop any more. One machine in
   this config reaches Windows through an OpenSSH server that hands the command down
   through a second shell, and every `$p` is expanded to nothing before the shell

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "staysfixed",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "Prove that what already worked still works after an agent changed the code. Picture checks, guards for fixed bugs, a pre-release walkthrough, and known-good markers — as a CLI and as an MCP server.",
   "type": "module",
   "license": "MIT",

package/src/v2/init.js

@@ -432,7 +432,17 @@ function productNeeds(product, project) {
   // A command-line program that has to be built before it can be run. This is what a product
   // nothing in package.json names looks like on a fresh clone: the source is there, the
   // program is real, and the file that would be run does not exist yet.
-  if (product.kind === 'cli' && !product.built.found) {
+  //
+  // `built.found === false` is NOT that on its own, and reading it as though it were sent a
+  // plain Node command-line tool's owner shopping for a build step it does not have. A
+  // script that runs straight from source is recorded as `found: false, how: "nothing to
+  // build — it runs from source"`, and this file used to ask a person to "name the command
+  // that builds it" about a file that was sitting right there and that the very same run
+  // had already worked out how to run. Two signals rule it out, and either is enough: the
+  // detector saying there is nothing to build, and a command already worked out for it.
+  const nothingToBuild = /nothing to build/i.test(String(product.built.how ?? ''));
+  const alreadyRunnable = Array.isArray(suggest.commands) && suggest.commands.length > 0;
+  if (product.kind === 'cli' && !product.built.found && !nothingToBuild && !alreadyRunnable) {
     const build = typeof suggest.buildWith === 'string' ? String(suggest.buildWith) : null;
     needs.push({
       what: `${product.name}, built`,