<!-- task=m-iop-owned-single-request-agent-execution/03+02_single_ingress plan=2 tag=API milestone-task=single-ingress -->

# Code Review Reference - API

> **[IMPLEMENTING AGENT — READ FIRST] Filling in this file is the mandatory final step of implementation.**
> The task is NOT complete until every implementation-owned section below is filled in.
> Complete the `Implementation Checklist`; the final checklist item is mandatory before saving.
> Fill implementation-owned sections, then stop with active files in place and report ready for review.
> Execute the plan's selected root cause, scope, files, and dependency decisions as written. Do not choose another owner, narrow/expand the write boundary, or replace a fix with another verification attempt.
> If implementation is blocked, record the exact blocker, attempted commands/output, and resume condition only in implementation-owned evidence fields.
> Do not ask the user directly, present choices, call user-input tools, create control-plane stop files, or classify the next state.
> Finalization (`Code Review Result`, log rename, `complete.log`, archive moves, `Review-Only Checklist`) is review-agent-only, even after compaction/resume.
> Follow the ownership table at the bottom of this file for which sections you own.

## Overview

date=2026-08-06
task=m-iop-owned-single-request-agent-execution/03+02_single_ingress, plan=2, tag=API

## Archive Evidence Snapshot

- Superseded refined pair: `plan_cloud_G09_1.log`, `code_review_cloud_G10_1.log`.
- The superseded pair contained no implementation evidence or review verdict; implementation has not started.
- Fresh-context correction: S01 now has a runtime Edge ingress counter and a real HTTP POST counter-delta assertion, and dependency evidence uses the exact active-or-single-archive candidate rule. Coordinator/state ownership remains in the surface-neutral `service` package, `repairing` remains in the approved state machine, and endpoint integration keeps a separate optional interface instead of widening the legacy `runService` contract.

## For the Review Agent

> **[REVIEW AGENT ONLY]** The finalization steps below are review-agent only. Implementing agents must not execute this section.

Compare implementation of each item against source files and verify that output in `Verification Results` matches code.
Review completion means the following steps are finished:

1. Append verdict and `review_rework_count` / `evidence_integrity_failure` routing signals.
2. Archive `CODE_REVIEW-cloud-G10.md` → `code_review_cloud_G10_2.log` and `PLAN-cloud-G09.md` → `plan_cloud_G09_2.log`.
3. If PASS, write `complete.log` and move active task directory to `agent-task/archive/YYYY/MM/m-iop-owned-single-request-agent-execution/03+02_single_ingress/`. If WARN/FAIL, fully write the next filesystem state required by the code-review skill.
4. If PASS, preserve `milestone-task=single-ingress` in `complete.log` and report it for runtime aggregation. Roadmap state evaluation belongs to `sync-milestone-workstate`.
5. Check applicable `Review-Only Checklist` items at the final `.log` location before reporting.

---

## Implementation Item Completion

| Item | Status |
|------|--------|
| API-1 Implement the coordinator in service | [ ] |
| API-2 Admit marked Anthropic requests exactly once | [ ] |
| API-3 Synchronize the coordinator boundary | [ ] |

## Implementation Checklist

- [ ] Implement the surface-neutral request-local coordinator, executor port, complete approved state graph including repair/internal-tool resume, immutable admission, cancellation, and one-shot endpoint terminal acknowledgement before `completed`.
- [ ] Route marked Anthropic Messages requests through a separate optional service capability before legacy admission, increment one bounded runtime Edge ingress counter, keep one HTTP lifetime, and prove one real POST plus counter delta `+1` with a multi-stage fake.
- [ ] Preserve unmarked Anthropic, Chat, and count-tokens behavior; expose only sanitized progress/final/error values and synchronize the boundary documents.
- [ ] Run dependency, targeted race, package, vet, full Edge regression, and `git diff --check` verification.
- [ ] Fill implementation-owned sections in CODE_REVIEW-*-G??.md with actual implementation notes and verification output.

## Review-Only Checklist

> **[REVIEW AGENT ONLY]** This checklist is used only by the review agent.
> Implementing agents must not modify or check this section.

- [ ] Append one verdict of `PASS`, `WARN`, or `FAIL` and verified `review_rework_count`, `evidence_integrity_failure` to `Code Review Result`.
- [ ] Verify that verdict, `Dimension Assessment`, and Required/Suggested/Nit classifications match.
- [ ] Archive active `CODE_REVIEW-*-G??.md` to `code_review_cloud_G10_2.log`.
- [ ] Archive active `PLAN-*-G??.md` to `plan_cloud_G09_2.log`.
- [ ] Verify that the Agent-Ops managed block in `.gitignore` unignores `agent-task/**/*.md` and `agent-task/**/*.log` and ignores `agent-roadmap/current.md`.
- [ ] If PASS, write `complete.log` based on `agent-ops/skills/common/code-review/templates/complete-log-template.md` and leave no active `.md` files.
- [ ] If PASS, move active task directory `agent-task/m-iop-owned-single-request-agent-execution/03+02_single_ingress/` to `agent-task/archive/YYYY/MM/m-iop-owned-single-request-agent-execution/03+02_single_ingress/` and update this checklist at the final archive path.
- [ ] If PASS, preserve and report `milestone-task=single-ingress` for runtime aggregation, without modifying roadmap or directly calling `update-roadmap`.
- [ ] If PASS for split work, remove empty active parent `agent-task/m-iop-owned-single-request-agent-execution/` or verify it was kept due to remaining siblings/files.
- [ ] If WARN/FAIL, write the next filesystem state matching code-review verdict and do not write `complete.log`.

## Deviations from Plan

_Record any deviations from the plan and the rationale here._

## Key Design Decisions

_Record key design decisions here._

## Reviewer Checkpoints

- Packet 02 completion evidence existed before implementation.
- Coordinator/state ownership is in `service`; no endpoint wire type crosses into it.
- All approved states, especially `repairing` and saved-stage `internal_tool`, are tested.
- Success remains `finalizing` until one endpoint terminal acknowledgement; duplicate/write-failure/cancel races cannot also complete.
- Exactly one outcome wins and all executor work is cancelled/joined.
- Marked routing precedes legacy pool/continuation; one real HTTP POST increments the bounded runtime Edge ingress counter exactly once, regardless of internal stage count.
- Public output has no reasoning, tool wire, provider/route/credential/workspace data, or caller `tool_use` continuation.

## Verification Results

### Dependency

Command: `test -f agent-task/m-iop-owned-single-request-agent-execution/02+01_preset_binding/complete.log || test "$(compgen -G 'agent-task/archive/*/*/m-iop-owned-single-request-agent-execution/02+01_preset_binding/complete.log' | wc -l)" -eq 1`

_Actual output/status:_

### Coordinator race and state graph

Command: `go test -race ./apps/edge/internal/service -run 'TestSingleRequest' -count=1`

_Actual output:_

### One runtime-counted ingress and compatibility

Command: `go test ./apps/edge/internal/openai -run 'Test(AnthropicSingleRequest|PresetRequestIdentityAcrossAnthropicTurns|PresetRequestIdentityAnthropicCountTokensBypassesCoordinator)' -count=1`

_Actual output:_

### Documentation

Command: `rg --sort path -n 'single-request|one POST|repairing|tool_use|count_tokens' agent-contract/outer/anthropic-compatible-api.md agent-spec/input/openai-compatible-surface.md agent-spec/runtime/edge-node-execution.md`

_Actual output:_

### Final regression

Commands:

- `go test ./apps/edge/internal/service ./apps/edge/internal/openai -count=1`
- `go vet ./apps/edge/...`
- `go test ./apps/edge/... -count=1`
- `git diff --check`

_Actual output:_

---

> **[IMPLEMENTING AGENT — BEFORE SAVING] Have you filled in every implementation-owned section?**
> If anything is blank, go back and fill it in before saving this file.
> Leave review-agent-only sections unchanged.

## Section Ownership

| Section | Owner | Note |
|---------|-------|------|
| Header comment, Overview, Review Agent Instructions | Fixed at stub creation | Implementing agent must not modify or execute these (archive, complete.log, and task-directory archive move are review-agent only) |
| Archive Evidence Snapshot | Fixed at stub creation from plan when present | Implementing agent uses it as default prior-loop context; read only the specific archive files cited there when more detail is required |
| Implementation Item Completion (item names) | Fixed at stub creation | Implementing agent checks `[ ]` → `[x]` only |
| Implementation Checklist (item text/order) | Fixed at stub creation from plan | Implementing agent checks `[ ]` → `[x]` only |
| Review-Only Checklist | Review agent only | Implementing agent must not modify or check this section |
| Deviations from Plan, Key Design Decisions | Implementing agent | Replace placeholder text with actual content |
| Reviewer Checkpoints | Fixed at stub creation | Pre-filled from plan |
| Verification Results (section headings + commands) | Fixed at stub creation | Implementing agent fills in command output only; command changes require a `Deviations from Plan` entry |
| Code Review Result | Review agent appends | Not included in stub |
