# v-harness Frontend Study

- Date: 2026-07-14
- Status: complete evidence capture · selected mechanisms validated in Viewer V0.4
- Source: `image2code-glm-v1@249c2bceedaf3c04f76ae3a899d91acbf8dc2641`
- Release: `v2.3.2`

This internal study records the v-harness frontend as it actually appears and
behaves. It is deliberately separate from the upstream manager (source lineage
and deployment) and from future internal trajectory-viewer implementation.

The original study remains the observation record. The separate Viewer V0.4
implementation has now validated selected mechanisms as `adopted`, `modified`
or `rejected`; `FUTURE_CONSIDERATION_LEDGER.md` links each status change to
implementation and browser/data evidence. Unimplemented candidates remain
`observed`.

## Research Package

- `GOAL_SPEC.md` — source-of-truth scope and acceptance criteria.
- `SCREEN_INVENTORY.md` — visible regions, hierarchy, responsive behavior and
  state-dependent presentation.
- `INTERACTION_MATRIX.md` — control-by-control behavior, API dependency, risk
  and evidence coverage.
- `STATE_MODEL.md` — frontend, job, batch, overlay and artifact state model.
- `SOURCE_UI_MAP.md` — pinned source routes/files mapped to visible behavior.
- `FIVE_DIMENSION_SYNTHESIS.md` — overall data management, single-case detail,
  case comparison, per-epoch inspection and HTML animated process replay,
  analyzed as five separate future-integration dimensions.
- `UX_ACCESSIBILITY_AUDIT.md` — screenshot-backed combined audit.
- `EVIDENCE_LOG.md` — timestamped captures, HTTP/DOM checks and limitations.
- `FUTURE_CONSIDERATION_LEDGER.md` — observed candidates and questions for a
  later trajectory-management integration project.
- `DELIVERY_MANIFEST.md` — task-scoped authored/generated files, runtime
  exclusions and dirty-worktree boundary.
- `evidence/screenshots/` — fresh, ordered screenshots from this audit run.

## Five organizing dimensions

1. Overall data management across gallery, runs, archives and batch state.
2. A single-case dossier spanning target, output, debug evidence and timeline.
3. Case comparison at target/reproduction, run/run and summary levels.
4. Per-epoch inspection with evidence, actions, gate outcome and provenance.
5. HTML process replay that can animate each meaningful step without treating
   a static screenshot sequence as the source of truth.

## Boundary

This project does not edit upstream frontend code, delete run history, run the
45-case suite, or merge a frontend mechanism into VeriHarness. Operationally
sensitive controls are inspected from source/DOM or exercised only in the
already approved isolated canary scope.