# User Review Required - m-openai-compatible-output-validation-filters/03_repeat_guard_s07_remote_evidence

## Requested At

2026-07-30

## Status

RESOLVED_REPLAN

## Reason

- Type: external-execution
- Target: non-interactive dev runner `ssh toki@toki-labs.com`, the authenticated `ornith:35b` S07 live smoke, and the selected OneXPlayer/RTX5090 provider capacity
- Current review number: 2
- Final verdict: FAIL
- Summary: The single authorized live invocation was consumed without completing the first five-request batch. No S07 summary was produced, and the selected provider had not returned to idle after the harness exited. Automatic execution cannot safely start another live invocation without explicit new authorization.

## Loop History

| Plan | Review | Verdict | Note |
|------|--------|---------|------|
| `plan_cloud_G08_0.log` | `code_review_cloud_G08_0.log` | FAIL | Authentication was unavailable, so the live invocation count remained 0. |
| `plan_cloud_G08_1.log` | `code_review_cloud_G08_1.log` | FAIL | One authorized live invocation exited after about 20 minutes with four SSE artifacts, no summary, and incomplete provider cleanup. |

## Blocking Evidence

- Problem: SDD S07 requires 15 provider responses, 15 Edge correlations, three capacity rows, and a sanitized repeat fingerprint/offset or `not_reproduced` result. The consumed invocation produced none of those completion artifacts.
- Current archived plan: `plan_cloud_G08_1.log`
- Current archived review: `code_review_cloud_G08_1.log`
- Verification command: read-only artifact, process, authentication, source-identity, runtime-config, and provider-status probes against the declared runner; no new provider invocation was started during this review-resolution pass.
- Actual output:
  - `artifact_probe=PASS files=4 names=run-01-attempt-01.sse,run-01-attempt-03.sse,run-01-attempt-04.sse,run-01-attempt-05.sse summary=absent harness=running`
  - `remote_harness=EXITED artifact_files=4 summary=absent invocation_count=1`
  - `remote_post_failure=BLOCKED stage=provider-idle invocation_count=1`
  - `provider_cleanup=onex_in_flight=1:onex_queued=0:rtx_in_flight=0:rtx_queued=0`
- A later caller-owned replacement attempt was explicitly cancelled at the user's request. Its exact remote harness processes were terminated, it left four SSE artifacts and no summary, and it is not accepted as S07 evidence.
- Blocking rationale: The declared runner, protected SOPS credential source, Edge listeners, and all four node connections are now available. The remaining preflight gap is narrower: the Control Plane status response currently reports zero `provider_snapshots`, so it cannot prove the selected providers' configured capacity or idle counters even though the loaded Edge config contains four providers.

## Required User Action

- [x] Confirm that the related external-environment issues have been resolved and request a fresh readiness test, review update, and replan. Preserve every failed artifact and require a fresh isolated path for any future live invocation.

## Resolution Evidence

- User decision recorded: on 2026-07-30 the user stated that the related problems were resolved and explicitly requested readiness testing, completion of this review, and a new plan.
- Authentication: `dev_openai_auth_preflight=PASS token_ref=toki-dev-pi status=200`; no raw token or token hash was printed or written to a tracked file.
- Deterministic verification:
  - remote source tests: `ok iop/apps/edge/internal/service`, `ok iop/apps/edge/internal/controlplane`, and `ok iop/apps/control-plane/cmd/control-plane`;
  - dispatcher regression: `227 passed, 109 subtests passed`;
  - Edge config: `edge_config_check=PASS` and `edge_refresh_dry_run=PASS status=applied changes=0 error=none`.
- Runtime identity: the remote checkout is clean at `750cb1d1cb88066a10d3c703c99f1326306d8e15`; the deployed Edge process uses the matching `build/dev-runtime/bin/edge`; all four nodes are connected; no repeat-guard harness remains.
- Remaining status-contract evidence: `status_error=none node_count=4 provider_snapshot_nodes=0 provider_snapshot_count=0 all_connected=true`. The config contains four enabled providers, including OneXPlayer capacity 3 and RTX5090 capacity 1, but live provider counters are not currently observable.
- Cancellation cleanup: the user-cancelled direct attempt was stopped at both the caller SSH session and the exact remote harness processes. Its artifact path `/tmp/iop-repeat-guard-live/repeat-guard-task-03-direct-2` remains preserved with four SSE files and no summary.

## Resume Condition

- The plan workflow archives this resolved stop as `user_review_1.log` and creates a new routed pair against the current clean remote baseline.
- The new plan must first restore or re-seed the live provider snapshot contract using the least invasive documented runtime-refresh path, then prove all four nodes connected and the selected providers healthy/idle at capacities `3+1`.
- A future live invocation must use a new artifact path, run in a caller-owned foreground session through terminal exit, start at most once, and stop without retry after process start. Starting the implementation loop is the execution boundary; this review-resolution pass itself does not start a model invocation.

## Next Execution Hint

- Resume through the plan workflow for `m-openai-compatible-output-validation-filters/03_repeat_guard_s07_remote_evidence`; make provider-snapshot restoration and a sanitized `3+1` idle proof the first implementation gate.

## Closure Rules

- If the recorded user action and supplied evidence directly satisfy every archived acceptance criterion, update this stop to resolved, write `complete.log` from `agent-ops/skills/common/code-review/templates/complete-log-template.md`, and archive the task directory.
- If new execution is required, the plan skill archives `USER_REVIEW.md` to `user_review_N.log` before writing a new `PLAN-*-G??.md` / `CODE_REVIEW-*-G??.md` pair.
