staysfixed 0.11.0 → 0.12.0

package/src/v2/journeys/record.js

@@ -35,6 +35,18 @@ import path from 'node:path';
 /** The shape of a journeys file on disk. Version it, because a format nobody versioned is a format nobody can change. */
 export const JOURNEY_FILE_VERSION = 2;
 
+/**
+ * Where recordings live, relative to the project.
+ *
+ * One name, because three readers used to spell it out for themselves — the gatherer, the
+ * check path and the recording command — and three copies of a folder name is three chances
+ * for a recording to be written where nothing looks for it, which reads afterwards exactly
+ * like a recording that was never made.
+ *
+ * It is committed, not ignored: a recording is the promise, not the evidence.
+ */
+export const RECORDINGS_DIR = path.join('.staysfixed', 'journeys');
+
 // ---------------------------------------------------------------------------
 // Keeping secrets out
 // ---------------------------------------------------------------------------

package/src/v2/mcp/tools.js

@@ -493,13 +493,13 @@ export function toolDefinitions() {
           journeys: {
             type: 'string',
             description:
-              "Where the steps come from. 'code' is the default and needs nothing: each adapter reads your source and offers what it finds - routes, commands, screens, message channels. 'suite' walks the project's own test suite as well: each test file runs twice inside the scratch copy, every check is reported by name, and it stops after 90 seconds naming each file it did not reach. It catches breaks nothing else can - a rounding change the product's own output never shows. It is opt-in because running a stranger's whole suite twice on every check is not something to do by default. You can also pass a path to a journeys file naming steps by hand. 'recorded' (replay a recorded session) is written and not yet wired into a run: ask for it and it says so rather than checking something else.",
+              "Where the steps come from. 'code' is the default and needs nothing: each adapter reads your source and offers what it finds - routes, commands, screens, message channels. 'suite' walks the project's own test suite as well: each test file runs twice inside the scratch copy, every check is reported by name, and it stops after 90 seconds naming each file it did not reach. It catches breaks nothing else can - a rounding change the product's own output never shows. It is opt-in because running a stranger's whole suite twice on every check is not something to do by default. 'recorded' replays the sessions somebody recorded with `staysfixed record` and kept in .staysfixed/journeys - the only source that knows which four screens a person actually opens every morning, which reading the source cannot work out. You can also pass a path to a journeys file naming steps by hand.",
           },
           surface: {
             type: 'string',
-            enum: ['auto', 'cli', 'library', 'server', 'web', 'electron', 'android', 'ios'],
+            enum: ['auto', 'cli', 'library', 'server', 'web', 'electron', 'android', 'ios', 'extension'],
             description:
-              "What kind of product to aim at. Default 'auto', which uses the settings. 'web' opens the page in a browser of the tool's own — never yours — and reads what the screen says each control is and does. 'electron' opens the desktop app with its own scratch data folder and drives it over its own debugging port. 'android' installs the APK on a virtual device; 'ios' boots the built app on a simulator. Aim it at something this copy or this machine cannot drive and it refuses by name rather than checking something else and reporting that.",
+              "What kind of product to aim at. Default 'auto', which uses the settings. 'web' opens the page in a browser of the tool's own — never yours — and reads what the screen says each control is and does. 'electron' opens the desktop app with its own scratch data folder and drives it over its own debugging port. 'android' installs the APK on a virtual device; 'ios' boots the built app on a simulator. 'extension' loads a browser extension into a throwaway browser: its manifest is read as a contract, its popup and options pages are walked like any other page, and what its content scripts do to somebody else's page is measured by opening that page with the extension and without it and comparing the difference — point 'extension.dir' in the settings at the folder you would load unpacked. Aim it at something this copy or this machine cannot drive and it refuses by name rather than checking something else and reporting that.",
           },
           at: {
             type: 'string',
@@ -934,19 +934,12 @@ async function toolCheck(ctx, input) {
   const limit = positive(input.limit) ?? DEFAULT_LIMIT;
   const offset = positive(input.offset) ?? 0;
 
-  // A value the engine does not understand must be refused BY NAME, never passed down.
-  //
-  // `suite` is now wired and reaches the harvest. `recorded` is still written and called by
-  // nothing, so passing it down would reach the engine as the name of a FILE and come back as
-  // "there is no journeys file at .../recorded" — an error that sends an agent looking for a
-  // file it never asked for. Refusing it by name and saying why is the honest answer, and a
-  // clean result about the wrong steps would be worse than no result.
+  // Every word this tool offers now reaches something that walks. `suite` harvests the
+  // project's own tests; `recorded` replays the sessions in `.staysfixed/journeys`, which was
+  // written and wired to nothing until 2026-08-31 and was refused here by name because of it.
+  // A project with no recordings comes back BLOCKED from the engine, naming the folder and the
+  // command that makes one - never as a clean result about steps nobody walked.
   const wantedJourneys = text(input.journeys);
-  if (wantedJourneys === 'recorded') {
-    return problem(
-      'Replaying a recorded session is written and not wired into a run yet, so nothing was checked. Leave journeys out to use the steps each adapter reads from your source, pass "suite" to walk your own test suite, or pass the path to a journeys file.'
-    );
-  }
 
   const surface = text(input.surface);
   const at = text(input.at);

package/src/v2/types.js

@@ -39,7 +39,7 @@
 
 /**
  * Where an observation came from, when it matters which platform produced it.
- * @typedef {'cli'|'library'|'server'|'web'|'electron'|'android'|'ios'|'windows'} Surface
+ * @typedef {'cli'|'library'|'server'|'web'|'electron'|'android'|'ios'|'windows'|'linux'|'macos'|'extension'} Surface
  */
 
 // ---------------------------------------------------------------------------

package/src/v2/watch/events.js

@@ -56,9 +56,12 @@ export const SURFACE_WORDS = Object.freeze({
   server: 'Server',
   web: 'Website',
   electron: 'Desktop app',
+  extension: 'Browser extension',
   android: 'Android phone',
   ios: 'iPhone',
   windows: 'Windows app',
+  linux: 'Linux desktop app',
+  macos: 'Mac app',
 });
 
 /**
@@ -71,9 +74,12 @@ export const SURFACE_NOTES = Object.freeze({
   server: 'started on its own port, watched through what it answered',
   web: 'opened in a browser, watched through what the page says its controls do',
   electron: 'launched with its own data folder, watched through the app and its channels',
+  extension: 'loaded into a throwaway browser, watched through its manifest, its own pages, and what it does to somebody else\'s page',
   android: 'installed on an emulator, watched through what is on the screen',
   ios: 'installed on a simulator, watched through what is on the screen',
   windows: 'driven on a real Windows desktop, watched through what is on the screen',
+  linux: 'opened on a real Linux desktop, watched through what the accessibility bus says its controls do',
+  macos: 'opened in the background on a Mac, watched through what is on the screen',
 });
 
 /**