@thehammer/template-verification 0.2.20 → 0.2.22

package/dist/types.d.ts

@@ -8,12 +8,16 @@
  * entry is a {@link DataPointMeta} describing that one field's verification state.
  */
 /**
- * Status bucket derived from the integer 1-5 confidence (orthogonal to discrepancy),
- * plus 'failed' (SG-189) — a distinct extraction/citation-correction OUTCOME, not a
- * confidence bucket. 'failed' is resolved from the extracted candidate's `state`
- * field, never from bucketing a confidence integer.
+ * What a machine value's confidence mark shows: one of the five levels of the
+ * operator's scale (SG-843 — the SAME five the Demand Desk draws, from the same
+ * `@danxbot/ui` source), `"unrated"` when no rating was recorded, or `"failed"`
+ * (SG-189) — a distinct extraction/citation-correction OUTCOME, not a level,
+ * resolved from the extracted candidate's `state` and never from its confidence.
+ *
+ * Replaced the three buckets high/medium/low (SG-901): a 4 and a 5 were
+ * identical in the letter while the screen beside it drew them differently.
  */
-export type VerificationStatus = "high" | "medium" | "low" | "unverifiable" | "failed";
+export type ConfidenceState = 1 | 2 | 3 | 4 | 5 | "unrated" | "failed";
 /** The winning candidate key for a resolved data point, or `none` when no candidate exists. */
 export type ResolvedSource = "override" | "extracted" | "claim" | "none";
 /** The basis a user picked when saving an override. */
@@ -139,12 +143,21 @@ export interface Correction {
 /**
  * The extracted (pipeline) candidate — carries provenance: confidence, reasoning, citation.
  *
- * SG-392: the host's BASE render (`data.__meta`) ships only `value`/`confidence`/
+ * SG-392: the host's BASE render (`data.__meta`) ships only `value`/`source`/`confidence`/
  * `state` plus the two `_count` integers below (`sources`/`history` are `undefined`
- * there) — `reasoning` and `verbatim` (SG-325) ship in both light and full mode, being
- * short per-field strings rather than per-attempt arrays. NOTHING IN THIS LIBRARY FILLS
- * `sources`/`history` IN ANY
- * MORE. They used to be lazy-fetched by the in-letter Inspector dialog, which is
+ * there).
+ *
+ * SG-851: `reasoning` and `verbatim` are `undefined` on the base render too. An earlier
+ * revision of this paragraph said they ship in both light and full mode "being short
+ * per-field strings rather than per-attempt arrays" — that was true when written and stopped
+ * being true when the host measured them at 17% of a real 1.4 MB tree and moved them onto the
+ * same on-demand fetch `sources`/`history` already used. Neither key is retired: the host
+ * serves both from `data-point-sources` for the single field whose detail is open. Both are
+ * declared optional below, so a consumer that reads them off a base-render candidate gets
+ * `undefined` rather than a type error — this library reads NEITHER, and any consumer that
+ * wants them must fetch that field's detail, exactly as it already must for its citations.
+ *
+ * NOTHING IN THIS LIBRARY FILLS `sources`/`history` ANY MORE. They used to be lazy-fetched by the in-letter Inspector dialog, which is
  * deleted; the embedding app reads a data point's full detail against its own
  * session instead. A real production render was shipping every field's
  * full retry history — each carrying its own `sources[]`, each source carrying two

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thehammer/template-verification",
-  "version": "0.2.20",
+  "version": "0.2.22",
   "description": "Read-write verification overlay for rendered template apps — per-data-point confidence, discrepancy, 3-source resolution (override > extracted > claim), inline edit, and a recursive comparison page. Consumes the host's __meta sidecar; fetches nothing.",
   "license": "MIT",
   "type": "module",
@@ -39,6 +39,7 @@
     "vue": "^3.4.0"
   },
   "devDependencies": {
+    "@danxbot/ui": "^7.2.0",
     "@tailwindcss/vite": "^4.0.0",
     "@thehammer/danx-ui": "0.8.20",
     "@vitejs/plugin-vue": "^5.0.0",