First R3 (Theater) piece. Reworks the stale artifact-keyed ReplayRoute into the turn-keyed hero over the #716 sealed-replay backend, and fully retires the dead W-026 artifact-keyed machinery on both sides (the NOT_YET_MIRRORED comment anticipated this). The hero makes determinism *felt*: pick a journaled turn, CORE re-executes its prompt in a sealed fresh runtime, and the result renders as a hash verdict (≡ equivalent / ≠ diverged) + the original/replay DigestBadges + a leaf diff (critical weighted above informational, each with a ≠ glyph). The 'What this proves' card surfaces comparison_basis + origin_state and states the honest limit: a divergence means nondeterminism OR origin-state influence, never rendered on its own as a determinism failure. Retirement (verified zero serving uses): - Python schemas.py: removed ReplayComparison/ReplayDivergence/ReplayStatus/ ReplayDivergenceSeverity; scripts/dump-enums.py drops the two replay enums; both snapshots regenerated (deterministic: dump == committed) - TS: removed ReplayComparison/ReplayDivergence/ReplayDivergenceSeverity; added TurnReplayComparison/TurnReplayDivergence (+ basis/origin/severity unions); NOT_YET_MIRRORED now empty (every engine schema mirrored) - badges: removed ReplayStatusBadge + ReplayDivergenceSeverityBadge + meta/enums + their enumCoverage cases (hero renders severity inline) - api: fetchReplayComparison/useReplayComparison -> fetchTurnReplay/ useTurnReplay (/replay/<turnId>) - deleted ArtifactList, ReplayComparisonPanel, ReplayDiffViewer, ReplayMetadataTable, old replay.test.tsx - App route /replay/:artifactId? -> /replay/:turnId?; conformance row turn-keyed (loading 'Loading turns...', empty 'No turns recorded yet.') Tests: ReplayRoute.test.tsx (equivalence hero + honesty card, diverged critical leaf, informational-only label, replace-mode select, j/k spine). Full vitest 358 green; workbench Python 34 green; both snapshots deterministic. Follow-up flagged (not in this PR to keep it focused): the artifact query hooks (useArtifacts/useArtifactDetail/fetchArtifacts*) are now orphaned but entangled with the still-live artifact EvidenceSubject kind — a separate cleanup once an Artifacts route or that subject's fate is decided. Brief: docs/handoff/wave-R3-briefs-2026-06-13.md (all four R3 pieces).
39 lines
650 B
JSON
39 lines
650 B
JSON
{
|
|
"EpistemicState": [
|
|
"perceived",
|
|
"evidenced",
|
|
"evidenced_incomplete",
|
|
"verified",
|
|
"decoded",
|
|
"decoded_unarticulated",
|
|
"inferred",
|
|
"unverified_possible",
|
|
"unverified_novel",
|
|
"contradicted",
|
|
"ambiguous",
|
|
"undetermined",
|
|
"scope_boundary",
|
|
"computationally_bounded",
|
|
"epistemic_state_needed"
|
|
],
|
|
"GroundingSource": [
|
|
"pack",
|
|
"teaching",
|
|
"vault",
|
|
"partial",
|
|
"oov",
|
|
"none"
|
|
],
|
|
"NormativeClearance": [
|
|
"cleared",
|
|
"violated",
|
|
"unassessable",
|
|
"suppressed"
|
|
],
|
|
"ReviewState": [
|
|
"pending",
|
|
"accepted",
|
|
"rejected",
|
|
"withdrawn"
|
|
]
|
|
}
|