REQUEST_TOKEN: sol-mini-trial-plan-r4-opencode-20261023
     EFFECTIVE_MODEL: requested opencode/deepseek-v4.1-flash-free#max
     / configured opencode/deepseek-v4.1-flash-free / Plan / read-
     only; max variant not independently read back; evidence: harness
     model/provider metadata and enforced native-read-only tools;
     upstream identity unverified.
     VERDICT: changes_required
     BLOCKERS: Step 4/8 (lines 50, 54): the margin is not a closed
     uncertainty budget as written. pass_margin = timing_band +
     bracket_half_width, but a coordinator UTC/monotonic difference up
     to step_threshold = max(250 ms, bracket_half_width) is tolerated.
     Line 54 says the margin covers "timestamp resolution and bracket
     uncertainty," yet a 200 ms forward step is not flagged when the
     threshold is 250 ms. With a 50 ms bracket and 50 ms band, the
     margin is 100 ms: a wait 200 ms before true completion plus a 200
     ms forward step records at true completion, so wait_return -
     completed_c is 100 ms and passes. That is a false pass. Either
     state that wait_return and completed_c are compared on the pre-
     step monotonic frame, add the tolerated step to pass_margin, or
     make the step gate strict.
     SUGGESTIONS: Line 71's "timing inside pass_margin" should read
     "later than completed_c but less than pass_margin" to match line
     54's early-wait failure; line 65's "timing difference" should
     name the subtraction order. Line 50 calls offset >2 s or bracket
     >250 ms a pre-prompt setup blocker, while line 71 lists them as
     inconclusive; state which report category applies.
     FILES_AT_RISK: docs/plans/2026-10-23-herdr-mini-isolated-trial.
     md, lines 50, 54, 65, 71 (edited margin/threshold sentences only)
     .
     CONCEDED: The 250 ms bracket half-width is now inside
     pass_margin, and the table consistently uses pass_margin for
     timing and step_threshold for drift; the round-3 label mismatch
     is gone. The remaining hole is the tolerated step, which the
     margin does not cover. I did not compute the plan SHA-256 with
     native read tools; the coordinator owns file verification.
     COMPLETION: complete / no delegates / no background work; narrow
     read of the four margin/threshold sentences only.
