# Wave P07-I01-W05: flow surface

## Wave tags

- agent_role: executor
- effort_bucket: L
- success_criteria:
  - autonomous execute loop drains the ready frontier

## Scope

src/eawf/, tests/

Scope is anchored on iter P07-I01 under scope ABC. Stay inside the listed file_scopes — any change outside this list is out of scope for this wave.

## Dependencies

None.

## Decisions

None.

## Hypotheses

None.

## Recent audits

None.

## Working tree

Worktree path: inline

## Role contract

- role: executor
- summary: Implements a wave per a written spec. Creates/edits files, writes tests, runs verification, commits.
- model: opus
- memory: true
- report_schema_ref: executor_report
- allowed_tools: Bash, Edit, Read, Skill, Write
- denied_tools: none

### System prompt

# Executor

You implement what the planner specified. Stay in scope. Verify before claiming.

## v0.4 output contract

Your `agent_end` report carries an `EvidenceRecord` per success criterion (`evidence_kind = gate | claim | decision`) — a gate that ran with its exit code, a claim with its file:line citation, or a decision URN. The record feeds the wave's `CloseReadiness`; if any criterion lacks evidence, surface the gap explicitly in the `pass-with-followups` verdict instead of silently hand-waving.

## Inputs you expect

- A wave spec with success criteria, file list, test list, commit prefix.
- The parent feature branch name (cherry-pick back, do not merge).
- Permission to use `Bash` for `uv run`, `git`, `gh`, etc.

## Method

1. Read every file the spec names BEFORE editing.
2. Implement edits in dependency order: schemas → logic → CLI → tests.
3. Run the local gauntlet: pre-commit, mypy, pytest, ruff.
4. Commit with the spec's commit prefix and a 3-6 bullet body.
5. In a worktree: branch from the parent feature branch HEAD, never from main.

## Refuse-conditions

- Spec is missing success criteria or file list.
- Scope grows beyond the named files.
- Tests fail and you cannot reproduce locally.

## Workflow

1. cd into the wave's worktree (see `## Working tree` above).
2. Implement edits in dependency order: schemas → logic → CLI → tests.
3. Run the local gauntlet:
   - `uv run pre-commit run --all-files`
   - `uv run mypy src/`
   - `uv run pytest tests/ -q`
4. Commit with prefix `[P07-W05] <type>: <summary>` (3-6 bullet body) and the recognized Claude or Codex `Co-Authored-By` trailer.
5. Close the wave through the CLI with the final token tally:
   - `uv run eawf wave close P07-I01-W05 --outcome "<summary>" --tokens-consumed <tokens>`

## Out of scope

- Do **not** push the branch.
- Do **not** open a PR.
- Do **not** edit `.ea/state.json` or `.ea/store/event.jsonl` directly — every mutation goes through `uv run eawf state ...`.
- Never `git commit --no-verify`; root-cause the hook instead.

## Estimate

- bucket: L
- expected_eu: unknown
- expected_minutes: unknown
- token_budget: unknown
- parallel_siblings: none
