@sigloch/graphcode-client 1.1.0 → 1.3.0

package/dist/panels.d.ts

@@ -57,6 +57,32 @@ export interface RecommendationsPanel {
     total: number;
 }
 export declare function recommendationsPanel(violations: RuleViolation[], limit?: number): RecommendationsPanel;
+/** One rule's firings, collapsed: the true count plus a NAMED-capped element sample. */
+export interface ViolationGroup {
+    ruleId: string;
+    severity: 'error' | 'warning' | 'info';
+    /** Firings of this rule over the UNCAPPED input — never derived from `elementIds`. */
+    count: number;
+    message: string;
+    fixHint?: string;
+    /** At most `elementLimit` element ids, in input order. */
+    elementIds: string[];
+    /** How many element ids the cap cut off — the cap is never silent. */
+    elementIdsOmitted: number;
+}
+/**
+ * Group violations by ruleId — **group first, cap after**.
+ *
+ * The counting runs over the UNCAPPED violations, never over an already-capped
+ * item list: cap-then-count reports "50×" for a rule that fired 60×, and a wrong
+ * number is worse than a long list (CR-GVE-250). `elementIds` is cut at
+ * `elementLimit` and says via `elementIdsOmitted` how many are missing — a silent
+ * cap is exactly the defect this function exists to prevent.
+ *
+ * Pure projection: the input array is not mutated, and violations without an
+ * `elementId` (graph-scoped findings) still count, they just contribute no id.
+ */
+export declare function groupViolations(violations: RuleViolation[], elementLimit?: number): ViolationGroup[];
 export type Freshness = 'live' | 'stale' | 'absent';
 /**
  * Two artifact kinds with TWO distinct staleness mechanisms (CR-GC-222):

package/dist/panels.js

@@ -27,6 +27,47 @@ export function recommendationsPanel(violations, limit = 5) {
     });
     return { items, total: violations.length };
 }
+/**
+ * Group violations by ruleId — **group first, cap after**.
+ *
+ * The counting runs over the UNCAPPED violations, never over an already-capped
+ * item list: cap-then-count reports "50×" for a rule that fired 60×, and a wrong
+ * number is worse than a long list (CR-GVE-250). `elementIds` is cut at
+ * `elementLimit` and says via `elementIdsOmitted` how many are missing — a silent
+ * cap is exactly the defect this function exists to prevent.
+ *
+ * Pure projection: the input array is not mutated, and violations without an
+ * `elementId` (graph-scoped findings) still count, they just contribute no id.
+ */
+export function groupViolations(violations, elementLimit = 10) {
+    const byRule = new Map();
+    for (const v of violations) {
+        let g = byRule.get(v.ruleId);
+        if (!g) {
+            g = {
+                ruleId: v.ruleId,
+                severity: v.severity,
+                count: 0,
+                message: v.message,
+                fixHint: v.fixHint,
+                elementIds: [],
+                elementIdsOmitted: 0,
+                allElementIds: [],
+            };
+            byRule.set(v.ruleId, g);
+        }
+        g.count += 1;
+        if (v.elementId)
+            g.allElementIds.push(v.elementId);
+    }
+    return [...byRule.values()]
+        .sort((a, b) => b.count - a.count)
+        .map(({ allElementIds, ...g }) => ({
+        ...g,
+        elementIds: allElementIds.slice(0, Math.max(0, elementLimit)),
+        elementIdsOmitted: Math.max(0, allElementIds.length - Math.max(0, elementLimit)),
+    }));
+}
 /**
  * The canonical INCOSE-tab artifact catalog (readiness-artifact-model.md §6). Renders are the
  * deterministic CR-GC-220 views; the 5 analysis ids are exactly CR-GC-221's creation keys

package/dist/readiness.js

@@ -31,6 +31,13 @@ const isCodingProfile = (id) => /^(BQ-|ND-)/.test(id);
  * resolves — the Presence/Resolution split contracts documents (R-19/R-20/R-26 declare
  * a binding, RC-01/02/03/04 check it actually resolves on disk). RC-05 (cross-module
  * import drift) has no presence partner; it is module coupling, so it follows R-23.
+ *
+ * CR-SM-262: RC-06 folgt RC-05 aus demselben Grund. Ein Praesenz-Partner kaeme nicht in
+ * Frage — die Regel prueft ausschliesslich `external === true`, und genau diese Knoten sind
+ * von R-20 AUSGENOMMEN ("exempt from the R-20 realRef-binding requirement", ELEMENT_ATTRIBUTES).
+ * Sie loest also keine Praesenzforderung auf, sondern stellt eine eigene: das Paket, auf das
+ * eine externe Bindung zeigt, muss in den dependencies stehen. Ihr Gegenstand ist damit die
+ * Paket-Abhaengigkeit, die groebste Form von Modul-Kopplung — dieselbe Kategorie wie RC-05.
  */
 const RC_PRESENCE_PARTNER = {
     'RC-01': 'R-20', // FUNC realRef → declared symbol
@@ -38,6 +45,7 @@ const RC_PRESENCE_PARTNER = {
     'RC-03': 'R-26', // SCHEMA realRef → declared export
     'RC-04': 'R-26', // SCHEMA realRef parsed at its interface
     'RC-05': 'R-23', // cross-module import the graph does not document
+    'RC-06': 'R-23', // external binding on a package the consumer does not depend on
 };
 /**
  * Phase-Readiness gates (INCOSE technical reviews) → the rules each gate owns.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sigloch/graphcode-client",
-  "version": "1.1.0",
+  "version": "1.3.0",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -37,11 +37,11 @@
     "access": "public"
   },
   "peerDependencies": {
-    "@sigloch/contracts": ">=5 <7",
+    "@sigloch/contracts": ">=5 <10",
     "@sigloch/graph-api-core": ">=5 <6"
   },
   "devDependencies": {
-    "@sigloch/contracts": "^6.0.0",
+    "@sigloch/contracts": ">=6 <10",
     "@sigloch/graph-api-core": "^5.0.0"
   }
 }