@bensandee/tooling 0.69.0 → 0.71.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bensandee/tooling",
-  "version": "0.69.0",
+  "version": "0.71.0",
   "description": "CLI tool to bootstrap and maintain standardized TypeScript project tooling",
   "license": "MIT",
   "repository": {
@@ -32,7 +32,7 @@
     "@bensandee/common": "0.1.4",
     "@clack/prompts": "^1.7.0",
     "citty": "^0.2.2",
-    "dependency-cruiser": "^18.1.1",
+    "dependency-cruiser": "^18.2.0",
     "json5": "^2.2.3",
     "jsonc-parser": "^3.3.1",
     "picomatch": "^4.0.5",
@@ -41,16 +41,17 @@
   },
   "devDependencies": {
     "@bensandee/config": "0.14.0",
-    "@changesets/cli": "2.31.1",
+    "@changesets/cli": "3.0.1",
     "@release-it/bumper": "8.0.0",
     "@types/node": "24.13.3",
     "@types/picomatch": "4.0.3",
     "commit-and-tag-version": "13.1.2",
+    "oxfmt": "0.57.0",
     "prettier": "3.9.6",
-    "release-it": "21.0.1",
+    "release-it": "21.0.2",
     "tsdown": "0.22.14",
-    "@bensandee/claude-hooks": "0.11.0",
-    "@bensandee/forgejo": "0.1.0"
+    "@bensandee/claude-hooks": "0.11.2",
+    "@bensandee/forgejo": "0.2.0"
   },
   "scripts": {
     "build": "tsdown",

package/tooling.schema.json

@@ -263,6 +263,12 @@
               "type": "number",
               "minimum": 0
             },
+            "floorPp": {
+              "description": "Absolute floor in percent: a total at or above it passes the check regardless of baseline delta, and --update-baseline tracks its current value freely (up or down). Below the floor, the baseline ratchet applies unchanged. Unset means pure ratchet semantics.",
+              "type": "number",
+              "minimum": 0,
+              "maximum": 100
+            },
             "gateOnPullRequests": {
               "description": "Run coverage on PR builds too (default: false; deferred follow-up)",
               "type": "boolean"
@@ -291,9 +297,11 @@
       "type": "object",
       "properties": {
         "enabled": {
+          "description": "Opts into the gate (default false; absent and false alike mean off). `health:check` and `health:summary` print a disabled notice and exit 0 rather than failing while off. Read at generation time as well as at check time, so enabling the gate takes a `repo:sync` as well as a config edit. Dominates `history`.",
           "type": "boolean"
         },
         "src": {
+          "description": "Repo-relative directory roots the measurement is scoped to (default `[\"packages/*/src\"]` when a `packages/` directory exists at the repo root, else `[\"src\"]`). Scopes both the file-tree walk and the dependency-cruiser globs, but not the same way: for the file-tree walk, an entry is expanded against existing directories (one `*` segment only, nothing else). An entry the expander cannot represent at all (`src/**/*.ts`, any other `**`) and one that is well-formed but names no existing directory (a typo, a directory renamed after the config was written) are both reported by name, classified separately, and a run whose file-tree scope resolves to zero source files fails `health:check` before its baseline is read, created, updated, or reset -- `--no-fail-on-empty-src` downgrades that to a notice. For the dependency-cruiser globs the entry is spliced in verbatim, so a `**` entry like `packages/**/src` still cruises and leaves the graph metrics live even though `crowdedDirectories` and the linesOfCode observation see an empty tree. Use `packages/*/src`. The file-tree walk also drops test files, `.d.ts` declarations and `exclude` matches; the dependency-cruiser half drops only `exclude` matches, so a colocated test file or a `.d.ts` under a `src` root still carries graph edges.",
           "type": "array",
           "items": {
             "type": "string"
@@ -307,12 +315,14 @@
           }
         },
         "extensions": {
+          "description": "Leading-dot file extensions that count as source (default `[\".ts\", \".tsx\"]` for a `typescript` stack, `[\".js\", \".jsx\", \".mjs\", \".cjs\"]` for `javascript`, `[]` for `none`). Feeds the walk and the cruiser globs. `[]` means match-all for the walk and switches the linesOfCode observation off; the line counter strips C-family comments, so a non-C-family extension degrades that observation to non-blank lines. `[]` means something different for the cruiser half: the cruiser glob then has no extension group to match, leaving the dependency-cruiser half matching nothing, so on a ts/js stack an explicit `\"extensions\": []` leaves every graph metric reading 0 while the gate passes.",
           "type": "array",
           "items": {
             "type": "string"
           }
         },
         "directoryFileLimit": {
+          "description": "A directory is a crowdedDirectories offender at strictly more than this many measured files sitting directly in it (default 20). The metric counts over-limit directories rather than files, so splitting one crowded directory into two crowded directories makes it worse. 0 makes every directory holding a measured file an offender.",
           "type": "integer",
           "minimum": 0,
           "maximum": 9007199254740991
@@ -340,13 +350,16 @@
           "type": "boolean"
         },
         "history": {
+          "description": "How history is persisted. \"orphan-branch\" (default) has `health:record` append one JSON line per commit to `historyBranch` and has `repo:sync` emit the CI record and status steps; \"none\" turns both off. Does not disable the gate, since the baseline is a committed file. Ignored when `enabled` is false.",
           "type": "string",
           "enum": ["orphan-branch", "none"]
         },
         "historyBranch": {
+          "description": "The orphan branch `health:record` appends to and `health:status` reads (default \"bst/health-metrics\"). Never merges into the default branch and holds no source; separate from `coverage.historyBranch` and must not share a branch with it. `branch:prune`'s built-in never-touch list matches the default name exactly, so a custom name should be named in `branchPrune.exclude` as well.",
           "type": "string"
         },
         "tolerance": {
+          "description": "Slack in offender counts before an increase is a regression: a metric fails when the current count exceeds baseline + tolerance (default 0, so any increase fails). The same allowance applies to every per-module ceiling in health-baseline.json's moduleCeilings, not only the headline metrics. A count, not a percentage -- coverage's percentage-point slack is `coverage.tolerancePp`. Raising it un-tracks every module beneath the new line at once, which is why a justified `exempt` entry is the better answer to one stubborn hub.",
           "type": "integer",
           "minimum": 0,
           "maximum": 9007199254740991
@@ -521,6 +534,17 @@
       },
       "additionalProperties": false
     },
+    "lint": {
+      "description": "bst lint:types (the type-aware oxlint gate) overrides. See lint.strictTypeAware.",
+      "type": "object",
+      "properties": {
+        "strictTypeAware": {
+          "description": "Make `bst lint:types` (the type-aware oxlint gate, backed by oxlint-tsgolint) exit non-zero on any finding while the tooling is still in its report phase (default false; the enforce phase, a later tooling release, exits non-zero unconditionally). A missing oxlint-tsgolint binary is also a hard failure rather than a notice while this is set: arming the gate is what turns a platform gap into a build break, deliberately, because the repo that armed it is the one that asked for it.",
+          "type": "boolean"
+        }
+      },
+      "additionalProperties": false
+    },
     "agent": {
       "description": "agent:daemon behaviour overrides. Opt-in: see agent.autonomy for the interior-autonomy gate.",
       "type": "object",
@@ -533,6 +557,10 @@
           "description": "Attempt a clean-only rebase of the work branch onto the default branch before the implement (execute) phase's container starts (default true). A clean rebase runs the container on the rebased branch; a conflicting one is aborted, reported on the run's ledger comment, and the run still proceeds on the un-rebased branch for a later agent/repair cycle to resolve -- it never fails the run. Set false to skip the attempt entirely for this repo: no fetch, no rebase, no abort, and the branch is worked exactly as cloned.",
           "type": "boolean"
         },
+        "backlog": {
+          "description": "Whether the daemon may self-trigger backlog runs consuming this repo's .agent/findings/ ledger (default: on wherever the ledger exists, which only happens in a repo whose own review loop wrote it). A backlog run opens a pull request that fixes or refutes the pending findings; false disarms it, leaving the ledger to accumulate for a human.",
+          "type": "boolean"
+        },
         "priority": {
           "description": "Map this repo's own issue-label names onto the daemon's four priority levels, e.g. {\"P1\": \"critical\", \"P4\": \"low\"}. The map UNIONS with the built-in priority/<level> names rather than replacing them, and the daemon does not create aliased labels -- the repo owns names the daemon did not choose. Priority affects claim order only: it never changes a run's model, effort, or any budget.",
           "type": "object",
@@ -543,6 +571,10 @@
             "type": "string",
             "enum": ["critical", "high", "normal", "low"]
           }
+        },
+        "triageAnalysis": {
+          "description": "Whether the daemon may route its own agent-note/human-triage-needed issues through the agent/analyze stage (default: off). Unlike agent.backlog, which defaults on, this defaults off: a backlog run batches every pending finding into one container, while triage routing spends one container per issue -- arming it is the reversible direction, not disarming it.",
+          "type": "boolean"
         }
       },
       "additionalProperties": false