-
Notifications
You must be signed in to change notification settings - Fork 0
Review provenance drawer never receives metadata — provider/model/confidence not surfaced to users #1284
Copy link
Copy link
Open
Labels
Priority IIThe active direction's next tranche: wedge capabilities, significant defects, near-term hardening.The active direction's next tranche: wedge capabilities, significant defects, near-term hardening.bugSomething isn't workingSomething isn't workingfrontendPrimary implementation impact in Vue/TypeScript UI and client runtime.Primary implementation impact in Vue/TypeScript UI and client runtime.product-truthProduct or docs claim something unsupported, misleading, or silently untrue; truth-repair work.Product or docs claim something unsupported, misleading, or silently untrue; truth-repair work.
Description
Activity
Metadata
Metadata
Assignees
Labels
Priority IIThe active direction's next tranche: wedge capabilities, significant defects, near-term hardening.The active direction's next tranche: wedge capabilities, significant defects, near-term hardening.bugSomething isn't workingSomething isn't workingfrontendPrimary implementation impact in Vue/TypeScript UI and client runtime.Primary implementation impact in Vue/TypeScript UI and client runtime.product-truthProduct or docs claim something unsupported, misleading, or silently untrue; truth-repair work.Product or docs claim something unsupported, misleading, or silently untrue; truth-repair work.
Projects
- StatusShow more project fieldsPending
Context
Surfaced by the #1273 (PR #1283) adversarial review (Lens B, LOW).
ReviewMain.vue:123renders<ReviewProvenance :rows="provenance" :proposal-id="proposalId" ...>with no:metadataprop.ReviewProvenancetherefore passesmetadata ?? null = nulltoProvenanceDrawer, whose meta section isv-if="metadata"— so the provider / model / confidence / latency / promptVersion block never renders in the review flow. The card modal (CardModalMetadata.vue) and inbox detail also omit provider/model.Net: the (now-truthful, post-#1273) capture-triage provenance value
deterministic-extractor/capture-triage-v1is persisted on the capture payload and returned by the capture API, but is not displayed to users anywhere in the review UI.ProvenanceDrawer.spec.tscovers the rendering as an isolated-component guarantee only.Acceptance criteria
ProvenanceMetadatafrom the reviewed proposal's capture provenance (provider, model, promptVersion, and confidence/latency if available) in the review selectors.:metadatathroughReviewMain.vue→ReviewProvenance→ProvenanceDrawerso the meta section renders.deterministic-extractor/capture-triage-v1to a user (not just the isolated component spec).Notes
Pre-existing gap (not introduced by #1273). Archive-closeout scope — nice-to-have for provenance-visible automation, low urgency for single-user personal use.