@thehammer/template-verification 0.2.20 → 0.2.21
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.
- package/dist/types.d.ts +14 -5
- package/package.json +1 -1
package/dist/types.d.ts
CHANGED
|
@@ -139,12 +139,21 @@ export interface Correction {
|
|
|
139
139
|
/**
|
|
140
140
|
* The extracted (pipeline) candidate — carries provenance: confidence, reasoning, citation.
|
|
141
141
|
*
|
|
142
|
-
* SG-392: the host's BASE render (`data.__meta`) ships only `value`/`confidence`/
|
|
142
|
+
* SG-392: the host's BASE render (`data.__meta`) ships only `value`/`source`/`confidence`/
|
|
143
143
|
* `state` plus the two `_count` integers below (`sources`/`history` are `undefined`
|
|
144
|
-
* there)
|
|
145
|
-
*
|
|
146
|
-
* `
|
|
147
|
-
*
|
|
144
|
+
* there).
|
|
145
|
+
*
|
|
146
|
+
* SG-851: `reasoning` and `verbatim` are `undefined` on the base render too. An earlier
|
|
147
|
+
* revision of this paragraph said they ship in both light and full mode "being short
|
|
148
|
+
* per-field strings rather than per-attempt arrays" — that was true when written and stopped
|
|
149
|
+
* being true when the host measured them at 17% of a real 1.4 MB tree and moved them onto the
|
|
150
|
+
* same on-demand fetch `sources`/`history` already used. Neither key is retired: the host
|
|
151
|
+
* serves both from `data-point-sources` for the single field whose detail is open. Both are
|
|
152
|
+
* declared optional below, so a consumer that reads them off a base-render candidate gets
|
|
153
|
+
* `undefined` rather than a type error — this library reads NEITHER, and any consumer that
|
|
154
|
+
* wants them must fetch that field's detail, exactly as it already must for its citations.
|
|
155
|
+
*
|
|
156
|
+
* NOTHING IN THIS LIBRARY FILLS `sources`/`history` ANY MORE. They used to be lazy-fetched by the in-letter Inspector dialog, which is
|
|
148
157
|
* deleted; the embedding app reads a data point's full detail against its own
|
|
149
158
|
* session instead. A real production render was shipping every field's
|
|
150
159
|
* full retry history — each carrying its own `sources[]`, each source carrying two
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@thehammer/template-verification",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.21",
|
|
4
4
|
"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.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|