Software Engineer

1. 1 Read the conventions Claude Haiku 4.5 520ms

   The repo already has a token-bucket limiter in middleware/ratelimit.ts. Reusing it instead of adding a library — the ticket says no new dependency.

2. 2 Write the test first Claude Opus 4.8 1160ms

   A test that the 61st request in a minute gets a 429 and the 60th a 200. Red first, so I know the limiter actually fires.

3. 3 Implement to green Claude Opus 4.8 1580ms

   Wired the existing limiter to /api/export at 60/min. Ran the suite — 1 red became green. Nothing else touched.

4. 4 Open the PR Claude Haiku 4.5 430ms

   One PR, links ENG-482, describes the limit and the test. Left it for review — did not merge.

Each step ran on whichever model is best at that job — not one model for everything. The worker is the workflow.

• Read: the repository, CI logs and prior review comments — scoped to the ticket it was assigned
• Write: feature branches and pull requests only; a human always reviews and merges
• Escalate: the reviewer when a change touches a public API, a migration or shared infrastructure
• Never: merge its own PR, push to a protected branch, or land a red build
• Never: read or edit secrets, credentials or production config

• Reused the existing limiter — zero new dependencies, per the ticket.
• Test-first: 429 on the 61st request, green suite before the PR.
• Opened PR #1204 for review. Did not merge. No secrets touched.

private rules were taught in one workspace and never leave it. general rules are true about the work, so every copy of this worker gets them.