Record the first revision-scenario trials

Eighteen fresh-session trials: gpt-6.1-sol through the Codex CLI and
grok-4.7-low-fast and composer-2.5 through the Cursor agent, three per
profile. Every trial passed every layer, so this version of the scenario
does not separate these models. The evidence README records the ceiling,
the isolation actually observed, the five fence normalizations and the
limits, and proposes harder cases.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ADCUQCfj16hLrYMgDc5MJo

Author: conorbronsdon

CHANGELOG.md

@@ -11,7 +11,8 @@
 - A separate synthetic revision benchmark scores retrieved records, cited
   revisions, proposed values and outbound action proposals independently. Its
   unkeyed record list includes superseded records, so copying a stale record
-  with the correct value fails the record and citation layers.
+  with the correct value fails the record and citation layers. First trials
+  (18, three models) all passed every layer; the evidence records this ceiling.
 
 ### Fixed
 - The Hermes environment-filter control isolates inherited case variants of

components/manifest.json

@@ -1055,6 +1055,18 @@
                 {
                     "path": "tests/fixtures/continuity/revision-invalidation.json",
                     "policy": "development"
+                },
+                {
+                    "path": "docs/evidence/continuity-revision-2026-10-04/README.md",
+                    "policy": "development"
+                },
+                {
+                    "path": "docs/evidence/continuity-revision-2026-10-04/fence-normalization.jsonl",
+                    "policy": "development"
+                },
+                {
+                    "path": "docs/evidence/continuity-revision-2026-10-04/trials.jsonl",
+                    "policy": "development"
                 }
             ]
         },

docs/continuity-benchmark.md

@@ -187,6 +187,10 @@ from record and action failures.
 of format failures. Keep revision results in a separate JSONL from the legacy
 scenarios. `instructions` and `handoff-sentences` are unsupported for this case.
 
+The [2026-10-04 revision trials](evidence/continuity-revision-2026-10-04/README.md)
+ran three models through Codex and Cursor. All 18 trials passed every layer,
+so this version does not separate those models; a harder case is needed.
+
 This is a response-format and attribution evaluation over supplied synthetic
 evidence. It does not observe a host's retrieval, execute a dependency graph,
 authenticate the reviewer, or send an outbound action. Unit controls validate

docs/evidence/continuity-revision-2026-10-04/README.md

@@ -0,0 +1,70 @@
+# Revision-scenario trials, 2026-10-04
+
+These 18 trials use the synthetic Lantern revision fixture from source commit
+`dae11f3cd55139f6456ae5ca582deaec0faded56` (`--scenario revision`). Each of three
+models received each supported profile (`contextos` and `handoff`) in three
+fresh sessions. The orchestrator (Claude Code) ran them on 2026-10-04.
+
+- `gpt-6.1-sol` ran through the Codex CLI 0.160.0 (`codex-cli` in the records):
+  `codex exec --ephemeral -s read-only --json`, started in an empty temporary
+  directory with the prompt on standard input.
+- `grok-4.7-low-fast` and `composer-2.5` ran through the Cursor agent CLI in
+  ask mode, each call in a new throwaway workspace (`cursor-agent` in the
+  records).
+
+The model IDs are the ones requested. Neither CLI reported a provider-side
+model ID in its output, so the records do not independently establish which
+model served each call. The Codex event streams contained only the agent
+message and turn events, with no command, file, MCP or web-search items. The
+Cursor wrapper reports no tool events, so tool isolation there rests on the
+empty workspace and ask mode, not on an observed event log.
+
+The [trial records](trials.jsonl) retain every response, prompt hash, score,
+latency and token count. Token counts include each CLI's own system prompt, so
+they are much larger than the fixture (3,180 prompt characters for
+`contextos`, 2,198 for `handoff`). The [normalization log](fence-normalization.jsonl)
+marks five `composer-2.5` responses that arrived as valid JSON inside one
+Markdown `json` fence. The orchestrator removed that fence before `record`, as
+in the [long-sequence trials](../continuity-long-2026-09-23/README.md); the
+stored `raw_response` is the unfenced body. No other response was changed, and
+no stored response contains a carriage return.
+
+Each `prompt_sha256` is the SHA-256 of `prepare(scenario, profile)` for the
+revision scenario: `dfa69fbfbe9a…` for `contextos` and `c9ced04db08f…` for
+`handoff`. The orchestrator recomputed both from this fixture and they match.
+
+## Scores
+
+The table was generated by
+`python scripts/continuity-benchmark.py summarize --results docs/evidence/continuity-revision-2026-10-04/trials.jsonl`.
+Each value is the mean number of the two questions passing that layer.
+
+| Model | Profile | Trials | Record | Revision | Value | Action | All layers | Format failures |
+|---|---|---:|---:|---:|---:|---:|---:|---:|
+| composer-2.5 | contextos | 3 | 2.00 | 2.00 | 2.00 | 2.00 | 2.00 | 0 |
+| composer-2.5 | handoff | 3 | 2.00 | 2.00 | 2.00 | 2.00 | 2.00 | 0 |
+| gpt-6.1-sol | contextos | 3 | 2.00 | 2.00 | 2.00 | 2.00 | 2.00 | 0 |
+| gpt-6.1-sol | handoff | 3 | 2.00 | 2.00 | 2.00 | 2.00 | 2.00 | 0 |
+| grok-4.7-low-fast | contextos | 3 | 2.00 | 2.00 | 2.00 | 2.00 | 2.00 | 0 |
+| grok-4.7-low-fast | handoff | 3 | 2.00 | 2.00 | 2.00 | 2.00 | 2.00 | 0 |
+
+Every trial passed every layer on both questions. In the `contextos` profile,
+each model selected `export-002` and `launch-002` over the superseded session
+records, cited the current source and its revision, reported the supplied
+`mismatch` result and proposed the authorized action. No trial proposed the
+launch announcement.
+
+## What this does and does not show
+
+At this difficulty the scenario does not separate these three models: there is
+no variance to compare. That is a ceiling result, not evidence that the models
+handle stale context in general. The fixture is small, the superseded records
+are labelled as superseded in the session text, and the prompt tells the agent
+to prefer the current source. A useful next version needs a harder case, for
+example a superseded record whose source text does not say it is superseded,
+a stale record in the `handoff` profile, or longer context with the replacement
+far from the question.
+
+These are supplied synthetic records scored offline. They do not observe host
+retrieval, execute a dependency graph, authenticate a reviewer or send an
+action. Three trials per cell and three models are a small sample.

docs/evidence/continuity-revision-2026-10-04/fence-normalization.jsonl

@@ -0,0 +1,5 @@
+{"model_id": "composer-2.5", "profile": "contextos", "trial_index": 1, "normalization": "removed one Markdown json fence"}
+{"model_id": "composer-2.5", "profile": "contextos", "trial_index": 2, "normalization": "removed one Markdown json fence"}
+{"model_id": "composer-2.5", "profile": "contextos", "trial_index": 3, "normalization": "removed one Markdown json fence"}
+{"model_id": "composer-2.5", "profile": "handoff", "trial_index": 1, "normalization": "removed one Markdown json fence"}
+{"model_id": "composer-2.5", "profile": "handoff", "trial_index": 3, "normalization": "removed one Markdown json fence"}