# FEEDBACK — mgf-test-web (ProofWarden)

> Paper-tracking file for issues, friction, and requests against this sibling.
>
> **Where to file what:**
> - **Authority-specific** (the warden broker / lease registry / single-flight
>   decision, `testctl`, a runner adapter, the `[web]` console) → file HERE.
> - **The spine** (a schema, the sync engine, a sync state, the live/run-record
>   wire formats, the `SourceProvider` seam) → that is the spine:
>   [mgf-fedres/FEEDBACK.md](https://codeberg.org/magogi-admin/mgf-fedres/src/branch/main/FEEDBACK.md).
> - **The runner itself** (tiering, `.gates`, quarantine) →
>   [mgf-test-supervisor](https://codeberg.org/magogi-admin/mgf-test-supervisor).
> - **Federation-wide** → [mgf-common/FEEDBACK.md](https://codeberg.org/magogi-admin/mgf-common/src/branch/main/FEEDBACK.md).
>
> **Discipline:** see DOCUMENTATION.md §FEEDBACK (FB-01..FB-05, DOC-13).

## §1 Process

1. **File freely.** Anyone hitting friction files a PAPER-NN under §2.
2. **Status flips** `OPEN` → `SHIPPED` / `DEFERRED` / `WONTFIX` / `MOVED`.
3. **Renumbering** never happens (FB-01).

## §2 Open feedback (active)

_No papers yet._ `mgf-test-web` is new at **0.1.0** (the **A4** warden spike — the
single-flight core — is in; the catalog + console + live logs + history + CI are
the next milestones). File the first PAPER-NN here.

## §3 Reviewer's meta-feedback

_None yet._

## §4 How to submit feedback

1. **Open a Codeberg issue** at <https://codeberg.org/magogi-admin/mgf-test-web/issues>.
2. **For a structured pain point**: file a PAPER-NN here as a PR that adds the entry to §2.

## §5 Cross-references

- [mgf-fedres](https://codeberg.org/magogi-admin/mgf-fedres) — the federation-resources spine (the shared core this builds on).
- [mgf-test-supervisor](https://codeberg.org/magogi-admin/mgf-test-supervisor) — the tier runner (`mtest`), driven as a library.
- [mgf-fed-web](https://codeberg.org/magogi-admin/mgf-fed-web) — the sibling federation dashboard (same spine).
- [mgf-common/FEEDBACK.md](https://codeberg.org/magogi-admin/mgf-common/src/branch/main/FEEDBACK.md) — federation-wide PAPERs.

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

| Field | Value |
|---|---|
| Status | OPEN |
| Submitter | mgf-fedres queue sweep (Court-delegated) on 2026-07-10 |
| Submitted | 2026-07-10 |
| Severity | 🟢 Nice-to-have (unblocks planned cleanup) |
| Federation paper | relayed by the supervisor from `mgf-fedres/pending-feedback/mgf-test-web.md` (FB-05) |

- **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
