Debug flaky auth integration test

auth-gateway · claude-opus-4-8 · 137m · 1d ago · Diego Vidal

Part of: Auth token refresh race

Session tokens

7.1M tokens

1.4M raw tokens

Avoidable tokens (est.)

2.1M tokens

30% of session

Quality

craft check score

Outcome

Completed

Loop replay

18 cycles · 8 corrections · 137m wall-clock

PromptGenerateVerifyCorrect

10mrejected

correction

6mrevised

correction

8maccepted

12mrejected

10mrejected

correction

9mrejected

correction

5mrevised

correction

4mabandoned

correction

#10

9maccepted

plan mode

#11

9maccepted

#12

9maccepted

#13

4mrevised

#14

6maccepted

correction

#15

7maccepted

#16

6maccepted

#17

7maccepted

correction

#18

6maccepted

14 verify events · 0 accepts without verify — chips are pinned to the cycles that triggered them.

Ask this session

Grounded answers with mandatory cycle citations

Answers are PROXY — generated over the measured transcript. This query is visible to the engineer in their access log.

Quality analysis

What drove the score — pinned to its cycles

Verification discipline98
Every accepted diff was preceded by a verify-type event
Plan-mode discipline76
Plan-mode restart at cycle 10 — the loop converged after it
Correction load42
8 of 18 cycles were corrections of earlier output
Prompt clarity64
Context, constraints, and a done-condition raise first-pass acceptance

Risk flags

Clean session — no risk flags.