@descryy/core 0.1.1 → 0.3.0

package/dist/store/schema.js

@@ -77,11 +77,13 @@ export const DERIVED_TABLES = [
 ];
 /**
  * Cannot be regenerated: a run that witnessed an edge fire is gone once the
- * process exits, and a human's correction of a wrong edge is not in the source
- * at all. These survive every rebuild.
+ * process exits, a run that executed a test is gone the same way, and a human's
+ * correction of a wrong edge is not in the source at all. These survive every
+ * rebuild.
  */
 export const EARNED_TABLES = [
     "observed_edges",
+    "observed_tests",
     "edge_corrections",
     "incident_links",
     "pr_scopes",
@@ -264,6 +266,44 @@ CREATE TABLE IF NOT EXISTS observed_edges (
   PRIMARY KEY (edge_id, run_id)
 ) STRICT;
 
+-- Which tests actually ran, and what happened. The coverage axis — AI layer §20's
+-- "Verification status" — a different question from confidence, needing a
+-- different carrier.
+--
+-- Earned for the same reason as observed_edges, one step over: nothing in the
+-- source says which tests executed, so a rebuild that dropped this would turn
+-- "what I actually verified" silently back into "what might be affected".
+--
+-- Not an edge, deliberately. A test-runner's evidence carries no stack, so an
+-- observed test names exactly one node — its own TEST_CASE — and pairing it with
+-- a function it merely co-occurred with would mint an edge from temporal
+-- coincidence. That is why this is a table and not a promotion of a TESTS edge
+-- to R4; see DEC-NEXT-test-run-coverage-has-no-carrier.md.
+--
+-- (node_id, run_id) is the identity: two runs of one test are two facts, while a
+-- retry inside one run is the same fact re-observed, so the latter updates in
+-- place. Within-run retries are therefore not distinguishable here — a disclosed
+-- limit, not an oversight; this table is a coverage carrier, not a flake detector.
+CREATE TABLE IF NOT EXISTS observed_tests (
+  node_id        TEXT NOT NULL,
+  run_id         TEXT NOT NULL,
+  qualified_name TEXT NOT NULL,
+  outcome        TEXT NOT NULL,         -- 'passed' | 'failed' | 'skipped'
+  -- REAL, not INTEGER, and this was an INTEGER until a real run proved it could
+  -- not be. Runners report fractional milliseconds — node:test emits 2.316958 —
+  -- and a STRICT table refuses that value outright, so every write failed on
+  -- first contact with an actual suite while the unit tests, which all passed
+  -- integer literals, stayed green. Rounding was the other option and is worse:
+  -- sub-millisecond tests are ordinary here, and 0.36 rounded to 0 reads as
+  -- "instant", the same falsehood the null-rather-than-zero rule below refuses.
+  duration_ms    REAL,
+  commit_sha     TEXT NOT NULL,
+  observed_at    INTEGER NOT NULL,
+  PRIMARY KEY (node_id, run_id)
+) STRICT;
+
+CREATE INDEX IF NOT EXISTS idx_observed_tests_run ON observed_tests(run_id);
+
 -- §11B.5. A human said an edge was wrong, or runtime contradicted it. Feeding
 -- this back is how precision improves; losing it repeats the same false claim.
 CREATE TABLE IF NOT EXISTS edge_corrections (

package/dist/store/schema.js.map

@@ -1 +1 @@
-{"version":3,"file":"schema.js","sourceRoot":"","sources":["../../src/store/schema.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgDG;AAEH,OAAO,EAAE,cAAc,EAAE,MAAM,aAAa,CAAC;AAE7C;;;;;GAKG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAAG,CAAC,CAAC,CAAC,4CAA4C;AAEhF;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,cAAc,CAAC,OAAO,CAAC,GAAG,EAAE,EAAE,CAAC,CAAC;AAE9D;;GAEG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG;IAC5B,OAAO;IACP,OAAO;IACP,iBAAiB;IACjB,aAAa;IACb,YAAY;IACZ,cAAc;CACN,CAAC;AAEX;;;;GAIG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG;IAC3B,gBAAgB;IAChB,kBAAkB;IAClB,gBAAgB;IAChB,WAAW;CACH,CAAC;AAKX;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,YAAY;IACZ,iBAAiB;IACjB,OAAO;IACP,OAAO;IACP,aAAa;IACb,cAAc;CAC4B,CAAC;AAE7C,MAAM,CAAC,MAAM,UAAU,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyNzB,CAAC"}
+{"version":3,"file":"schema.js","sourceRoot":"","sources":["../../src/store/schema.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgDG;AAEH,OAAO,EAAE,cAAc,EAAE,MAAM,aAAa,CAAC;AAE7C;;;;;GAKG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAAG,CAAC,CAAC,CAAC,4CAA4C;AAEhF;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,cAAc,CAAC,OAAO,CAAC,GAAG,EAAE,EAAE,CAAC,CAAC;AAE9D;;GAEG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG;IAC5B,OAAO;IACP,OAAO;IACP,iBAAiB;IACjB,aAAa;IACb,YAAY;IACZ,cAAc;CACN,CAAC;AAEX;;;;;GAKG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG;IAC3B,gBAAgB;IAChB,gBAAgB;IAChB,kBAAkB;IAClB,gBAAgB;IAChB,WAAW;CACH,CAAC;AAKX;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,YAAY;IACZ,iBAAiB;IACjB,OAAO;IACP,OAAO;IACP,aAAa;IACb,cAAc;CAC4B,CAAC;AAE7C,MAAM,CAAC,MAAM,UAAU,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+PzB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@descryy/core",
-  "version": "0.1.1",
+  "version": "0.3.0",
   "type": "module",
   "description": "Descry graph engine: storage, graph builder, query layer, traversal, diff scoping, git source, MCP server.",
   "license": "MIT",
@@ -24,6 +24,6 @@
     "build": "tsc -b"
   },
   "dependencies": {
-    "@descryy/ir": "0.1.1"
+    "@descryy/ir": "0.3.0"
   }
 }