@thehammer/template-verification 0.2.15 → 0.2.16

package/README.md

@@ -30,10 +30,17 @@ itself is two products fighting over one viewport — in a frame that cannot rea
 any of the viewers the embedding app already has. Reviewing a value now happens
 in that app, which opens the citation and the record beside the letter.
 
-`initVerification` still **accepts** `saveOverride` and `detailUrl` and ignores
-both. That is compile-time compatibility for already-built templates, whose
-`App.vue` is generated from a snippet that still passes them; it is not a
-feature. See `src/context.ts`.
+`initVerification` still **accepts** `saveOverride` and ignores it. That is
+compile-time compatibility for already-built templates, whose `App.vue` is
+generated from a snippet that still passes it; it is not a feature. See
+`src/context.ts`.
+
+`detailUrl` was the same story until SG-689, when gpt-manager's wiring snippet
+and its server-side sidecar both stopped emitting it — it is no longer part of
+`InitVerificationConfig` at all. An already-built template's source that still
+names it keeps building (the template build does not type-check) and keeps
+harmlessly passing an unread property, same as before it had a name in this
+interface.
 
 ## Install
 

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

@@ -84,6 +84,26 @@ import type { MetaCarrier } from "../types";
  * back to full opacity with higher selector specificity than either hover
  * rule, so a keyboard user tabbing to the mark while the pointer happens to
  * be resting on the value still sees it clearly.
+ *
+ * ==== SG-693: THE DEFAULT SLOT RENDERS MARKDOWN, WHICH IS BLOCK-LEVEL ====
+ *
+ * The inline-anchoring contract above ("ANCHORING TO THE TRAILING EDGE OF
+ * WRAPPED TEXT") assumes `.tv-field-value`'s content is plain inline text
+ * flowing across possibly-several lines. The markdown fallback (see the
+ * template below) renders through danx-ui's `CodeViewer`, which is a `<div>`
+ * — block-level, not inline — wrapping a `<p>` (or `<ul>`/`<table>`/etc. for
+ * richer markdown). A `<span>` containing an in-flow block box gets split
+ * into anonymous block boxes around it per CSS2.1 §9.2.1.1, so the mark
+ * anchor no longer lands on "the end of the last wrapped line" the way it
+ * does for plain text — it lands after the whole rendered block instead.
+ * This is a real, deliberate trade-off, not an oversight: every real
+ * self-closing `<VerifiedField>` usage in the two in-scope templates
+ * (TPL-1/TPL-2 — see SG-693's investigation) is already the SOLE content of
+ * its own `<p class="dl-prose">` wrapper, never inline mid-sentence, so the
+ * mark simply sits at the end of that paragraph either way. A future caller
+ * that binds `<VerifiedField>` truly inline within running prose (not as a
+ * paragraph's only child) would see the mark detach from the trailing text
+ * for exactly this reason — worth revisiting if that usage shape appears.
  */
 type __VLS_Props = {
     source?: MetaCarrier;

package/dist/context.d.ts

@@ -42,15 +42,6 @@ export interface InitVerificationConfig {
      * {@link ../lib/hostBridge.DataPointActivatedMessage}.
      */
     workflowInputId?: number | string | null;
-    /**
-     * ACCEPTED AND IGNORED, for the same reason as `saveOverride` above.
-     *
-     * This was the Inspector dialog's lazy per-field detail endpoint. The
-     * Inspector is gone, and the embedder fetches a data point's citations and
-     * history against its own authenticated session rather than against a
-     * token-sealed url handed into an iframe.
-     */
-    detailUrl?: string | null;
     /** Seeds the overlay toggle ONLY when localStorage holds no prior value. */
     defaultEnabled?: boolean;
     /**