@webpieces/nx-webpieces-rules 0.4.726 → 0.4.728

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webpieces/nx-webpieces-rules",
-  "version": "0.4.726",
+  "version": "0.4.728",
   "description": "Nx-specific webpieces validation rules and graph tooling. Bundles all @webpieces rule packages with Nx graph validators and an inference plugin.",
   "type": "commonjs",
   "main": "./src/index.js",
@@ -18,11 +18,11 @@
     "README.md"
   ],
   "dependencies": {
-    "@webpieces/ai-hook-rules": "0.4.726",
-    "@webpieces/code-rules": "0.4.726",
-    "@webpieces/eslint-rules": "0.4.726",
-    "@webpieces/pr-gate": "0.4.726",
-    "@webpieces/rules-config": "0.4.726",
+    "@webpieces/ai-hook-rules": "0.4.728",
+    "@webpieces/code-rules": "0.4.728",
+    "@webpieces/eslint-rules": "0.4.728",
+    "@webpieces/pr-gate": "0.4.728",
+    "@webpieces/rules-config": "0.4.728",
     "madge": "8.0.0"
   },
   "peerDependencies": {

package/src/branch-identity-inputs.d.ts

@@ -14,7 +14,8 @@ import { TargetConfiguration } from '@nx/devkit';
  * unedited config file still hash identically — which is exactly the leak above.
  *
  * DELIBERATELY NOT IN `sharedGlobals`. Putting a branch-varying value there would make EVERY task hash
- * branch-unique and destroy cross-branch cache reuse fleet-wide (CLAUDE.md's measured ~3.2x contention cost
+ * branch-unique and destroy cross-branch cache reuse fleet-wide (`.claude/rules/build-verification.md`'s
+ * measured ~3.2x contention cost
  * is what that buys you). Scoped to the rule-running targets, `build`/`test`/`lint` keep sharing.
  *
  * The two vars are the same pair `getCurrentBranch()` reads, in the same order, so the hash keys off

package/src/branch-identity-inputs.js

@@ -16,7 +16,8 @@ exports.BRANCH_IDENTITY_INPUTS = void 0;
  * unedited config file still hash identically — which is exactly the leak above.
  *
  * DELIBERATELY NOT IN `sharedGlobals`. Putting a branch-varying value there would make EVERY task hash
- * branch-unique and destroy cross-branch cache reuse fleet-wide (CLAUDE.md's measured ~3.2x contention cost
+ * branch-unique and destroy cross-branch cache reuse fleet-wide (`.claude/rules/build-verification.md`'s
+ * measured ~3.2x contention cost
  * is what that buys you). Scoped to the rule-running targets, `build`/`test`/`lint` keep sharing.
  *
  * The two vars are the same pair `getCurrentBranch()` reads, in the same order, so the hash keys off

package/src/branch-identity-inputs.js.map

@@ -1 +1 @@
-{"version":3,"file":"branch-identity-inputs.js","sourceRoot":"","sources":["../../../../../packages/tooling/nx-webpieces-rules/src/branch-identity-inputs.ts"],"names":[],"mappings":";;;AAEA;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACU,QAAA,sBAAsB,GAA+C;IAC9E,EAAE,GAAG,EAAE,iBAAiB,EAAE;IAC1B,EAAE,GAAG,EAAE,kBAAkB,EAAE;CAC9B,CAAC","sourcesContent":["import { TargetConfiguration } from '@nx/devkit';\n\n/**\n * The BRANCH IDENTITY, as nx task-hash inputs. Append these to any CACHED target that can be turned off by\n * `turnOffRuleWhileOnBranch`.\n *\n * WHY A CACHED RULE TARGET NEEDS THEM: the branch hatch makes a rule's verdict depend on which branch you\n * are on, and nothing about the branch is otherwise in the hash. So a hatched branch runs `<project>:ci`\n * green and caches it under hash H; a later, UNRELATED PR that did not touch that project's files hashes to\n * the same H and REPLAYS the hatched green — the relaxation escapes the one branch that opted into it,\n * which is the single property the hatch is supposed to guarantee.\n *\n * `{workspaceRoot}/webpieces.config.json` in `sharedGlobals` (nx.json) is the other half and neither half\n * is sufficient alone: the config file makes EDITING a hatch bust the cache, but two branches sharing one\n * unedited config file still hash identically — which is exactly the leak above.\n *\n * DELIBERATELY NOT IN `sharedGlobals`. Putting a branch-varying value there would make EVERY task hash\n * branch-unique and destroy cross-branch cache reuse fleet-wide (CLAUDE.md's measured ~3.2x contention cost\n * is what that buys you). Scoped to the rule-running targets, `build`/`test`/`lint` keep sharing.\n *\n * The two vars are the same pair `getCurrentBranch()` reads, in the same order, so the hash keys off\n * exactly the values the skip decision keys off. A plain `git rev-parse` is deliberately NOT used: nx\n * inputs must be cheap and pure, and on the CI checkout the vars are the authoritative answer anyway.\n *\n * These are object literals because that is the nx INPUT DSL, not a webpieces data structure — the same\n * form the `{'runtime': ...}` inputs in validation-targets.ts already use.\n */\nexport const BRANCH_IDENTITY_INPUTS: NonNullable<TargetConfiguration['inputs']> = [\n    { env: 'GITHUB_HEAD_REF' },\n    { env: 'WEBPIECES_BRANCH' },\n];\n"]}
+{"version":3,"file":"branch-identity-inputs.js","sourceRoot":"","sources":["../../../../../packages/tooling/nx-webpieces-rules/src/branch-identity-inputs.ts"],"names":[],"mappings":";;;AAEA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACU,QAAA,sBAAsB,GAA+C;IAC9E,EAAE,GAAG,EAAE,iBAAiB,EAAE;IAC1B,EAAE,GAAG,EAAE,kBAAkB,EAAE;CAC9B,CAAC","sourcesContent":["import { TargetConfiguration } from '@nx/devkit';\n\n/**\n * The BRANCH IDENTITY, as nx task-hash inputs. Append these to any CACHED target that can be turned off by\n * `turnOffRuleWhileOnBranch`.\n *\n * WHY A CACHED RULE TARGET NEEDS THEM: the branch hatch makes a rule's verdict depend on which branch you\n * are on, and nothing about the branch is otherwise in the hash. So a hatched branch runs `<project>:ci`\n * green and caches it under hash H; a later, UNRELATED PR that did not touch that project's files hashes to\n * the same H and REPLAYS the hatched green — the relaxation escapes the one branch that opted into it,\n * which is the single property the hatch is supposed to guarantee.\n *\n * `{workspaceRoot}/webpieces.config.json` in `sharedGlobals` (nx.json) is the other half and neither half\n * is sufficient alone: the config file makes EDITING a hatch bust the cache, but two branches sharing one\n * unedited config file still hash identically — which is exactly the leak above.\n *\n * DELIBERATELY NOT IN `sharedGlobals`. Putting a branch-varying value there would make EVERY task hash\n * branch-unique and destroy cross-branch cache reuse fleet-wide (`.claude/rules/build-verification.md`'s\n * measured ~3.2x contention cost\n * is what that buys you). Scoped to the rule-running targets, `build`/`test`/`lint` keep sharing.\n *\n * The two vars are the same pair `getCurrentBranch()` reads, in the same order, so the hash keys off\n * exactly the values the skip decision keys off. A plain `git rev-parse` is deliberately NOT used: nx\n * inputs must be cheap and pure, and on the CI checkout the vars are the authoritative answer anyway.\n *\n * These are object literals because that is the nx INPUT DSL, not a webpieces data structure — the same\n * form the `{'runtime': ...}` inputs in validation-targets.ts already use.\n */\nexport const BRANCH_IDENTITY_INPUTS: NonNullable<TargetConfiguration['inputs']> = [\n    { env: 'GITHUB_HEAD_REF' },\n    { env: 'WEBPIECES_BRANCH' },\n];\n"]}