<!-- task=m-iop-owned-single-request-agent-execution/25+23,24_claude_smoke_qualification plan=20 tag=REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_REVIEW_API milestone-task=workspace-binding,claude-smoke -->

# Execute the fifth authorized sole Claude-through-IOP S12 call

## For the Implementing Agent

The user's `승인할테니 시작해` instruction authorizes exactly one new Claude Code `--run` against the repaired disposable managed IOP runtime. Refresh the expired disposable managed certificates using the existing deterministic local credential-smoke path before guard creation, then run fresh local and remote provider-free gates. Only after every gate passes, create `sole-live-5.started`, invoke the harness once, finalize it as `sole-live-5.rc-N`, and never retry. Claude calls only IOP; Gemini plan/review and Ornith-fast work remain internal IOP routes. Publish S12 evidence only on complete PASS.

## Background

The fourth authorization was consumed as `sole-live-4.rc-69`, which failed HTTP 400 before ingress. The exact installed Claude 2.1.177 thinking-redaction beta/display boundary is now repaired and provider-free qualified. At this plan's first readiness check, the disposable CA and leaf certificates were found expired at `2026-08-08 06:46:03 UTC`; no fifth guard or Claude process had been created. Certificate renewal is setup only and must finish before consuming the one-call authorization.

## Archive Evidence Snapshot

- Prior pair: `plan_cloud_G10_19.log` / `code_review_cloud_G10_19.log`; verdict `FAIL`, Required R13, `review_rework_count=18`, `evidence_integrity_failure=false`.
- Resolved external stop: `user_review_7.log`; the user explicitly authorized one fifth guarded execution and no retry.
- Existing guards `sole-live.rc-69`, `sole-live-2.rc-69`, `sole-live-3.rc-69`, and `sole-live-4.rc-69` are immutable. No `sole-live-5*` guard exists at plan start.
- Disposable Edge PID 16840 contains the reviewed thinking-redaction repair. Control Plane 8782 and Node 8790 were alive at plan start; certificates were expired and must be deterministically refreshed before readiness can pass.

## Finding Resolution Map

| Finding | Mode | Exact evidence | Changed precondition |
|---|---|---|---|
| R13 | direct external execution | Resolved `user_review_7.log`, renewed disposable TLS, fresh tests/status matrix/fleet/preflight, `sole-live-5` guard, one harness `--run` | The user explicitly authorized exactly one new call after the installed-client compatibility boundary was repaired. |

## Analysis

### Files Read

- `apps/edge/internal/openai/anthropic_types.go`
- `apps/edge/internal/openai/anthropic_bridge_test.go`
- `agent-contract/outer/anthropic-compatible-api.md`
- `agent-roadmap/phase/knowledge-tool-optimization-extension/milestones/iop-owned-single-request-agent-execution.md`
- `agent-roadmap/sdd/knowledge-tool-optimization-extension/iop-owned-single-request-agent-execution/SDD.md`
- `agent-test/dev/rules.md`
- `agent-test/dev/edge-smoke.md`
- `scripts/e2e-single-request-claude.sh`
- `scripts/e2e-credential-slot-smoke.sh`
- `user_review_7.log`

### SDD Criteria

S12 requires one real Claude request, ingress delta 1, ordered Gemini -> Ornith-fast -> Gemini stages, redacted stage/total timing, verified workspace result and cleanup, and one terminal. Failed or pre-ingress calls cannot qualify S12 and cannot publish success-only owners.

### Verification Context

- Runner: `toki@toki-labs.com` (Darwin/arm64); isolated source `/Users/toki/agent-work/iop-s12-validation-20260808/source`; workspace `/Users/toki/agent-work/iop-s12-validation-20260808/workspace`; managed root `/Users/toki/agent-work/iop-s12-managed-validation-20260808`.
- Canonical `/Users/toki/agent-work/iop-dev` remains read-only. Claude executable is `/opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/bin/claude.exe`; base is `https://127.0.0.1:18483`; model is `iop-single-request-light`.
- SOPS `tokens.toki-dev-cline` authenticates Claude only to IOP and stays in process memory.
- Certificate refresh may use only the existing deterministic credential-smoke with local fake providers, recoverable backups, and disposable runtime restart. It must not call a model or alter canonical dev/provider state.

### Test Coverage Gaps

Repository/provider-free compatibility is covered. Only one admitted real execution can prove S12.

### Symbol References

No source symbol changes are planned in this execution packet.

### Split Judgment

TLS readiness, the fifth guard, sole live call, cardinality, stage/workspace/terminal evidence, and PASS-only publication are one indivisible external-verification packet.

### Scope Rationale

Exclude direct provider requests, retries, a sixth guard, speculative compatibility fields, canonical dev mutation, dispatcher/Pi execution, and common Agent-Ops changes.

### Final Routing

- `evaluation_mode=isolated-reassessment`; `finalizer=finalize-task-policy.sh`; `finalizer_mode=pair`.
- Build `worker/cloud/G10`; review `review/cloud/G10`; `base_route_basis=grade-boundary`; scores `2/2/2/2/2`; `large_indivisible_context=true`.
- Loop risks: `temporal_state`, `concurrent_consistency`, `boundary_contract`, `variant_product`; count 4.
- `review_rework_count=18`, `evidence_integrity_failure=false`.

## Implementation Checklist

- [x] Renew expired disposable managed TLS deterministically and prove no model/guard activity during setup.
- [x] Pass fresh local and remote provider-free gates against the exact candidate and renewed runtime.
- [x] Create `sole-live-5` and execute exactly one authorized Claude-through-IOP call with no retry.
- [x] Publish stable S12 evidence and bounded qualification owners only on complete schema-valid PASS.
- [x] On failure, retain only closed diagnostics and make no success claim.
- [x] Fill implementation-owned review sections and stop for official review.

### REVIEW_API-1 — Restore disposable TLS readiness

Use the existing deterministic credential-smoke material generator, retain uniquely named recoverable backups, install only disposable managed CA/leaf keys, restart CP/Edge/Node, and require more than 900 seconds of certificate lifetime plus healthy process/fleet/catalog state. No fifth guard or model call may occur.

### REVIEW_API-2 — Freeze the exact repaired candidate

Rerun focused/race/harness/diff tests and the exact provider-free matrix: baseline, advanced beta, defer-loading, redacted beta, display omitted, and display summarized 200; strict, eager input streaming, and invalid display 400. Require zero ingress/activity, zero Claude process, four finalized guards, no fifth guard/result/manifest, and harness preflight PASS.

### REVIEW_API-3 — Execute one guarded call

Use the exact executable-name detector, atomically create `sole-live-5.started`, run the harness once with fresh temporary Claude config, renewed managed CA, and in-memory SOPS caller, capture closed `live_rc`, and rename the guard to `sole-live-5.rc-N`. Never retry.

### REVIEW_API-4 — Publish or close

On complete PASS only, validate/publish the redacted manifest and synchronize explicit S12-deferred contract/spec owners. On failure, leave those owners untouched and record only status/class/reason, ingress/process cardinality, safe stage families/timings if any, artifact presence, guard, and no-retry proof.

## Final Verification

1. Local focused/race/harness-self-test/diff checks.
2. Deterministic disposable TLS refresh with recoverable backups and zero model/guard activity.
3. Remote runtime identity, certificate, fleet/catalog/status matrix/activity/process/guard/artifact checks and harness `--preflight-only`.
4. One `sole-live-5` harness `--run`, no retry.
5. PASS-only manifest/owner publication or closed failure evidence; final hygiene.

After execution, fill implementation-owned sections in `CODE_REVIEW-cloud-G10.md`.
