Files
learnharness/components/artifacts/probe-done-card.tsx
T
amosblomqvist 1f41fb05a5 question tools: phase-visible names, hardened teach schemas, context-slim seams
The tools_fails_2 diagnosis (glm-5.3 dropping trailing required fields):
- probe-phase quiz/explain renamed to probe/recall — a shared name carried
  the probe call shape into teaching (the first teach quiz dropped nodeId);
  display seams accept the old names forever
- teach quiz+explain schemas lead with the required pair (type, nodeId);
  explain gains the predict/check type and joins the reveal law (checks
  collapse, predictions arrive open; no-type records render check-style)
- plan_init/probe_done results go context-slim (owner, context diet):
  content = validated nodeIds + binding-id reminder / fixed ack; details
  keeps the tree for the popup and {ok:true} — serializer-verified that
  details never reaches the model; failure echoes dropped
- the cards carry the tool's own name (Probe/Recall) and the quiz type
  reads on the label (Prediction/Check) in composer and transcript
2026-10-09 07:59:23 +03:00

71 lines
3.3 KiB
TypeScript

"use client";
import { ClipboardCheckIcon } from "lucide-react";
import { parseProbeDoneInput, type ProbeDoneResult } from "@/src/core";
/**
* The probe conclusion card (docs/probe-teach-split.md §2): renders the
* prober's probe_done call. The INPUT is the learner assessment — strand by
* strand, where his edge sits — and it belongs to the learner as much as to
* the transcript: it streams live while the prober writes it and stays as
* the handoff artifact. The OUTPUT is the seam's ack (ok) or the refusal
* the prober retried on (rendered quiet and small — it is model-facing
* bookkeeping, kept only for transcript honesty).
*
* The input preview is only trustworthy while the call is pending — an
* input-available input cleared schema validation at the boundary, and a
* mid-stream partial is guarded below. An output-error part's input was
* REJECTED by validation and can be any shape (live crash: the model
* stringified `assessment`); never render it.
*
* Deliberately plain v1: the proper assessment viewer design is deferred to
* the UI wave; this card just guarantees the data is never invisible.
*/
export function ProbeDoneCard({ part }: { part: { input?: unknown; output?: unknown; state?: unknown } }) {
const output = part.output as ProbeDoneResult | undefined;
const state = typeof part.state === "string" ? part.state : "";
// Parse, don't cast (the seam rule, src/core/tool-parts.ts): the model
// authored this input — it is consumer-trustworthy only if the SAME
// schema the tool declared says so. The parse subsumes the old state
// reasoning and shape guards: an errored call's stringified assessment,
// a mid-stream partial — anything that doesn't parse falls to the
// fallback branch. Output stays a cast: OUR execute authored it.
const input = parseProbeDoneInput(part.input);
// The assessment is the CALL's input (owner, context diet 2026-10-09):
// the result's echo is gone — details is {ok:true} only, and the refusal
// branch below still reads output.error.
const assessment = input?.assessment;
const strands = assessment && Array.isArray(assessment.strands) ? assessment.strands : null;
return (
<div data-testid="probe-done-card" className="my-3 rounded-xl border bg-card/60 p-3">
<div className="mb-2 flex items-center gap-2 text-xs font-medium uppercase tracking-wide text-muted-foreground">
<ClipboardCheckIcon className="size-3.5 text-primary" />
Probe concluded — your assessment
</div>
{output && !output.ok ? (
<p className="text-sm text-muted-foreground">The prober retried: {output.error}</p>
) : state === "output-error" ? (
<p className="text-sm text-muted-foreground">
The assessment was malformed — the prober retried with a corrected one.
</p>
) : strands ? (
<div className="space-y-2">
{strands.map((s, i) => (
<div key={i} className="rounded-lg bg-background/60 px-3 py-2">
<div className="text-sm font-medium">{s.strand}</div>
<div className="mt-0.5 text-sm text-muted-foreground">{s.assessment}</div>
</div>
))}
{assessment?.summary && (
<p className="px-1 text-sm text-muted-foreground">{assessment.summary}</p>
)}
</div>
) : (
<p className="text-sm text-muted-foreground">Writing the assessment…</p>
)}
</div>
);
}