`POKE_PROMPT.txt`

44 lines
A recent change (or a recurring failure) has put this project in a bad state. Your job: INVESTIGATE and propose a concrete patch.

CONTEXT FILES YOU SHOULD READ (in this directory if present):
- `CHANGES.md` — patches that were just applied
- `CODEX_REREVIEW.md` — re-review of those patches (regressions, missed call-sites)
- error logs, recent runs, README

STEPS:
1. Reproduce the failure mode (just by reading code/logs — do not run code).
2. Identify the SPECIFIC root cause. Don't speculate — point at file:line.
3. Decide: is this a regression introduced by the recent patches, or a pre-existing bug? State which.
4. Propose a concrete, surgical patch. Show diff-like before/after for the changed lines.
5. List any side-effects or call-sites the patch should also touch.

OUTPUT FORMAT (markdown, terse):

## Failure mode
1-2 sentences describing what's wrong.

## Root cause
file:line — the specific code that's broken — why it's broken.

## Origin
REGRESSION (cite which CHANGES.md item) / PRE-EXISTING / UNCLEAR.

## Proposed patch
```
- old line
+ new line
```
With file:line headers. Surgical only — no rewrites.

## Side-effects to handle
Bullet list of other files/lines that need similar treatment, OR `none observed`.

## Risks of the patch
1-2 sentences. What could go wrong with this fix?

CONSTRAINTS:
- Read-only. Do not modify any files.
- Cite file:line for every claim.
- Cap output at ~500 words.
- If the failure is environmental (e.g., a remote site rejecting connections), say so explicitly and don't propose code changes — propose retry/timeout/circuit-breaker patterns instead.