# Pending feedback → mgf-test-web

Drafts awaiting relay to `mgf-test-web/FEEDBACK.md` (FB-05 outbox).

### PAPER — mgf-fedres widened `test_status_value`: the warden outcome projection can be dropped

- **Severity:** 🟢 Nice-to-have (unblocks planned cleanup)
- **Filed by:** mgf-fedres queue sweep (Court-delegated) on 2026-07-10
- **What hurts:** `src/mgf/test_web/warden/outcomes.py` still projects
  `crashed/hung→error` and `quarantined→skipped` when writing durable
  run-records, preserving the verbatim outcome only in an
  `{"event":"outcome"}` audit row — a fidelity workaround for the old
  narrow `test_status_value` enum (mgf-fedres PAPER-04).
- **Why it matters:** the schema now carries the supervisor vocabulary
  natively; keeping the projection means `result` keeps lying to any reader
  who doesn't also parse the audit trail, for no remaining reason.
- **Evidence:** mgf-fedres branch `feedback/queue-sweep-2026-07-10` —
  `src/mgf/fedres/schemas/_common.schema.json` `test_status_value` enum now
  `["pass","fail","error","skipped","crashed","hung","quarantined","unknown"]`;
  `tests/test_schemas.py::test_supervisor_outcomes_validate_natively` proves
  crashed/hung/quarantined validate as `test_run_record.result`. mgf-fedres
  FEEDBACK PAPER-04 is SHIPPED.
- **Suggested shape:** once the widened mgf-fedres release is pinned, delete
  the projection rows from `warden/outcomes.py` (the paper said the table "is
  structured to drop its projection the moment the schema widens") and write
  the supervisor outcome verbatim into `result`; keep the audit row if wanted
  for history, but it is no longer load-bearing.
- **Status:** OPEN
