@bensandee/tooling 0.85.0 → 0.86.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bensandee/tooling",
-  "version": "0.85.0",
+  "version": "0.86.0",
   "description": "CLI tool to bootstrap and maintain standardized TypeScript project tooling",
   "license": "MIT",
   "repository": {

package/tooling.schema.json

@@ -94,7 +94,7 @@
             "type": "string"
           },
           "publish": {
-            "description": "Exclude this image from docker:publish while publishDocker stays true (default true).",
+            "description": "The publish decision either way: true keeps an image published -- including one its compose service is declared only in the check overlay, which a later release stops publishing by default -- and false excludes it while publishDocker stays true. Unset means the discovery default, which publishes everything except a check-only image once that rule is enforced.",
             "type": "boolean"
           }
         },
@@ -389,11 +389,11 @@
           "maximum": 9007199254740991
         },
         "exempt": {
-          "description": "Per-metric, per-module reporting suppression, keyed first by metric name (fanInOutliers or fanOutOutliers) then by the repo-relative module path exactly as `health:summary --explain` prints it. Each module maps to a required, non-empty justification string. An exempt module stays fully in the graph -- its edges still count toward every other module's fan-in/fan-out -- and only stops being listed as an outlier for that one metric.",
+          "description": "Per-metric, per-module exemption, keyed first by metric name (fanInOutliers, fanOutOutliers or crowdedDirectories) then by the repo-relative path exactly as `health:summary --explain` prints it: a module path for the two fan metrics, a directory path for crowdedDirectories. Each path maps to a required, non-empty justification string. An exempt module or directory is listed in the summary with its count and reason, carries no ceiling in health-baseline.json, and is counted in no metric -- it is out of the gate, not suppressed inside it. Adding one is a raise: it travels alone in a ceiling-only pull request, never beside code. An exempt module stays fully in the graph -- its edges still count toward every other module's fan-in/fan-out.",
           "type": "object",
           "propertyNames": {
             "type": "string",
-            "enum": ["fanInOutliers", "fanOutOutliers"]
+            "enum": ["fanInOutliers", "fanOutOutliers", "crowdedDirectories"]
           },
           "additionalProperties": {
             "type": "object",