@bensandee/tooling 0.72.1 → 0.72.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bensandee/tooling",
-  "version": "0.72.1",
+  "version": "0.72.3",
   "description": "CLI tool to bootstrap and maintain standardized TypeScript project tooling",
   "license": "MIT",
   "repository": {
@@ -51,7 +51,7 @@
     "prettier": "3.9.6",
     "release-it": "21.0.2",
     "tsdown": "0.22.14",
-    "@bensandee/claude-hooks": "0.11.3",
+    "@bensandee/claude-hooks": "0.11.4",
     "@bensandee/forgejo": "0.2.0"
   },
   "scripts": {

package/tooling.schema.json

@@ -546,11 +546,11 @@
       "additionalProperties": false
     },
     "agent": {
-      "description": "agent:daemon behaviour overrides. Opt-in: see agent.autonomy for the interior-autonomy gate.",
+      "description": "agent:start behaviour overrides. Opt-in: see agent.autonomy for the interior-autonomy gate.",
       "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 daemon 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 daemon 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.",
           "type": "boolean"
         },
         "preRunRebase": {
@@ -558,11 +558,11 @@
           "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.",
+          "description": "Whether the agent 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.",
+          "description": "Map this repo's own issue-label names onto the agent'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 agent does not create aliased labels -- the repo owns names the agent did not choose. Priority affects claim order only: it never changes a run's model, effort, or any budget.",
           "type": "object",
           "propertyNames": {
             "type": "string"
@@ -573,7 +573,7 @@
           }
         },
         "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.",
+          "description": "Whether the agent 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"
         }
       },