@thehammer/template-verification 0.2.11 → 0.2.13

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

@@ -24,16 +24,46 @@ import type { MetaCarrier } from "../types";
  * 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.
  *
- * ==== THE MARK IS OUT OF FLOW, AND THAT IS A HARD REQUIREMENT ====
- *
- * It is absolutely positioned against the wrapper (see the `<style>` block at
- * the foot of this file), overlaying the right-hand end of the value it belongs
- * to. It therefore occupies ZERO inline space: turning the overlay on or off,
- * or toggling a field from "unverified" to "verified", must not move a single
- * character of the letter. The previous layout was an `inline-flex` row with a
- * gap, so every mark pushed the rest of its line along — which reflowed the
- * document the moment the overlay was switched on, in a product whose entire
- * point is that the document is the deliverable.
+ * ==== NOTHING MOVES, AND NOTHING IS COVERED ====
+ *
+ * Two requirements, and the shape below is the one that satisfies BOTH.
+ *
+ * 1. NO REFLOW. Turning the overlay on or off, or a field going from
+ *    "unverified" to "verified", must not move a single character of the
+ *    letter. The document is the deliverable, and a reviewer toggling the
+ *    overlay must be looking at the same pagination they will print.
+ * 2. NO OCCLUSION. The value must stay fully readable. A mark that hides the
+ *    claimant's surname or the year of the accident makes the letter unusable,
+ *    which is worse than any layout wobble.
+ *
+ * The mark therefore lives in a PERMANENTLY RESERVED SLOT: `.tv-mark-slot` is
+ * an empty fixed-width inline-block rendered beside every value ALWAYS —
+ * overlay on, overlay off, tracked or untracked, on screen and on paper. It is
+ * the slot, not the mark, that occupies the inline space, so the space never
+ * appears or disappears and nothing ever reflows. The mark is absolutely
+ * positioned INSIDE that slot, so its own width — a bare confidence dot, a
+ * verified chip, either of them wearing a discrepancy flag — can never push a
+ * character either.
+ *
+ * Two earlier shapes, and why each one loses:
+ *
+ * - `inline-flex` row with a gap (the original): every mark pushed the rest of
+ *   its line along, so the whole letter reflowed the moment the overlay was
+ *   switched on. Fails (1).
+ * - Absolute at `right: 0` against the wrapper, occupying zero inline space
+ *   (the shape this replaces): it bought (1) by overlaying the last characters
+ *   of the value — `Abdinasir Abdi` rendered as `Abdinasir ✔`, `October 23,
+ *   2024` as `October 23, 2 ✔`. Fails (2), and fails it on exactly the two
+ *   fields a reader most needs. `left: 100%` is the same trade with the damage
+ *   moved onto whatever the template wrote next, which is no better.
+ *
+ * What the reserved slot costs, stated plainly: about one-and-a-bit character
+ * widths of permanent space after every data point, present even in print. That
+ * is the price of never covering a value, and it is deliberately paid in the
+ * one place a document can absorb it — inter-word space — rather than on top of
+ * the words themselves. It is NOT hidden by the `@media print` chrome rule: the
+ * slot is not chrome, so the printed page is laid out identically to the screen
+ * and only the glyph goes away.
  */
 type __VLS_Props = {
     source?: MetaCarrier;

package/dist/lib/discrepancy.d.ts

@@ -1,4 +1,4 @@
-import type { CandidateSet, DataPointMeta } from "../types";
+import type { CandidateSet, Correction, DataPointMeta } from "../types";
 /**
  * A data point is in discrepancy when two or more PRESENT candidates hold
  * differing values. A single candidate (or none) can never disagree with itself.
@@ -20,3 +20,12 @@ export declare function candidatesDisagree(candidates?: CandidateSet | null): bo
  * which wording the mark's accessible name carries.
  */
 export declare function isSourceDiscrepancy(meta?: DataPointMeta | null): boolean;
+/**
+ * True when a data point carries a `correction` (SG-406) — "we normalised/typo-fixed this
+ * value" provenance the block dedupe recorded, DISTINCT from a source-document conflict.
+ * Never implies `isSourceDiscrepancy`/`hasDiscrepancy`, and the reverse: a genuine conflict
+ * carries no `correction` unless the same value was also corrected.
+ */
+export declare function hasCorrection(meta?: DataPointMeta | null): boolean;
+/** The correction record, or null/undefined when this data point carries none. */
+export declare function correctionOf(meta?: DataPointMeta | null): Correction | null | undefined;