npm - @sigloch/graph-view-edit - Versions diffs - 0.6.0 → 0.7.2 - Mend

@sigloch/graph-view-edit 0.6.0 → 0.7.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (7) hide show

package/dist/assets/index-Cu_Z807i.css +1 -0
package/dist/assets/index-Dbtyb0kh.js +244 -0
package/dist/index.html +2 -2
package/package.json +5 -5
package/vite.config.js +194 -37
package/dist/assets/index-Bn2YV92M.js +0 -181
package/dist/assets/index-P7N8B6D1.css +0 -1

package/dist/index.html CHANGED Viewed

@@ -4,8 +4,8 @@
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
     <title>graph-view-edit</title>
-    <script type="module" crossorigin src="/assets/index-Bn2YV92M.js"></script>
-    <link rel="stylesheet" crossorigin href="/assets/index-P7N8B6D1.css">
+    <script type="module" crossorigin src="/assets/index-Dbtyb0kh.js"></script>
+    <link rel="stylesheet" crossorigin href="/assets/index-Cu_Z807i.css">
   </head>
   <body>
     <div id="root"></div>

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@sigloch/graph-view-edit",
-  "version": "0.6.0",
+  "version": "0.7.2",
   "description": "React/Vite viewer+editor over @sigloch/graphcode — 12 graph-views + 16 doc-views via a declarative View-Registry, plus an SE-Dashboard sibling route. Reads docs/graph/<member>.graph.json client-side (no 2nd Kuzu handle).",
   "type": "module",
   "bin": {
@@ -17,20 +17,20 @@
     "build": "vite build",
     "preview": "vite preview",
     "prepack": "npm run build",
-    "test": "vitest run"
+    "test": "node scripts/run-tests.mjs"
   },
   "comment:deps": "Runtime = what vite.config.js + bin/gve.mjs load at Node level when serving the prebuilt dist/. The UI libs (react, react-dom, elkjs, @tanstack/react-table, zustand) are bundled INTO dist/ by vite and must stay devDependencies — shipping them would make consumers download the whole UI stack twice.",
   "dependencies": {
-    "@sigloch/contracts": ">=5 <7",
+    "@sigloch/contracts": ">=5 <10",
     "@sigloch/graph-api-core": ">=5 <6",
-    "@sigloch/graphcode-client": ">=1 <2",
+    "@sigloch/graphcode-client": ">=1.3 <2",
     "@vitejs/plugin-react": "^4.3.4",
     "vite": "^5.4.11",
     "zod": "^4.3.6"
   },
   "devDependencies": {
     "@playwright/test": "^1.58.2",
-    "@sigloch/graphcode": "^0.13.0",
+    "@sigloch/graphcode": "^0.18.0",
     "@tanstack/react-table": "^8.20.5",
     "@testing-library/react": "^16.0.1",
     "elkjs": "^0.11.1",

package/vite.config.js CHANGED Viewed

@@ -3,7 +3,7 @@ import { join, basename } from 'node:path';
 import { fileURLToPath } from 'node:url';
 import { defineConfig } from 'vite';
 import react from '@vitejs/plugin-react';
-import { DefaultRuleEngine, SE_DESCRIPTOR } from '@sigloch/graph-api-core';
+import { DefaultRuleEngine, SE_DESCRIPTOR, fromOntologyGraph } from '@sigloch/graph-api-core';
 import { ONTOLOGY_VERSION, RULES_VERSION } from '@sigloch/contracts/se';
 // CR-GC-265: these eight come from the read-side client, not the substrate.
 // They are pure projection plus a node:net socket call — depending on
@@ -18,6 +18,8 @@ import {
   VIEW_FILENAMES,
   ARTIFACT_CATALOG,
   analysisCreationCurrencyProvider,
+  PHASE_GATE_RULES,
+  groupViolations,
   callHost,
   HOST_SOCK_BASENAME,
 } from '@sigloch/graphcode-client';
@@ -159,43 +161,19 @@ function configApiPlugin() {
  * just fetches the JSON like any other static resource.
  */
 /**
- * docs/graph/*.graph.json ⇄ graph-api-core's Graph{nodes,edges} — the ONE
- * definition of this repo's wire format (audit F5). graph-api-core/browser
- * exports only the forward direction (`projectToOntologyGraph`: Graph →
- * OntologyGraph, what graph_export itself uses to WRITE this file) — no
- * inverse is published, so this is that function's exact mirror image,
- * derived by reading its field-lift contract (se-descriptor.ts) rather than
- * re-guessing the shape: status/asil/method/kinds live inside `attributes`
- * (that's where projectToOntologyGraph reads them back out of), created_at/
- * updated_at are GraphNode's own top-level camelCase fields (never inside
- * attributes, or `projectToOntologyGraph` would read them back as '').
+ * docs/graph/*.graph.json → graph-api-core's Graph{nodes,edges} via the
+ * PUBLISHED inverse `fromOntologyGraph` (CR-SM-254) — no hand-rolled mirror.
+ * The previous hand-derived copy lifted exactly four flat keys
+ * (status/asil/method/kinds) into `attributes` and dropped everything else
+ * the exporter writes flat (concept, severity/occurrence/detection,
+ * analysisFreshness, testRefs, …) — the CR-GC-402 "second truth": the
+ * dashboard evaluated a castrated graph and disagreed with graph_readiness.
  * `tests/vite-config-load-graph.test.mjs` pins the round trip against the
  * REAL projectToOntologyGraph, so a drift in either direction fails loud.
  */
 export function loadGraph(file) {
   const json = JSON.parse(readFileSync(file, 'utf8'));
-  const nodes = (json.elements ?? []).map((e) => ({
-    uid: e.id,
-    type: e.type,
-    name: e.name,
-    description: e.description ?? '',
-    createdAt: e.created_at,
-    updatedAt: e.updated_at,
-    attributes: { ...(e.attributes ?? {}), status: e.status, asil: e.asil, method: e.method, kinds: e.kinds },
-  }));
-  const edges = (json.traces ?? []).map((t) => ({
-    sourceId: t.source,
-    targetId: t.target,
-    edgeType: t.type,
-    attributes: {
-      ...(t.attributes ?? {}),
-      category: t.category,
-      label: t.label,
-      weight: t.weight,
-      created_at: t.created_at,
-      verified_at: t.verified_at,
-    },
-  }));
+  const { nodes, edges } = fromOntologyGraph(json);
   // CR-GC-300: graph_export now stamps graphVersion at write time — the live
   // comparison value computeAnalysisCurrency() needs against each analysis
   // artifact's SYS.attributes.analysisFreshness.<id>.graphVersion stamp
@@ -204,10 +182,146 @@ export function loadGraph(file) {
   return { nodes, edges, graphVersion: json.graphVersion ?? 0 };
 }
+/**
+ * Das Recommendations-Teilstück des Dashboard-Payloads (CR-GVE-250):
+ * `recommendationsPanel`s `items`/`total` UNVERÄNDERT — die Items tragen
+ * `topCandidate`, das die Ein-Klick-Fix-Geste (CR-GVE-111) braucht — plus
+ * die Gruppen als zusätzliche Sicht, nicht als Ersatz.
+ *
+ * Die Gruppierung selbst ist seit CR-GVE-259 `groupViolations` aus
+ * @sigloch/graphcode-client — dieselbe Funktion, die die MCP-Fläche unter
+ * `detail:'grouped'` liefert (CR-GC-411). Die frühere lokale Kopie ist
+ * GELÖSCHT, nicht deprecated: eine Aggregation, zwei Konsumenten.
+ */
+export function recommendationsPayload(violations, limit = 50) {
+  return { ...recommendationsPanel(violations, limit), groups: groupViolations(violations) };
+}
+/**
+ * Gate-Blocker als strukturierte Gruppen (CR-GVE-256) — dieselbe Mechanik wie
+ * `recommendationsPayload` (erst gruppieren, dann kappen; Counts aus den
+ * UNGEKAPPTEN Listen), eingeschränkt auf die Regeln, die das Gate besitzt.
+ * Nur error-severity blockiert (warnings/info sind advisory `open` —
+ * readiness.js scorePhaseGate) — deshalb wird hier identisch gefiltert.
+ */
+export function gateBlockerGroups(violations, ruleIds, elementLimit = 10) {
+  return groupViolations(
+    violations.filter((v) => v.severity === 'error' && ruleIds.includes(v.ruleId)),
+    elementLimit,
+  );
+}
+/**
+ * Gate-übergreifende Aggregat-Sicht (CR-GVE-256): EINE Gruppe je ruleId über
+ * alle Gates, mit Gate-Chips — dieselbe Regel wird nicht n-fach gelistet.
+ * Die Gate-Zuordnung ist die VORHANDENE server-seitige Ableitung
+ * (`PHASE_GATE_RULES` aus @sigloch/graphcode-client — dieselbe Tabelle, aus
+ * der readiness.js die Gates scored), kein lokaler zweiter Regel-Katalog.
+ * Impl-Gates besitzen keine Element-Regeln (ihre Blocker sind CRs/Scope/
+ * Creations — strukturell, ohne ruleId) und tauchen deshalb hier nicht auf.
+ */
+export function gateBlockerRollup(violations, gateRules = PHASE_GATE_RULES, elementLimit = 10) {
+  const ruleToGates = new Map();
+  for (const [gateId, ruleIds] of Object.entries(gateRules)) {
+    for (const rid of ruleIds) {
+      if (!ruleToGates.has(rid)) ruleToGates.set(rid, []);
+      ruleToGates.get(rid).push(gateId);
+    }
+  }
+  const owned = violations.filter((v) => v.severity === 'error' && ruleToGates.has(v.ruleId));
+  return groupViolations(owned, elementLimit).map((g) => ({ ...g, gates: ruleToGates.get(g.ruleId) }));
+}
+/**
+ * Das Readiness-Teilstück des Dashboard-Payloads (CR-GVE-256):
+ * `readinessPanel` UNVERÄNDERT als Basis, aber je Gate ersetzt das flache
+ * `blocking`-String-Array durch `blockerGroups` (regelbasierte Blocker,
+ * gruppiert) + `blockingOther` (Milestones/CRs/Creations/Completeness — die
+ * Zeilen ohne ruleId). Das flache Feld wird ENTFERNT, nicht daneben
+ * weitergereicht — sonst rendert es irgendwann wieder jemand (Parallelpfad).
+ */
+export function readinessPayload(report) {
+  const panel = readinessPanel(report);
+  const enrich = (g) => {
+    const ruleIds = PHASE_GATE_RULES[g.id] ?? [];
+    const { blocking, ...rest } = g;
+    return {
+      ...rest,
+      blockerGroups: gateBlockerGroups(report.violations, ruleIds),
+      // Regel-Zeilen sind als Gruppen abgebildet; übrig bleiben die
+      // strukturellen Blocker ("<CR> not done", "milestone … missing",
+      // "<Creation> not performed", "… completeness x/y").
+      blockingOther: blocking.filter((line) => !ruleIds.some((rid) => line.startsWith(`${rid}: `))),
+    };
+  };
+  return {
+    ...panel,
+    phaseGates: panel.phaseGates.map(enrich),
+    implGates: panel.implGates.map(enrich),
+    blockerRollup: gateBlockerRollup(report.violations),
+  };
+}
+/**
+ * Autopilot-Scoreboard (CR-GVE-257) — Präsentations-Aggregation der
+ * `.graphcode/trajectory.jsonl` des Ziel-Repos (Projektion des OperationsLog,
+ * graphcode CR-GC-252). NUR Zeilen zählen aus einer Datei, die graphcode
+ * schreibt — keine eigene Metrik-/Regelberechnung (Grenze, Entscheidung
+ * 2026-08-25; Spiderweb/Konvergenz sind graphcode CR-DRAFT-GC-410).
+ *
+ * Zähl-Semantik entlang der CR-Referenzzahlen (193 / 2 418 / 45 im
+ * graphcode-Repo): applied/rejected über `operation === 'mutate'`;
+ * `opsTotal` = Summe `opCounts` der APPLIED Mutationen (was wirklich durchs
+ * Gate in den Graphen ging); Sessions = distinct `consumerId`; der
+ * Autorschafts-Split zählt die applied Mutationen (wer den Graphen WIRKLICH
+ * geschrieben hat). Violations-Delta: erste → letzte Zeile der Session des
+ * letzten Eintrags. Kaputte Zeilen werden übersprungen, leere Datei → null
+ * (die Karte zeigt „keine Trajektorie vorhanden", kein Crash).
+ */
+export function autopilotStats(jsonlText) {
+  const entries = (jsonlText ?? '')
+    .split('\n')
+    .map((line) => {
+      try {
+        return JSON.parse(line);
+      } catch {
+        return null;
+      }
+    })
+    .filter((e) => e && typeof e === 'object');
+  if (entries.length === 0) return null;
+  const mutates = entries.filter((e) => e.operation === 'mutate');
+  const applied = mutates.filter((e) => e.applied === true);
+  const versions = applied.map((e) => e.graphVersion).filter((v) => typeof v === 'number');
+  const authors = { agent: 0, human: 0 };
+  for (const e of applied) authors[e.consumerType === 'agent' ? 'agent' : 'human'] += 1;
+  const lastSessionId = entries[entries.length - 1].consumerId;
+  const lastSession = entries.filter((e) => e.consumerId === lastSessionId);
+  const zero = { error: 0, warning: 0, info: 0 };
+  return {
+    applied: applied.length,
+    rejected: mutates.length - applied.length,
+    graphVersionFrom: versions.length ? Math.min(...versions) : null,
+    graphVersionTo: versions.length ? Math.max(...versions) : null,
+    opsTotal: applied.reduce((n, e) => n + (typeof e.opCounts === 'number' ? e.opCounts : 0), 0),
+    sessions: new Set(entries.map((e) => e.consumerId)).size,
+    activeDays: new Set(entries.map((e) => String(e.ts ?? '').slice(0, 10)).filter(Boolean)).size,
+    authors,
+    lastSession: {
+      consumerId: lastSessionId,
+      violationsFrom: { ...zero, ...(lastSession[0]?.violations ?? {}) },
+      violationsTo: { ...zero, ...(lastSession[lastSession.length - 1]?.violations ?? {}) },
+    },
+  };
+}
 function dashboardApiPlugin() {
   const cwd = resolveRepoRoot();
   const GRAPH_DIR = join(cwd, 'docs', 'graph');
   const VIEWS_DIR = join(cwd, 'docs', 'views');
+  // CR-GVE-257: die Trajektorie liegt im Ziel-Repo, nicht im Viewer-Repo —
+  // derselbe resolveRepoRoot()-Anker wie GRAPH_DIR/host.sock.
+  const TRAJECTORY_FILE = join(cwd, '.graphcode', 'trajectory.jsonl');
   const engine = new DefaultRuleEngine(SE_DESCRIPTOR.version);
   engine.register(SE_DESCRIPTOR.rules ?? []);
@@ -241,7 +355,18 @@ function dashboardApiPlugin() {
       const staleVsGraph = exists ? statSync(p).mtimeMs < graphMtime : false;
       return { id: entry.id, exists, staleVsGraph };
     });
-    return artifactsPanel(items);
+    // CR-GVE-252: welche Zeile ein Dokument oeffnen kann, entscheidet der
+    // KATALOG, nicht `kind`. 14 der 15 Artefakte haben einen VIEW_FILENAMES-
+    // Eintrag — auch vier der fuenf `analysis`-Creations (conops/fmea/trade/
+    // implplan). Nur `assumption-review` hat keinen. Die frueher hier
+    // implizite Gleichsetzung `kind === 'render'` == "hat eine Datei" war
+    // schlicht falsch (CR-GVE-250 §8.1). Dieselbe Tabelle, gegen die
+    // /api/view-doc aufloest — kein zweites Kriterium im Client.
+    const panel = artifactsPanel(items);
+    return {
+      ...panel,
+      artifacts: panel.artifacts.map((a) => ({ ...a, hasDoc: !!VIEW_FILENAMES[a.id] })),
+    };
   }
   function synthHealth(graph) {
@@ -270,16 +395,48 @@ function dashboardApiPlugin() {
       member: basename(file).replace(/\.graph\.json$/, ''),
       repoRoot: servedRepoRoot(),
       empty: graph.nodes.length === 0,
-      readiness: readinessPanel(report),
-      recommendations: recommendationsPanel(violations, 50),
+      readiness: readinessPayload(report),
+      recommendations: recommendationsPayload(violations, 50),
       artifacts: scanArtifacts(file, graph),
       health: synthHealth(graph),
+      // CR-GVE-257: Repo ohne Trajektorie → null (Karte zeigt den Hinweis).
+      autopilot: existsSync(TRAJECTORY_FILE) ? autopilotStats(readFileSync(TRAJECTORY_FILE, 'utf8')) : null,
       computedAt: new Date().toISOString(),
     };
   }
+  /**
+   * GET /api/view-doc?id=<artifactId> (CR-GVE-250) — der einzige Weg von der
+   * Artefaktzeile des Dashboards zu docs/views/<name>.md: `dist/` liefert
+   * `docs/` nicht aus, ein statischer Link geht also nicht.
+   *
+   * `id` wird AUSSCHLIESSLICH über den Katalog `VIEW_FILENAMES` aufgelöst —
+   * aus der Anfrage wird nie ein Pfad zusammengesetzt, deshalb läuft ein
+   * `../..`-Versuch nicht ins Dateisystem, sondern in den Katalog-Miss (404).
+   * `Object.hasOwn` statt `in`, sonst würden `__proto__`/`constructor` als
+   * Treffer gelten.
+   */
+  function readViewDoc(id) {
+    if (!id || !Object.hasOwn(VIEW_FILENAMES, id)) return null;
+    const file = join(VIEWS_DIR, VIEW_FILENAMES[id]);
+    return existsSync(file) ? readFileSync(file, 'utf8') : null;
+  }
   const middleware = (req, res, next) => {
-    if (req.url !== '/api/dashboard') return next();
+    const url = new URL(req.url ?? '/', 'http://localhost');
+    if (url.pathname === '/api/view-doc') {
+      const markdown = readViewDoc(url.searchParams.get('id'));
+      if (markdown === null) {
+        res.statusCode = 404;
+        res.setHeader('Content-Type', 'application/json');
+        res.end(JSON.stringify({ error: 'unknown view-doc id' }));
+        return;
+      }
+      res.setHeader('Content-Type', 'text/markdown; charset=utf-8');
+      res.end(markdown);
+      return;
+    }
+    if (url.pathname !== '/api/dashboard') return next();
     res.setHeader('Content-Type', 'application/json');
     res.end(JSON.stringify(buildDashboard()));
   };