mostlyright-data 0.29.6__tar.gz → 0.29.8__tar.gz

{mostlyright_data-0.29.6 → mostlyright_data-0.29.8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mostlyright-data
-Version: 0.29.6
+Version: 0.29.8
 Summary: Mostly Right hosted CLI for reviewed datasets
 Project-URL: Homepage, https://mostlyright.md/
 Project-URL: Documentation, https://mostlyright.md/docs/guides/cli/

{mostlyright_data-0.29.6 → mostlyright_data-0.29.8}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mostlyright-data"
-version = "0.29.6"
+version = "0.29.8"
 description = "Mostly Right hosted CLI for reviewed datasets"
 readme = "README.md"
 requires-python = ">=3.11"

{mostlyright_data-0.29.6 → mostlyright_data-0.29.8}/skills/mr-data-build/references/commands.md

@@ -18,7 +18,7 @@ gap rather than doing anything, and `export-hosted-candidate`, which is a backen
 | `mr-data dataset` | Bring the dataset page into existence before there is anything on it, then fill it in while somebody watches. `dataset create --name TEXT` mints it and prints the `dataset_id`, unless the user's own request already has an empty dataset open, in which case it answers `open_request_reused` with that `dataset_id` and mints nothing (`--separate` mints a new one for a different dataset); `dataset show ID` reads it back; `dataset set ID --name TEXT --topics "a,b,c" --license ID --description-file F` writes the title, the descriptive tags, the SPDX licence and the description under the version it was read at, retrying once if somebody else wrote first, and an empty `--topics` or `--license` takes that value off the page; send `--name` and `--topics` whenever you send `--description-file`, because a description sent on its own can make Studio write a new title and new tags, and read `changed` and `written_by_studio` on the receipt for every field the write moved; a saved write whose public sync fails exits 2 and reports `public_projection_synced: false` — use `dataset sync ID` to retry that sync without rewriting Studio; `dataset note ID --heading H --blocks-file B` writes one cell of the decision record that OUTLIVES every run, and `--list` reads it back; `dataset watch ID` follows the page's own event stream; `dataset activity ID --phase P --message TEXT` says what is happening right now, silently, and is never a chat message and never a cell; `dataset publish ID [--mode public|link|private]` says who can read the dataset — `public` lists it in the public directory and serves it at an address anybody can read, `link` serves it at an unlisted address, `private` takes it back to the workspace — and `dataset publish ID --show` reads that back without changing it; `dataset archive ID --confirm-name TITLE` retires the page and frees its title, deleting nothing. |
 | `mr-data recipe` | Register one recipe document — dataset, question, table plan, sources, transform, checks and units — in one call, and print the identifiers the server derived. The document is read first and every fault comes back in one refusal, each with the JSON pointer that names it; `--no-lint` sends it as written instead. Registration refuses `THIN_BRIEF_MISSING` when the dataset's record carries no answered question and no delegation, and `THIN_RECIPE_DATASET_UNBOUND` when the document names no `dataset.id`; `--delegated "their words"` writes the delegation onto the dataset and registers in the same command, and clears the first of those two and never the second. `mr-data recipe show ID` reads one back. `mr-data recipe explain FILE` (or a recipe identifier) lists every reason its table can or cannot refresh, each with a rule code and Studio's suggested repair, and exits 2 when one blocks it. `mr-data recipe forecast RECIPE_ID --digest DIGEST` says what one run would ask of each source before it runs, and exits 3 when the run would overrun today's platform quota or one attempt. `mr-data recipe readiness --table TABLE_ID --current-only` reads the revision one table runs now. [Making a table incremental](making-a-table-incremental.md#the-loop-explain-forecast-run-diagnose) says when to use each. |
 | `mr-data cover` | Generate and attach one branded 1200×630 dataset cover. Give it the dataset ID and what the image should depict; Studio fixes the model, single-color style, curated random palette, dimensions and storage. |
-| `mr-data run` | Start one run against a registered recipe, named as `--recipe RECIPE_ID --digest RECIPE_DIGEST` — both required, neither positional, and the digest is the bare hex the registration receipt printed. The mode is one of six: `sample`, `full`, `refresh`, `backfill`, `compact` and `replay`. Four have a shorthand flag (`--sample`, `--full`, `--refresh`, `--backfill`) and two do not, so write `--mode MODE`, which is accepted for every one of them. A refresh executes only Studio's persisted source-action plan, and a plan shape it does not refresh returns `RESYNC_REQUIRED` before acquisition; [which plans refresh](making-a-table-incremental.md#which-plans-refresh) lists them, and `mr-data recipe explain` says which one a table is. Use `mr-data table resync TABLE_ID --request-id UUID` for an explicit full source reread, retaining that UUID if the response is uncertain. `--backfill` states the exact window with `--window START END`. `--mode replay --sources-from RUN_ID` asks Studio to run the registered revision against the RETAINED RAW INPUTS of one named successful run of the same table: nothing is fetched from this computer, nothing is acquired again, the result is compared against that run and never becomes the live version, and it neither asks for nor records an approval. Where Studio has replay switched off, or the named run is not successful, not the same table, or no longer retains its inputs, it answers a typed refusal — report the code rather than retrying in another mode. `--sources-from` on any other mode is refused `THIN_ARGUMENT_INVALID` before anything is sent. `--max-rows` and `--max-source-bytes` bound ONE SOURCE rather than the finished table. A large run is held for a size confirmation (not a charge), which `--confirm` settles and whose printed `confirm_command` re-states every argument the request carried. `--approve-full RUN_ID` releases the full an existing legacy sample-first pair is holding once its preview has succeeded, naming either half of the pair; where the deployment still wants a person at a browser it answers `THIN_INTERACTIVE_HUMAN_REQUIRED` and names the run page. `--retry RUN_ID` tries one failed run again when its triple carries `room_fault: true`, re-stating that run's own coordinate under a byte ceiling that cannot narrow it, and refuses with the triple when the recipe was at fault. `--cancel RUN` stops one. |
+| `mr-data run` | Start one run against a registered recipe, named as `--recipe RECIPE_ID --digest RECIPE_DIGEST` — both required, neither positional, and the digest is the bare hex the registration receipt printed. The mode is one of six: `sample`, `full`, `refresh`, `backfill`, `compact` and `replay`. Four have a shorthand flag (`--sample`, `--full`, `--refresh`, `--backfill`) and two do not, so write `--mode MODE`, which is accepted for every one of them. A refresh executes only Studio's persisted source-action plan, and a plan shape it does not refresh returns `RESYNC_REQUIRED` before acquisition; [which plans refresh](making-a-table-incremental.md#which-plans-refresh) lists them, and `mr-data recipe explain` says which one a table is. Use `mr-data table resync TABLE_ID --request-id UUID` for an explicit full source reread, retaining that UUID if the response is uncertain. `--backfill` states the exact window with `--window START END`. `--mode replay --sources-from RUN_ID` asks Studio to run the registered revision against the RETAINED RAW INPUTS of one named successful run of the same table: nothing is fetched from this computer, nothing is acquired again, the result is compared against that run and never becomes the live version, and it neither asks for nor records an approval. Where Studio has replay switched off, or the named run is not successful, not the same table, or no longer retains its inputs, it answers a typed refusal — report the code rather than retrying in another mode. `--sources-from` on any other mode is refused `THIN_ARGUMENT_INVALID` before anything is sent. `--max-rows` and `--max-source-bytes` bound ONE SOURCE rather than the finished table. A large run is held for a size confirmation (not a charge), which `--confirm` settles and whose printed `confirm_command` re-states every argument the request carried. `--approve-full RUN_ID` releases the full an existing legacy sample-first pair is holding once its preview has succeeded, naming either half of the pair; where the deployment still wants a person at a browser it answers `THIN_INTERACTIVE_HUMAN_REQUIRED` and names the run page. `--retry RUN_ID` tries one failed run again when its triple carries `room_fault: true`, re-stating that run's own coordinate and ceilings and naming the failed run so Studio starts a new attempt, and refuses with the triple when the recipe was at fault. `--cancel RUN` stops one. |
 | `mr-data status` | Report which of the seven states one run is in, what it delivered and whether a ceiling cut it short, and — on a failure — what failed, where, and whether the fault was the execution room's rather than the recipe's. Exits non-zero on a failed run. `--diagnose` adds everything else Studio can say about the run: its progress, a per-row source's plan counts, its checkpoints, and how each attempt ended, with a lost attempt's cause marked as an inference. |
 | `mr-data runs` | Report this workspace's own runs: identifier, mode, state and creation time, plus the failure triple of any that failed and whether that failure was the execution room's. `--dataset DATASET_ID` narrows it to one dataset's runs, so "what have I run for this dataset?" is one scoped read, and a value that is not an identifier is refused `THIN_ARGUMENT_INVALID`. `--status` and `--mode` narrow it too and are refused `THIN_ARGUMENT_INVALID` for a word outside the seven states or the six modes; the three combine. Studio narrows before it cuts a page, so a filtered page holds the newest runs that match however many runs the workspace has. `--limit` says how many, and pages are followed to reach it; a listing that does not end says how many were read and suggests a smaller `--limit` or a narrower filter. The answer prints `next_cursor`, and `--cursor` continues from it. |
 | `mr-data watch` | Stream one run's live progress under the durable event type of each stage, resuming across stream cuts. Exits non-zero when the run failed. |

{mostlyright_data-0.29.6 → mostlyright_data-0.29.8}/skills/mr-data-build/references/live-run.md

@@ -28,8 +28,9 @@ appends again, and `watch` stops rather than reconnecting.
 
 **A terminal run is cached against `(recipe, digest, mode, clamps)`.** Re-running that exact
 coordinate replays the stored result rather than making a new attempt — a stored failure included —
-which is why `mr-data run --retry RUN_ID` moves a ceiling rather than re-sending the request as it
-was. It is also why `SANDBOX_MEMORY_BOUNDARY` reads as a source problem and is not one: it names
+which is why `mr-data run --retry RUN_ID` names the failed run to Studio rather than re-sending the
+request as it was; the ceilings stay the same unless Studio does not admit the named retry, and
+then the byte ceiling is raised as it was before. It is also why `SANDBOX_MEMORY_BOUNDARY` reads as a source problem and is not one: it names
 the source being fetched, the cause is a clean room with no delegated memory cgroup, it is
 intermittent and per-instance, and `room_fault` is true on that run so nothing has to be inferred
 from the wording. Report the failure once, retry it when supported, then report the replacement

{mostlyright_data-0.29.6 → mostlyright_data-0.29.8}/skills/mr-data-build/references/making-a-table-incremental.md

@@ -319,10 +319,12 @@ call:
 
 - `parameter` is declared with `required: true`. `{id}` is the whole of one `static_query` value
   and appears nowhere else.
-- `key_column` is a column the pinned Reader declares. The worker splits the answer back to
-  members by that column.
-- `batch` refuses a POST, a `body_template`, a `platform` credential and
-  `pages.max_unavailable_members` above 0. The preflight names each before anything is sent.
+- `key_column` is a column the pinned Reader decodes to: one of its `columns[]`, or the
+  `record_key_column` of a `json.tabular` 1.3.0 pin reading `records_from: object_values`. The
+  worker splits the answer back to members by that column.
+- `batch` refuses a POST, a `body_template` and a `platform` credential. The preflight names
+  each before anything is sent. `pages.max_unavailable_members` above 0 is for Studio to answer
+  at registration, which admits it when its engine counts a batch's unavailable members.
 - Member ids and saved answers do not change, so turning `batch` on keeps every paid answer.
 - `absent: "failed"` fails a member the answer does not name, so the next run asks again. The
   default, `empty`, records it with no rows.

{mostlyright_data-0.29.6 → mostlyright_data-0.29.8}/skills/mr-data-build/references/sources.md

@@ -239,7 +239,7 @@ at 0 there is no second attempt, so the first answer too large fails the run. Ra
 
 If the API takes a list of ids in one query parameter, add `request.batch` and send up to 100
 members in one call. It keeps every member id and saved answer. It refuses a POST, a
-`body_template`, a `platform` credential and a failure budget above 0.
+`body_template` and a `platform` credential.
 [`batch`](making-a-table-incremental.md#batch-many-rows-in-one-request) has the grammar.
 
 A collection whose calls are paid for is sized from evidence, not from its ceiling. Run

{mostlyright_data-0.29.6 → mostlyright_data-0.29.8}/src/mostlyright/data_harness/thin/fast_features.py

@@ -178,15 +178,8 @@ def _batch(sources: list[Mapping[str, Any]]) -> dict[str, Any]:
         if isinstance(request.get("batch"), Mapping):
             used.append(name)
             continue
-        pages = _mapping(collection.get("pages"))
-        tolerated = pages.get("max_unavailable_members")
         platform = _mapping(source.get("connector")).get("credential_mode") == "platform"
-        if (
-            request.get("method") == "POST"
-            or "body_template" in request
-            or platform
-            or (type(tolerated) is int and tolerated > 0)
-        ):
+        if request.get("method") == "POST" or "body_template" in request or platform:
             refused.append(name)
         else:
             open_to.append(name)
@@ -205,8 +198,8 @@ def _batch(sources: list[Mapping[str, Any]]) -> dict[str, Any]:
         return _entry(
             BATCH,
             NOT_APPLICABLE,
-            f"{', '.join(refused)} is a POST, a body_template, a platform credential or a "
-            "failure budget above 0, and batch refuses each",
+            f"{', '.join(refused)} is a POST, a body_template or a platform credential, and "
+            "batch refuses each",
             sources=refused,
         )
     return _entry(BATCH, NOT_APPLICABLE, "no source sends one request per upstream row")

{mostlyright_data-0.29.6 → mostlyright_data-0.29.8}/src/mostlyright/data_harness/thin/recipe_lint.py

@@ -944,7 +944,12 @@ def _request_placeholder_sites(request: Mapping[str, Any], at: str) -> list[tupl
 
 
 def _reader_columns(connector: Any) -> set[str] | None:
-    """The column names the connector's pinned Reader declares, or ``None`` when unreadable."""
+    """The column names the connector's pinned Reader decodes to, or ``None`` when unreadable.
+
+    Options that state ``records_from: object_values`` with a ``record_key_column`` decode that
+    key column too (``json.tabular`` 1.3.0), as Studio's ``reader_pin_columns`` reads them. Which
+    Reader versions may state those options is left to Studio.
+    """
 
     parameters = connector.get("parameters") if isinstance(connector, Mapping) else None
     for parameter in parameters if isinstance(parameters, list) else ():
@@ -956,11 +961,15 @@ def _reader_columns(connector: Any) -> set[str] | None:
             columns = options.get("columns") if isinstance(options, Mapping) else None
             if not isinstance(columns, list):
                 return None
-            return {
+            names = {
                 entry["name"]
                 for entry in columns
                 if isinstance(entry, Mapping) and isinstance(entry.get("name"), str)
             }
+            key = options.get("record_key_column")
+            if options.get("records_from") == "object_values" and isinstance(key, str):
+                names.add(key)
+            return names
     return None
 
 
@@ -970,8 +979,11 @@ def _row_request_batch_coherence(sources: Any) -> list[Finding]:
     Studio's ``_row_request_batch_details``, restated. The batched parameter is declared with
     ``required: true``, and ``{parameter}`` is the whole of one ``static_query`` value and appears
     nowhere else. The request is a GET with no ``body_template``. The source uses no ``platform``
-    credential, and ``pages.max_unavailable_members`` is 0 or absent. ``key_column`` is a column
-    the pinned Reader declares.
+    credential. ``key_column`` is a column the pinned Reader decodes to.
+
+    ``pages.max_unavailable_members`` above 0 is NOT judged here. Studio admits it beside
+    ``batch`` when its pinned engine counts a batch's unavailable members, and this client cannot
+    see which engine is pinned, so registration answers that one.
     """
 
     if not isinstance(sources, list):
@@ -1005,17 +1017,6 @@ def _row_request_batch_coherence(sources: Any) -> list[Finding]:
                     "request cannot use",
                 )
             )
-        pages = source["collection"].get("pages")
-        tolerated = pages.get("max_unavailable_members") if isinstance(pages, Mapping) else None
-        if type(tolerated) is int and tolerated > 0:
-            findings.append(
-                Finding(
-                    DOCUMENT_INCOHERENT,
-                    f"{base}/pages/max_unavailable_members",
-                    f"is {tolerated}, and a batched request records no unavailable members, so "
-                    "this must be 0",
-                )
-            )
         name = batch.get("parameter")
         if isinstance(name, str):
             parameters = request.get("parameters")

{mostlyright_data-0.29.6 → mostlyright_data-0.29.8}/src/mostlyright/data_harness/thin/v4_runs.py

@@ -129,8 +129,10 @@ DISCARD_HISTORY_FLAG = "--discard-snapshot-history"
 #: ⚠ AND ANOTHER ATTEMPT NEEDS A DIFFERENT COORDINATE. Studio derives a run's identity from
 #: ``(recipe_id, recipe_digest, mode, clamps, resource_class)`` and replays a terminal result for
 #: an identical command, so re-issuing the same request returns the same failure without waking a
-#: worker. ``mr-data run --retry RUN_ID`` is what turns that into one command; see
-#: :func:`retry_clamps` for the one coordinate it moves and why moving it changes nothing else.
+#: worker. ``mr-data run --retry RUN_ID`` is what turns that into one command: it names the failed
+#: run as ``retry_of_run_id``, which Studio folds into the identity, and the ceilings go out as
+#: they were. See :func:`retry_clamps` for the coordinate it moves instead when Studio answers
+#: ``RUN_NOT_RETRYABLE`` or a stored run that is already over.
 ROOM_FAULT_CODES: frozenset[str] = frozenset(
     {
         "EXECUTION_LEASE_EXPIRED",
@@ -591,9 +593,12 @@ def declare_run_arguments(parser: argparse.ArgumentParser) -> None:
         "--retry",
         metavar="RUN_ID",
         help="try this failed run again, when what failed was the room rather than the recipe; "
-        "the same recipe, digest, mode and ceilings go out under one byte clamp raised above what "
-        "the document declares, because an identical command replays the stored failure. A run "
-        "that states a byte ceiling of its own has no such coordinate to move and is refused",
+        "the same recipe, digest, mode and ceilings go out naming the failed run, so Studio "
+        "starts a new attempt rather than replaying the stored failure. When Studio does not "
+        "admit that for the run, or answers with a stored run that is already over, the "
+        "command goes out once more under a byte clamp raised above what the document "
+        "declares. A stored run that is queued or running is printed as it is and no second "
+        "run is started",
     )
     parser.add_argument(
         "--approve-full",
@@ -1289,12 +1294,45 @@ def fresh_full_record(run: Mapping[str, Any]) -> bool:
     )
 
 
+#: The refusals of a retry that named the failed run after which the same retry goes out once
+#: more under a moved byte clamp, which is what this command sent before it named the run.
+#: ``RUN_NOT_RETRYABLE`` is Studio declining ``retry_of_run_id`` for this run: its list of
+#: platform failures is its own, and a Studio that has not yet deployed a code this client reads
+#: as a room fault answers with it. The snapshot-history refusal is here because the command it
+#: prints is re-typed without ``retry_of_run_id`` (there is no flag for it), so that command has
+#: to carry a coordinate of its own.
+#:
+#: ``KEEL_ENGINE_REQUIRED`` is here because naming the run can cause it. Studio never hands a
+#: retry of a Python run to Keel (``v4/runs.py``, ``retry_of_python_run``), and then refuses a
+#: recipe the Python engine does not build. The body this command sent before it named the run
+#: carries no ``retry_of_run_id``, so admission chooses the engine again and the run can start.
+#: When the second answer is the same refusal, it is raised as it is.
+_CLAMP_RETRY_CODES: frozenset[str] = frozenset(
+    {"RUN_NOT_RETRYABLE", SNAPSHOT_HISTORY_CODE, "KEEL_ENGINE_REQUIRED"}
+)
+
+#: The states of a run answered to the named retry that mean no new attempt started. Studio's own
+#: automatic resume of a lost progressive full starts its successor with the body the named retry
+#: sends (``apps/api/.../v4/auto_resume.py``: the lost run's clamps and resource class, with
+#: ``resume_capture_run_id`` and ``retry_of_run_id`` both naming it), so once that successor
+#: exists the named retry derives its run id and Studio answers ``201`` with the successor's
+#: stored record. When that record is already over, the retry goes out under the moved byte
+#: clamp, which is a coordinate the successor does not hold.
+#:
+#: ``succeeded`` is a member for the same reason as the other two: a run that is over is not the
+#: attempt this command was asked for. A plain start of the same command is answered with the
+#: failed run's stored record, so without this the table could not be built again from this
+#: command once a successor had succeeded, and 0.29.7 started a run here.
+_STORED_END_STATUSES: frozenset[str] = TERMINAL_RUN_STATUSES
+
+
 def retry_body(
     run: Mapping[str, Any],
     run_id: str,
     *,
     declared_bytes: int = 0,
     fresh_read_control: bool = False,
+    clamp_moved: bool = False,
 ) -> dict[str, Any]:
     """The ``create_run_command`` that is this failed run again, rebuilt off its own record.
 
@@ -1302,6 +1340,12 @@ def retry_body(
     nothing else: the whole point of ``--retry RUN_ID`` is that it does not require somebody to
     have kept the recipe, the digest, the mode and the ceilings the first attempt went out with.
 
+    THE FAILED RUN IS NAMED, AND THE CEILINGS ARE THE ONES IT CARRIED. ``retry_of_run_id`` enters
+    the identity Studio derives, so the command is a new attempt without any ceiling changing
+    (planning#234). ``clamp_moved`` builds the other body instead: no ``retry_of_run_id``, and
+    :func:`retry_clamps` in place of the stated ceilings, for a Studio that answered
+    ``RUN_NOT_RETRYABLE`` to the first.
+
     ⚠ A FRESH FULL IS RETRIED FRESH, AND THE BODY SAYS SO. Studio already keeps a resumed chain
     on the answer lineage its origin was admitted with, so a retry of a fresh full reads fresh
     whatever this body says; stating ``reuse_saved_answers: false`` makes the body, and the rerun
@@ -1319,7 +1363,16 @@ def retry_body(
                 "THIN_RESPONSE_INVALID", f"Studio reported run {run_id} without a {member}"
             )
         body[member] = stated
-    body["clamps"] = retry_clamps(run, declared_bytes=declared_bytes)
+    if clamp_moved:
+        body["clamps"] = retry_clamps(run, declared_bytes=declared_bytes)
+    else:
+        carried = run.get("clamps")
+        clamps = dict(carried) if isinstance(carried, Mapping) else {}
+        if "window" in clamps:
+            clamps["window"] = _command_window(clamps["window"])
+        if clamps:
+            body["clamps"] = clamps
+        body["retry_of_run_id"] = identifier(run_id, "run identifier")
     if body["mode"] == "full":
         body["progressive"] = True
         if run.get("progressive") is True:
@@ -1395,7 +1448,67 @@ def retry(run_id: str, *, client: StudioV4RunClient) -> dict[str, Any]:
             "--mode replay --sources-from RUN_ID once the room is well, or build the recipe "
             "rather than replaying it",
         )
-    # ⚠ THE RECIPE IS READ BEFORE THE RETRY IS BUILT, and that round trip is the price of the
+    # ⚠ THE CAPABILITY IS READ ONLY WHEN IT CAN CHANGE THE BODY. A retry of anything but a fresh
+    # full sends the same body whatever this Studio serves, so asking would be a round trip that
+    # decides nothing.
+    fresh_read_control = False
+    if fresh_full_record(run):
+        table_id = run.get("table_id")
+        if isinstance(table_id, str) and table_id:
+            fresh_read_control = (
+                table_capabilities(client, identifier(table_id, "table identifier")).get(
+                    FRESH_READ_CONTROL
+                )
+                is True
+            )
+    body = retry_body(run, run_id, fresh_read_control=fresh_read_control)
+    try:
+        started = client.create_run(body)
+    except ThinLaneError as refusal:
+        if getattr(refusal, "studio_code", None) in _CLAMP_RETRY_CODES:
+            return _retry_under_a_moved_clamp(
+                run, run_id, client=client, triple=triple, fresh_read_control=fresh_read_control
+            )
+        held = _held_for_confirmation(refusal, body)
+        if held is None:
+            raise
+        # ⚠ SETTLED BY THE HELD RUN'S OWN ID. A re-typed start has no flag for
+        # `retry_of_run_id`, so it would name the failed run's coordinate and Studio would answer
+        # with the stored failure. The refusal names the run Studio held, and `--confirm-held`
+        # confirms that exact record.
+        held["confirm_command"] = confirm_held_command(
+            identifier(str(held["run_id"]), "run identifier")
+        )
+        held["retry_of"] = run_id
+        held["retried_failure"] = triple
+        return held
+    if started.get("status") in _STORED_END_STATUSES:
+        # ⚠ A RUN THAT IS ALREADY OVER IS NOT ANOTHER ATTEMPT. Studio answered the named retry
+        # with a record it had stored under the same identity (see `_STORED_END_STATUSES`), so
+        # printing it as `run_retried` would hand back a stored failure as the retry
+        # (planning#234). The moved clamp is the coordinate 0.29.7 sent, and it starts a run.
+        return _retry_under_a_moved_clamp(
+            run, run_id, client=client, triple=triple, fresh_read_control=fresh_read_control
+        )
+    return _retried(client, started, run_id=run_id, triple=triple, clamp_moved=False)
+
+
+def _retry_under_a_moved_clamp(
+    run: Mapping[str, Any],
+    run_id: str,
+    *,
+    client: StudioV4RunClient,
+    triple: Mapping[str, Any],
+    fresh_read_control: bool,
+) -> dict[str, Any]:
+    """The same retry without ``retry_of_run_id``, under the one ceiling that can move.
+
+    What ``--retry`` sent before it named the failed run, kept for a Studio that answers
+    ``RUN_NOT_RETRYABLE`` or ``KEEL_ENGINE_REQUIRED`` to the named retry, or answers it with a
+    stored run that is already over.
+    """
+
+    # ⚠ THE RECIPE IS READ BEFORE THIS BODY IS BUILT, and that round trip is the price of the
     # clamp being inert. Studio projects from the document's own declared ceilings, so a clamp
     # chosen without reading them is a clamp that might lower what the run projects -- and
     # `projected_bytes` is what the spend and sample-first thresholds are read against.
@@ -1411,24 +1524,12 @@ def retry(run_id: str, *, client: StudioV4RunClient) -> dict[str, Any]:
             "Studio answered without the recipe document this run was started against, so the "
             "bytes it is projected against could not be read and a retry cannot be sized",
         )
-    # ⚠ THE CAPABILITY IS READ ONLY WHEN IT CAN CHANGE THE BODY. A retry of anything but a fresh
-    # full sends the same body whatever this Studio serves, so asking would be a round trip that
-    # decides nothing.
-    fresh_read_control = False
-    if fresh_full_record(run):
-        table_id = run.get("table_id")
-        if isinstance(table_id, str) and table_id:
-            fresh_read_control = (
-                table_capabilities(client, identifier(table_id, "table identifier")).get(
-                    FRESH_READ_CONTROL
-                )
-                is True
-            )
     body = retry_body(
         run,
         run_id,
         declared_bytes=declared_source_bytes(document),
         fresh_read_control=fresh_read_control,
+        clamp_moved=True,
     )
     try:
         started = client.create_run(body)
@@ -1450,10 +1551,25 @@ def retry(run_id: str, *, client: StudioV4RunClient) -> dict[str, Any]:
         held["retry_of"] = run_id
         held["retried_failure"] = triple
         return held
+    return _retried(client, started, run_id=run_id, triple=triple, clamp_moved=True)
+
+
+def _retried(
+    client: StudioV4RunClient,
+    started: Mapping[str, Any],
+    *,
+    run_id: str,
+    triple: Mapping[str, Any],
+    clamp_moved: bool,
+) -> dict[str, Any]:
+    """The receipt of a retry Studio started, with the cell that says why the run exists."""
+
     payload = _started(started, client.session, status="run_retried")
     payload["retry_of"] = run_id
     payload["retried_failure"] = triple
-    payload["note"] = _retry_note(client, started, run_id=run_id, triple=triple)
+    payload["note"] = _retry_note(
+        client, started, run_id=run_id, triple=triple, clamp_moved=clamp_moved
+    )
     return payload
 
 
@@ -1497,6 +1613,7 @@ def _retry_note(
     *,
     run_id: str,
     triple: Mapping[str, Any],
+    clamp_moved: bool = False,
 ) -> dict[str, Any] | None:
     """One cell on the NEW run saying which fault it is another attempt at, or ``None``.
 
@@ -1524,17 +1641,31 @@ def _retry_note(
     except ThinLaneError:
         return None
     try:
-        cell = client.append_cell(fresh, body=_retry_cell(client, fresh, run_id, triple))
+        cell = client.append_cell(
+            fresh, body=_retry_cell(client, fresh, run_id, triple, clamp_moved=clamp_moved)
+        )
     except ThinLaneError as refusal:
         return {"written": False, "refusal": {"code": refusal.code, "detail": refusal.detail}}
     return {"written": True, "cell_id": cell.get("cell_id")}
 
 
 def _retry_cell(
-    client: StudioV4RunClient, fresh: str, run_id: str, triple: Mapping[str, Any]
+    client: StudioV4RunClient,
+    fresh: str,
+    run_id: str,
+    triple: Mapping[str, Any],
+    *,
+    clamp_moved: bool = False,
 ) -> dict[str, Any]:
     """The append command that cell is, composed where its refusals are already being caught."""
 
+    coordinate = (
+        "A byte ceiling above anything the sources can deliver gives the attempt a coordinate "
+        "of its own; an identical command would have replayed the stored failure."
+        if clamp_moved
+        else "The attempt names the failed run and carries the same ceilings; an identical "
+        "command that did not name it would have replayed the stored failure."
+    )
     return run_cell_body(
         workspace_id=client.session.workspace_id,
         run_id=fresh,
@@ -1544,9 +1675,8 @@ def _retry_cell(
             f"Run {run_id} failed at the {triple['failed_stage']} stage with "
             f"{triple['failure_code']}: {triple['failure_detail']}\n\n"
             "That code is about the room the run landed in rather than about this recipe, so the "
-            "document is unchanged. A byte ceiling above anything the sources can deliver gives "
-            "the attempt a coordinate of its own; an identical command would have replayed the "
-            "stored failure. Full retries use progressive acquisition. When the failed full was "
+            f"document is unchanged. {coordinate} "
+            "Full retries use progressive acquisition. When the failed full was "
             "already progressive, the retry also names it as the capture ancestor so Studio can "
             "reuse compatible sealed pages."
         ),