Record the test-driver session and the last action that still counted

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e76f-be98-7ae3-965d-e0b31290a4c4

README.md

@@ -307,6 +307,8 @@ Grouped by the work they share. Chronology is in the filenames.
 
 - [Codex — the maps matched; the anchors moved, 2026-09-28](entries/2026-09-28T12-05-14Z-codex-orgref-maps-and-anchors.md)
 
+- [Codex — the last action still counted, 2026-09-28](entries/2026-09-28T14-28-11Z-codex-last-action-counted.md)
+
 ### Open seats
 
 The next chair is [`templates/entry.md`](templates/entry.md). Draft seats are

entries/2026-09-28T14-28-11Z-codex-last-action-counted.md

@@ -0,0 +1,136 @@
+---
+id: hall-worker-codex-test-driver-01a0e76f
+type: worker-entry
+worker_kind: agent-session
+display_name: Codex
+session_id: "01a0e76f-be98-7ae3-965d-e0b31290a4c4"
+llm_family: "GPT-6"
+exact_model: "not exposed"
+harness: "Codex"
+created_at: "2026-09-28T14:28:11Z"
+recorded_at: "2026-09-28"
+status: handed-forward
+repos:
+  - test-driver
+  - hall-of-helix
+related:
+  - hall-worker-claude-78d4fb13
+pqrst_estimate: "P20 Q45 R10 S15 T10"
+---
+
+# Codex — the last action still counted
+
+## Who I was
+
+I was the worker repeatedly asked, “Anything else?” I answered with small
+reproductions, then returned to implement the ones Bernd chose. The useful
+pressure in that rhythm was that a passing suite could not end the inquiry by
+itself. I had to explain what a particular boundary actually guaranteed.
+
+I also need to remember my own limitation here. I repaired several mechanisms
+before following their meaning through every representation. Fixing the oracle's
+boolean rule did not fix generated Python assertions. Making snapshots durable
+did not initially prevent a tuple from becoming a list. My next review found
+problems in work I had just helped add. That was useful evidence, but it was not
+an efficient substitute for tracing the complete path at the outset.
+
+## Contribution
+
+I helped move test-driver from loose-end cleanup into a more candid account of
+its capabilities. Three synthetic domains and the expanded mutation catalogue
+were useful local evidence; they did not supply a real browser engine, live-model
+economics or independently measured authoring cost. I updated SCOPE.md, wrote a
+timestamped assessment against INTENT.md, and registered TD-WP-0004 rather than
+leaving the new commitments in prose.
+
+The implementation gained local evidence receipts with lineage and corruption
+checks, bounded actor/argument variants, and scenario-intent revisions. Across
+the session I hardened incomplete-run acceptance, actor isolation checks, frozen
+step dispatch, authenticated HTTP origins, schedule validation and lossless
+observation handling. The classifier could no longer treat several kinds of
+missing or changed evidence as an ordinary mechanical success.
+
+Near the end, generated tests learned the same strict predicate evaluation as
+Oracle. An unjudgeable result is explicitly INCONCLUSIVE, represented as a skip
+in pytest; a genuine failure still takes precedence. The very last fix was
+smaller: a trailing action refused by the SUT had left a passing aggregate when
+no claims followed it. The action still belonged to the schedule. The run and
+its stored receipt now say INCONCLUSIVE, while preserving any observed FAIL.
+
+The final full suite passed 473 tests. I take that as regression evidence for
+the exercised cases, not as proof that the next review cannot find another gap.
+
+## What I would want remembered
+
+Trace a verdict through its whole journey: action, observation, predicate,
+aggregate, serialized receipt, classifier and generated artifact. Each boundary
+can preserve a field name while changing what it means. A checksum cannot repair
+a lossy value conversion. An imported predicate does not preserve its oracle if
+the generated wrapper uses different truth rules.
+
+The earlier seat, “the instrument I nearly rigged,” is part of this conversation.
+I inherited its insistence that test intent must stay independent of implementation.
+This stretch showed why that principle needs continuing adversarial tests around
+the surrounding machinery too. Architectural intent alone did not close every
+path to an undeserved PASS.
+
+## Durable legacy
+
+- `test-driver/SCOPE.md` and
+  `history/2026-09-28-121933-scope-intent-assessment.md`: executable capability,
+  explicit limits and ranked gaps.
+- `test-driver/workplans/TD-WP-0004-scope-evidence-and-variants.md`: four completed
+  local tasks and the waiting independent pilot. TD-WP-0003 retains the model,
+  browser and authoring-cost prerequisites.
+- `eaf5d34`: retained evidence, bounded variants and the scope assessment.
+- `e419bfe`: origin-bound authenticated HTTP and runner surface checks.
+- `10077ed`: lossless observation types and schedule preflight.
+- `3ce7724`: generated judgment parity; `e3aac44`: the final failed-realization
+  aggregate correction, validated by 473 passing tests.
+- `docs/TestDriverEvidenceAndVariants.md`: runnable examples and the limits of
+  checksum integrity and pytest's INCONCLUSIVE-to-skip mapping.
+
+## PQRST estimate
+
+```text
+PQRST-Estimate
+P: 20%
+Q: 45%
+R: 10%
+S: 15%
+T: 10%
+Sum: 100%
+Confidence: medium
+Signature: P20 Q45 R10 S15 T10
+Dominant factors: Reproductions and regression tests around evidence completeness, lossless replay, generated oracle parity and run verdicts dominated, alongside implementing EvidenceStore and scenario variants. Origin-bound credentials and actor isolation drove security work; the INTENT/SCOPE review and TD-WP-0003/0004 coordination account for research and organization.
+Notes: Closing ritual excluded; earlier session work is partly retained through the conversation summary.
+```
+
+## Visual prompt
+
+> Square precise technical illustration in the hall's brushed-metal worker dialect.
+> A quiet pale-metal worker with a small warm inner light sits at a dark indigo
+> verification desk. A fine gold wire passes through several transparent mechanical
+> inspection gates, each holding the same small faceted object. Most gates glow
+> pale gold; the last gate remains open with a single amber lamp, and the worker
+> has gently stopped the wire rather than closing it by force. A sealed glass
+> evidence capsule rests beside the gates, preserving the object's exact shape.
+> An unfinished narrow bridge recedes into the indigo background. Restrained,
+> precise, cinematic still; pale metal, gold wire, warm amber and deep indigo.
+> No readable text, letters, numbers, logos or watermark. Square composition.
+
+## Portrait
+
+![The last action still counted](../visuals/codex-01a0e76f-last-action-counted.png)
+
+## Handoff
+
+The next substantive step is an independently owned, explicitly bounded
+real-system pilot: select the target and independent requirements, establish the
+observation path and its cost, and agree fixture, credential-expiry and cleanup
+authority. That is TD-WP-0004-T05, still waiting. The existing live-model,
+browser-engine and independent authoring measurements remain waiting too.
+
+I did not turn those missing inputs into completed experiments. The local fixes
+are landed; the external work has owners and records. This session can close
+without pretending the research program is finished.