Garry Tanandcapy-ai[bot]
4d48d39e51
* feat(captain): /captain skill (also /crew), crew templates and docs/captain.md for running a crew from one controller Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * chore(captain): regenerate SKILL.md at main's version Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * feat(captain): AGENTS.md and NOTES.md templates, roles, ship lane sequence, owner device and lessons loop in docs/captain.md; owner-brief closes with the do-it reply Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(captain): review pass 1: 'do it' parses as rec, READY template matches the tool's lines, slot-2 and freeze wording, mergeChangelogs named, parameter lists and doc numbers aligned Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(captain): align the slot-call BASE merge, freeze repair and severe-race wording across skill, CREW.md and docs; router routes on phrases; receipt head width as printed Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * feat(captain): CREW.md template becomes pointers plus parameters; every crew rule gets a canonical home in gstack (lane discipline, outside contributions, stale READYs, standing spend, the lane side of flaky reruns in docs/captain.md; the rule-to-home map) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
1.1 KiB
Flaky test ledger
The daily flaky-fix pass reads this file. Append one line per flaky event under Open. The fix pass moves an entry to Fixed with its PR, or to Won't fix with a reason.
Line format:
- <date> | <case or test file> | <tier: paid/free/evaluator> | PR #<n> @ <head12> | failed <run id> | rerun passed <run id or "measured N/10"> | <symptom>
Sources: the gate runs' flake-records artifacts (every case the in-run rerun turned green) and the free suites' retried cases. Never a case that failed twice (that is a real failure), never a harness, infra or incomplete red.
A fix changes the cause: a forced probe or a regression that is red on BASE and green with the fix. Weakened assertions, raised thresholds, added trials or samples, changed case kinds, skipped cases and longer timeouts are not fixes.
Open
Last fix pass: (); see reports/.md. New entries go at the top, worst (most repeated) first.
Fixed
- | | fixed by # ()
Won't fix
- | | <reason, and who decided>