@bensandee/tooling 0.75.0 → 0.77.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bensandee/tooling",
-  "version": "0.75.0",
+  "version": "0.77.0",
   "description": "CLI tool to bootstrap and maintain standardized TypeScript project tooling",
   "license": "MIT",
   "repository": {
@@ -31,28 +31,29 @@
   },
   "dependencies": {
     "@bensandee/common": "0.1.4",
-    "@clack/prompts": "^1.7.0",
+    "@clack/prompts": "^1.8.1",
     "citty": "^0.2.2",
-    "dependency-cruiser": "^18.2.0",
+    "cross-spawn": "^7.0.6",
+    "dependency-cruiser": "^18.3.1",
     "json5": "^2.2.3",
     "jsonc-parser": "^3.3.1",
     "picomatch": "^4.0.7",
-    "yaml": "^2.9.0",
-    "zod": "^4.4.3"
+    "yaml": "^2.9.1",
+    "zod": "^4.6.5"
   },
   "devDependencies": {
-    "@bensandee/claude-hooks": "0.11.8",
-    "@bensandee/config": "0.14.2",
-    "@bensandee/forgejo": "0.3.0",
-    "@changesets/cli": "3.0.1",
-    "@release-it/bumper": "8.0.0",
-    "@types/node": "24.13.3",
+    "@bensandee/claude-hooks": "0.11.10",
+    "@bensandee/forgejo": "0.4.1",
+    "@changesets/cli": "3.0.3",
+    "@release-it/bumper": "8.0.1",
+    "@types/cross-spawn": "6.0.6",
+    "@types/node": "24.13.5",
     "@types/picomatch": "4.0.3",
-    "commit-and-tag-version": "13.1.2",
-    "oxfmt": "0.65.0",
-    "prettier": "3.9.6",
-    "release-it": "21.0.2",
-    "tsdown": "0.22.14"
+    "commit-and-tag-version": "13.2.1",
+    "oxfmt": "0.68.0",
+    "prettier": "3.9.8",
+    "release-it": "21.1.0",
+    "tsdown": "0.23.0"
   },
   "scripts": {
     "build": "tsdown",

package/tooling.schema.json

@@ -228,6 +228,30 @@
         "additionalProperties": false
       }
     },
+    "versionStamp": {
+      "description": "Files release:assets stamps with the release version before building assets, and verifies afterward. For a repo whose released artifact carries its version somewhere other than package.json (e.g. a WordPress theme's style.css Version: header). Fails loudly when a file's prefix/suffix does not match exactly one line.",
+      "type": "array",
+      "items": {
+        "type": "object",
+        "properties": {
+          "file": {
+            "type": "string",
+            "description": "Path to the file whose version line release:assets stamps, relative to the project root"
+          },
+          "prefix": {
+            "type": "string",
+            "minLength": 1,
+            "description": "Literal string (never a pattern) the target line must start with. Not a regex -- read the output line straight off prefix + version + suffix"
+          },
+          "suffix": {
+            "description": "Literal string (never a pattern) the target line must end with (default: none)",
+            "type": "string"
+          }
+        },
+        "required": ["file", "prefix"],
+        "additionalProperties": false
+      }
+    },
     "postReleaseHook": {
       "description": "Override the post-release hook command (default: POST to POST_RELEASE_HOOK_URL with HMAC-SHA256 auth)",
       "type": "string"
@@ -270,7 +294,7 @@
               "maximum": 100
             },
             "gateOnPullRequests": {
-              "description": "Run coverage on PR builds too (default: false; deferred follow-up)",
+              "description": "When true, checks:run's automatic coverage mode collects coverage on every branch instead of only the default branch, so pull-request and feature-branch runs also produce coverage/coverage-summary.json. An explicit --no-coverage still wins. Coverage recording and history stay default-branch-only. (default: false)",
               "type": "boolean"
             },
             "include": {
@@ -385,6 +409,22 @@
       },
       "additionalProperties": false
     },
+    "egress": {
+      "description": "Egress-audit history configuration, consumed by the bst-agent egress:* commands. There is no enabled key: egress:summary and egress:check read the transcripts root unconditionally, so history: 'none' is the only off-switch, and it disables egress:record alone.",
+      "type": "object",
+      "properties": {
+        "history": {
+          "description": "How egress-audit history is persisted. \"orphan-branch\" (default) has `bst-agent egress:record` append one JSON line per record to `historyBranch`; \"none\" turns off `egress:record` (it prints a disabled notice and exits 0). Unlike `health.history`, there is no `enabled` key gating `egress:summary` / `egress:check` themselves -- those read the current transcripts root unconditionally, so `history: \"none\"` is the only off-switch this block has.",
+          "type": "string",
+          "enum": ["orphan-branch", "none"]
+        },
+        "historyBranch": {
+          "description": "Orphan branch name for egress-audit history (default \"bst/egress-metrics\"). Separate from `coverage.historyBranch` and `health.historyBranch` and must not share a branch with either.",
+          "type": "string"
+        }
+      },
+      "additionalProperties": false
+    },
     "ascii": {
       "description": "ASCII-only gate (bst ascii:check) configuration. Opt-in: set enabled true to scan tracked text files for curated non-ASCII offenders (curly quotes, ellipsis, dashes, box-drawing) and report a suggested ASCII replacement for each hit.",
       "type": "object",
@@ -413,6 +453,13 @@
           "items": {
             "type": "string"
           }
+        },
+        "treatAsProse": {
+          "description": "Path globs (matched the same way as exclude) whose files --fix classifies as prose wholesale regardless of extension, flattening rather than flagging. The opt-back-in for an extension with no dedicated lexical-context classifier where blind flattening is known safe. No built-in defaults.",
+          "type": "array",
+          "items": {
+            "type": "string"
+          }
         }
       },
       "additionalProperties": false
@@ -550,7 +597,7 @@
       "type": "object",
       "properties": {
         "autonomy": {
-          "description": "Opt into interior autonomy (default false). When a phase's latest rationale reports readiness \"ready\" with an empty openQuestions[] and the review phase is clean, the agent applies the existing plan -> implement -> review -> park-at-mergeable advance itself instead of parking for a human. Never applies to the design/spec gate or the final merge from the mergeable terminal -- those always wait on a human. Also arms the trunk-red detector: when this repo's default branch combined status settles red, the agent files a tracking issue naming the failing checks and labels it agent/spec, starting the fix through the ordinary spec/plan/implement/review pipeline.",
+          "description": "Opt into interior autonomy (default false). When a phase's latest rationale reports readiness \"ready\" with an empty openQuestions[] and the review phase is clean, the agent applies the existing plan -> implement -> review -> park-at-mergeable advance itself instead of parking for a human. Never applies to the design/spec gate or the final merge from the mergeable terminal -- those always wait on a human. Also arms the trunk-red detector: when this repo's default branch combined status settles red, the agent files a tracking issue naming the failing checks and labels it agent/spec, starting the fix through the ordinary spec/plan/implement/review pipeline. It also closes that issue, with a comment, if the default branch recovers on its own before a human acts on it.",
           "type": "boolean"
         },
         "preRunRebase": {
@@ -596,7 +643,7 @@
           "maximum": 9007199254740991
         },
         "exclude": {
-          "description": "Branch-name globs added to bst branch:prune's built-in never-touch list (main, changeset-release/*, renovate/*, bst/coverage-metrics, bst/health-metrics, anything with an open PR or protected). Additive only -- there is no key that removes a built-in entry.",
+          "description": "Branch-name globs added to bst branch:prune's built-in never-touch list (main, changeset-release/*, renovate/*, bst/coverage-metrics, bst/health-metrics, bst/egress-metrics, anything with an open PR or protected). Additive only -- there is no key that removes a built-in entry.",
           "type": "array",
           "items": {
             "type": "string"