@flowrail/init 0.0.11 → 0.0.12

package/dist/hook-install.js

@@ -35,11 +35,22 @@ const INSTALL_NPM_ARGS = ['install', '--save-dev', exports.HOOK_PACKAGE];
  *      be a false positive.
  *   3. Spawns the bin file via `node` with no args. The hook entry
  *      point writes `flowrail-hook: unknown subcommand ...` to stderr
- *      and exits 2 when invoked without `pre-write`/`pre-bash`. We
- *      require both signals. This proves the file is parseable, all
+ *      when invoked without `pre-write`/`pre-bash`. We require that
+ *      message AND the bin name. This proves the file is parseable, all
  *      imports resolve at runtime, and the entry-point code runs to
  *      completion — catching broken shims, syntax errors, missing
  *      runtime deps, or a wrong binary masquerading at the bin path.
+ *
+ *      The EXIT CODE is deliberately accepted as either 0 or 2, because
+ *      hook >=0.0.18 (ADR-019 / PR #309) splits it by event provenance:
+ *      a provable PreToolUse invocation exits 2, everything else exits 0
+ *      so a stale hook can never fail CLOSED on version skew. This
+ *      self-test spawns the bin bare — no PreToolUse stdin — so it takes
+ *      the exit-0 path on >=0.0.18 and the exit-2 path on <=0.0.17.
+ *      Pinning `status === 2` broke `npx @flowrail/init@latest` against
+ *      hook 0.0.18. The two stderr signals, not the exit code, are what
+ *      establish the binary's identity; a silent `exit(0)` imposter still
+ *      fails because it emits neither.
  */
 function buildVerifyNodeScript(pkg, bin) {
     const pkgJson = JSON.stringify(`${pkg}/package.json`);
@@ -56,7 +67,10 @@ function buildVerifyNodeScript(pkg, bin) {
         '}',
         'const binPath = path.resolve(path.dirname(pkgPath), binEntry);',
         "const result = cp.spawnSync(process.execPath, [binPath], { encoding: 'utf8' });",
-        `if (result.status !== 2 || !/unknown subcommand/.test(result.stderr || '') || !new RegExp(${binName}).test(result.stderr || '')) {`,
+        // Accept BOTH of hook's documented unknown-subcommand exit paths:
+        // 2 (provable PreToolUse) and 0 (anything else, >=0.0.18). Identity is
+        // established by the two stderr signals below, not the exit code.
+        `if ((result.status !== 0 && result.status !== 2) || !/unknown subcommand/.test(result.stderr || '') || !new RegExp(${binName}).test(result.stderr || '')) {`,
         "  console.error('binary self-test failed: status=' + result.status + ' stderr=' + (result.stderr || '').slice(0, 300));",
         '  process.exit(2);',
         '}',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flowrail/init",
-  "version": "0.0.11",
+  "version": "0.0.12",
   "description": "One-shot FlowRail installer for Claude Code. Wires PreToolUse hooks, MCP server config, and skill markdown into a tester's repo, then probes the FlowRail server with their bearer.",
   "license": "UNLICENSED",
   "private": false,