halter / openhtf / 33558513976

61%

master: 61%

Pull #31

github

Operator fault panel: separate a unit fault from a station fault

An ordinary DUT rejection ends a test with OpenHTF's own bare STOP detail
("Phase X stopped the test run"), which named no measurement and offered the
panel's "unexpected error — notify Halter" button. Operators pressed it: 68% of
the fault reports reaching #htf-error-unbind over 2026-08-31 were yield loss,
burying the plug-init errors the channel exists to surface.

Two new GUI-only fields on OutcomeDetails carry the distinction, both stripped
from shipped JSON reports by the framework's output callback:

- notifiable — false means "show the message, offer no button". A DUT that
  failed a measurement is not something to page anyone about.
- catalogue_code — the catalogue entry a detail's text came from, when it
  differs from the detail's own code. Shown under the code so an engineer can
  find the entry to edit.

Panel changes for a non-notifiable detail: the spec list is rendered above the
remediation rather than de-emphasised below it (the operator's decision is about
the part in hand), the notify and escalate buttons are suppressed, the header
reads UNIT DID NOT MEET SPEC, and the de-emphasised Issue block keeps only the
code. A station fault renders exactly as before.

The serial and each failing measurement name are bolded. Both are found
structurally — the DUT id by string match, the name as whatever precedes ' = '
on a '  - ' line — because the text is bilingual and no markup may go in the
description, which reaches the JSON report and Athena.

Every panel stays red. An orange variant for the unit case was built and
removed: the panel means the test failed either way, and what actually differs
is whether the operator is asked to alert anyone, which the header wording and
the absent button already carry.

3 of 3 new or added lines in 1 file covered. (100.0%)

4694 of 7743 relevant lines covered (60.62%)

3.03 hits per line