@thehammer/template-verification 0.2.17 → 0.2.19

package/dist/components/VerifiedField.vue.d.ts

@@ -10,7 +10,7 @@ import type { MetaCarrier } from "../types";
  * value — and with no `initVerification` call at all it still renders and never
  * throws.
  *
- * ==== THE MARK IS THE WHOLE SURFACE. THERE IS NOTHING ELSE ====
+ * ==== HANDING OFF IS THE WHOLE SURFACE. NOTHING OPENS IN HERE ====
  *
  * What used to be here as well: a 90vw x 90vh tabbed Inspector dialog, a hover
  * panel summarising confidence and citation counts, and `contenteditable` on
@@ -18,11 +18,20 @@ import type { MetaCarrier } from "../types";
  * disabled. A letter is a document. Reviewing a value — reading its citations,
  * seeing the record it belongs to, correcting it — is the embedding app's job,
  * and that app already does all three better than a dialog squeezed into an
- * iframe ever could. Everything a reader can do from here is: click the mark.
+ * iframe ever could. Everything a reader can do from here is name a data point
+ * to the embedder; this component still opens, toggles and fetches nothing.
  *
- * The mark's own summary now lives in its ACCESSIBLE NAME rather than in a
- * hover panel, so the same sentence reaches a screen reader and a mouse
- * hovering the glyph, and neither costs a second piece of chrome in the page.
+ * SG-764 widened HOW that naming is triggered, not what it does. There are two
+ * ways to say "this one", and they post the identical message: the mark, and
+ * the VALUE itself, which carries the dotted underline saying it can be
+ * corrected. The mark was the only one for a while, and a 0.85em glyph is not
+ * what a reviewer reading a letter points at — see the value span in the
+ * template below for the full reasoning, including why the value is not also a
+ * tab stop.
+ *
+ * The mark's own summary lives in its ACCESSIBLE NAME rather than in a hover
+ * panel, so the same sentence reaches a screen reader and a mouse hovering the
+ * glyph, and neither costs a second piece of chrome in the page.
  *
  * ==== PLACEMENT: MOSTLY OUTSIDE THE VALUE, NEVER IN ITS OWN RESERVED SPACE ====
  *

package/dist/constants.d.ts

@@ -6,5 +6,30 @@
  * components and the print-chrome regression test agree on one source of truth.
  */
 export declare const CHROME_CLASS = "tv-chrome";
+/**
+ * Class applied to a rendered VALUE the reader can correct — the dotted
+ * underline plus the pointer cursor that say "this is a data point, click it"
+ * (SG-764). Its condition is the same one that decides whether the value is a
+ * click target at all: a real `anchor` on the point's `__meta`, which is the
+ * only thing that gives the save endpoint somewhere to write. An unanchored
+ * point never wears it, so the mark can never promise an edit that cannot be
+ * saved.
+ *
+ * ==== WHY THIS IS NOT `CHROME_CLASS`, AND WHY IT IS NOT A SECOND PRINT RULE ====
+ *
+ * `CHROME_CLASS` marks an ELEMENT as the library's own — a settings button, an
+ * overlay mark — and print deletes it whole. That is deliberately kept OFF the
+ * field's value, which is the host's content and must print (a regression test
+ * asserts exactly that separation). This class is the other kind of thing: the
+ * library painting a screen-only decoration ONTO host content. The element
+ * stays; only the paint goes.
+ *
+ * The two are therefore removed DIFFERENTLY — `display: none` versus
+ * `border-bottom: none` — but by the SAME `@media print` block, in
+ * `VerificationChrome.vue`, which is the only file in this package that carries
+ * one. A second print rule beside the first is how the on-paper answer ends up
+ * being decided in two places; `printChrome.test.ts` fails if one appears.
+ */
+export declare const EDITABLE_CLASS = "tv-editable";
 /** localStorage key holding the persisted overlay enabled/disabled state. */
 export declare const ENABLED_STORAGE_KEY = "template-verification:enabled";

package/dist/index.d.ts

@@ -40,5 +40,5 @@ export { walkDataPoints } from "./lib/walk";
 export type { WalkedDataPoint } from "./lib/walk";
 export { computeProgress } from "./lib/progress";
 export type { VerificationProgress } from "./lib/progress";
-export { CHROME_CLASS, ENABLED_STORAGE_KEY } from "./constants";
+export { CHROME_CLASS, EDITABLE_CLASS, ENABLED_STORAGE_KEY } from "./constants";
 export type { VerificationStatus, ResolvedSource, SourceChoice, VerificationSource, ExtractedCandidate, HumanCitation, OverrideCandidate, ClaimCandidate, CandidateSet, DataPointAnchor, ResolvedValue, DataPointMeta, MetaCarrier, SaveOverrideArgs, SaveOverrideFn, } from "./types";