<!-- task=m-multi-provider-protocol-profile-native-messages/06+01,02_fixture_suite plan=1 tag=REVIEW_TEST -->

# Plan - REVIEW_TEST

## For the Implementing Agent

Filling implementation-owned sections in `CODE_REVIEW-cloud-G03.md` is mandatory. Run the verification block exactly, paste actual stdout/stderr, keep both active files in place, and report ready for review. If blocked, record only the exact blocker, attempted commands/output, and resume condition in implementation-owned evidence. Do not ask the user, call user-input tools, create control-plane stop files, classify the next state, archive logs, or write `complete.log`; finalization belongs to code review.

## Background

The fixture matrix is correct and passed fresh reviewer verification, but the prior implementation evidence reported two unsupported package failures and incorrect working-directory diagnoses. This follow-up restores trustworthy SDD S09 evidence by rerunning the exact deterministic suite in one explicitly isolated executable Go cache/temp environment and recording unabridged output without changing source behavior.

## Archive Evidence Snapshot

- `agent-task/m-multi-provider-protocol-profile-native-messages/06+01,02_fixture_suite/plan_local_G03_0.log`: original fixture-suite plan requiring all four fresh commands to exit 0 without credentials or external provider calls.
- `agent-task/m-multi-provider-protocol-profile-native-messages/06+01,02_fixture_suite/code_review_cloud_G03_0.log`: FAIL with 1 Required, 0 Suggested, and 0 Nit findings; `review_rework_count=1`, `evidence_integrity_failure=true`. Fresh reviewer runs passed all four suites under an executable isolated cache/temp environment, contradicting the recorded config/Edge failures and their path diagnoses.
- Roadmap carryover: `fixture-suite` remains the only completion target. Dependencies are satisfied by `agent-task/archive/2026/08/m-multi-provider-protocol-profile-native-messages/01_protocol_core/complete.log` and `agent-task/archive/2026/08/m-multi-provider-protocol-profile-native-messages/02+01_messages_ingress/complete.log`.

## Roadmap Targets

- Milestone: `agent-roadmap/phase/operational-observability-provider-management/milestones/multi-provider-protocol-profile-native-messages.md`
- Milestone link: [Milestone document](agent-roadmap/phase/operational-observability-provider-management/milestones/multi-provider-protocol-profile-native-messages.md)
- Task ids:
  - `fixture-suite`: deterministic, credential-free provider profile qualification
- Completion mode: check-on-pass

## Analysis

### Files Read

- `agent-task/m-multi-provider-protocol-profile-native-messages/06+01,02_fixture_suite/PLAN-local-G03.md`
- `agent-task/m-multi-provider-protocol-profile-native-messages/06+01,02_fixture_suite/CODE_REVIEW-cloud-G03.md`
- `apps/node/internal/adapters/openai_compat/protocol_profile_test.go`
- `apps/node/internal/adapters/openai_compat/openai_compat_test_support_test.go`
- `apps/node/internal/adapters/openai_compat/provider_tunnel.go`
- `apps/node/internal/adapters/openai_compat/request.go`
- `packages/go/config/provider_catalog_config_test.go`
- `apps/edge/internal/openai/anthropic_surface_test.go`
- `agent-contract/inner/edge-node-runtime-wire.md`
- `agent-contract/inner/edge-config-runtime-refresh.md`
- `agent-spec/runtime/edge-node-execution.md`
- `agent-spec/runtime/provider-pool-config-refresh.md`
- `agent-roadmap/phase/operational-observability-provider-management/milestones/multi-provider-protocol-profile-native-messages.md`
- `agent-roadmap/sdd/operational-observability-provider-management/multi-provider-protocol-profile-native-messages/SDD.md`

### SDD Criteria

`agent-roadmap/sdd/operational-observability-provider-management/multi-provider-protocol-profile-native-messages/SDD.md` is approved and unlocked. Acceptance Scenario S09 maps to Milestone Task `fixture-suite`; its Evidence Map requires a credential-free full provider fixture suite with network-disabled test results. The checklist therefore changes only the active evidence artifact and requires fresh all-pass output for the focused profile matrix, Node adapter package, config package, and Edge OpenAI package.

### Verification Context

No handoff was supplied. Repository-native preflight resolved Go at `/config/.local/bin/go` (`go1.26.2 linux/arm64`, `GOROOT=/config/opt/go`) and found that the inherited `GOCACHE` points to an inaccessible scratchpad. `/tmp` and `/config/.cache` are non-executable for compiled test binaries, while `/config/workspace` is executable. Fresh reviewer runs using an isolated directory under `/config/workspace` passed all four commands with `-count=1`. The follow-up creates one outside-repository executable temp root, records the tool/environment preflight, uses it for both `GOCACHE` and `GOTMPDIR`, and removes it on exit. No external runner, provider credential, SOPS command, curl command, or live endpoint is allowed. Confidence is high because the complete command block already passed against the current checkout.

### Test Coverage Gaps

- No source behavior gap remains: the 12-profile matrix covers JSON, driver-appropriate SSE, and provider HTTP error frames.
- The only gap is evidence fidelity: the prior review artifact omitted actual failure diagnostics and asserted causes contradicted by fresh execution.

### Symbol References

None. No source symbol changes are planned.

### Split Judgment

This remains the existing compact `06+01,02_fixture_suite` child. Predecessor index `01` is satisfied by archived `01_protocol_core/complete.log`; predecessor index `02` is satisfied by archived `02+01_messages_ingress/complete.log`. The follow-up has one independently verifiable invariant: one fresh, credential-free command block must exit 0 and be copied faithfully into the active review artifact.

### Scope Rationale

Production source, test source, contracts, specs, roadmap files, CI, credentials, and live provider calls are excluded because fresh reviewer evidence already proves the implementation and deterministic suites pass. Only the active review evidence file may change.

### Final Routing

- `evaluation_mode=isolated-reassessment`; finalizer=`finalize-task-policy.sh`, mode=`pair`.
- Build closures: scope/context/verification/evidence/ownership/decision are closed. Scores: scope=0, state=0, blast=0, evidence=2, verification=1; grade=`G03`; base=`local-fit`; `large_indivisible_context=false`; positive loop risks=`boundary_contract,variant_product` (2); `review_rework_count=1`; `evidence_integrity_failure=true`; final basis=`recovery-boundary`; route=`cloud`; canonical file=`PLAN-cloud-G03.md`.
- Review closures are closed. Scores: scope=0, state=0, blast=0, evidence=2, verification=1; grade=`G03`; basis=`official-review`; route=`cloud`; canonical file=`CODE_REVIEW-cloud-G03.md`.
- Capability gap: none.

## Dependencies and Execution Order

1. `agent-task/archive/2026/08/m-multi-provider-protocol-profile-native-messages/01_protocol_core/complete.log` satisfies predecessor `01`.
2. `agent-task/archive/2026/08/m-multi-provider-protocol-profile-native-messages/02+01_messages_ingress/complete.log` satisfies predecessor `02`.
3. Run the single isolated qualification block and record its actual output.

## Implementation Checklist

- [ ] [REVIEW_TEST-1] Replace the contradicted config/Edge failure claims with unabridged fresh output from one explicitly isolated, credential-free qualification run in which every command exits 0.
- [ ] Fill implementation-owned sections in CODE_REVIEW-*-G??.md with actual implementation notes and verification output.

### [REVIEW_TEST-1] Restore trusted deterministic qualification evidence

**Problem**

`code_review_cloud_G03_0.log:222-244` records two package failures and working-directory diagnoses that fresh reviewer execution contradicted. SDD S09 and the original plan require all four commands to exit 0 with actual network-disabled output.

**Solution**

Do not change source or test code. Run the final verification block from the repository root. In the active review, replace the prior unsupported evidence shape:

```text
Result: **Pre-existing failure** — ... path does not resolve ...
```

with the actual unabridged command stdout/stderr and explicit exit-0 result for every command. Record the isolated `GOCACHE`/`GOTMPDIR` setup and state that no credential or external provider command ran. Do not reconstruct output or reuse cached text.

**Modified Files and Checklist**

- [ ] `agent-task/m-multi-provider-protocol-profile-native-messages/06+01,02_fixture_suite/CODE_REVIEW-cloud-G03.md`: fill implementation evidence with the actual fresh preflight and four-command output; remove unsupported failure claims.

**Test Strategy**

No new test source is needed. The existing focused table and three package suites directly exercise the required S09 behavior; this item repairs evidence fidelity only.

**Verification**

Run the exact block in `Final Verification`. Expected: preflight identifies the Go tool, all four `go test -count=1` commands exit 0, the temp directory is removed on exit, and no credential or external network command runs.

## Modified Files Summary

| File | Items |
|---|---|
| `agent-task/m-multi-provider-protocol-profile-native-messages/06+01,02_fixture_suite/CODE_REVIEW-cloud-G03.md` | REVIEW_TEST-1 |

## Final Verification

```bash
review_tmp="$(mktemp -d /config/workspace/iop-fixture-suite-review-XXXXXX)"
test -n "$review_tmp"
trap 'find "$review_tmp" -depth -delete' EXIT
mkdir -p "$review_tmp/gocache" "$review_tmp/gotmp"
command -v go
go version
go env GOROOT GOCACHE GOTMPDIR
GOCACHE="$review_tmp/gocache" GOTMPDIR="$review_tmp/gotmp" go test -count=1 -v ./apps/node/internal/adapters/openai_compat -run '^TestProtocolProfileOperationURLFixtures$'
GOCACHE="$review_tmp/gocache" GOTMPDIR="$review_tmp/gotmp" go test -count=1 ./apps/node/internal/adapters/openai_compat
GOCACHE="$review_tmp/gocache" GOTMPDIR="$review_tmp/gotmp" go test -count=1 ./packages/go/config/...
GOCACHE="$review_tmp/gocache" GOTMPDIR="$review_tmp/gotmp" go test -count=1 ./apps/edge/internal/openai/...
```

Expected: every command exits 0 with fresh output. The review evidence must state that only loopback/in-memory fixtures ran and no SOPS, curl, provider credential, or live provider endpoint was invoked. Cached output is not accepted.

After completing all code changes, fill implementation-owned sections in `CODE_REVIEW-*-G??.md`.
