diff --git a/CLAUDE.md b/CLAUDE.md
index f8aeaf8..fe2ecf0 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -193,8 +193,9 @@ The board has three views (header switcher):
   reads, edits, test runs, commits and card moves, with filters and expandable
   output. Sessions persist to `.sessions/*.jsonl`, so past ones can be replayed.
 - **Focus** — a heads-up display for one session: the task it holds, its live
-  TodoWrite plan, the definition-of-done checks (pytest / lint-imports /
-  frontend), and per-file diff stats from its worktree.
+  TodoWrite plan, the project's configured definition-of-done checks (a
+  `checks` file in `manager/local/` overriding the shipped default in
+  `core/`), and per-file diff stats from its worktree.
 
 Liveness comes from Claude Code hooks configured in `.claude/settings.json`:
 every session in this repo POSTs normalized events to the board via the
diff --git a/manager/local/CLAUDE.md b/manager/local/CLAUDE.md
index c7a4331..5df2766 100644
--- a/manager/local/CLAUDE.md
+++ b/manager/local/CLAUDE.md
@@ -3,3 +3,7 @@
 This file is yours — updates never touch manager/local/. Put here what an
 agent or teammate needs that the core doc cannot know: post-merge chores,
 what the driver assumes, what each local command is for.
+
+Bench's definition of done is `python3 -m unittest` and nothing else; the
+`checks` file beside this one is what the Focus view's CHECKS panel shows
+for this project.
diff --git a/tasks/task-template.md b/tasks/task-template.md
index fe3f865..d17a9db 100644
--- a/tasks/task-template.md
+++ b/tasks/task-template.md
@@ -55,9 +55,9 @@ tempting neighbours — delete rather than leave empty.
 ## Acceptance
 
 Observable outcomes, not implementation steps — review agents judge the
-diff against exactly this list. The repo's definition of done (tests pass,
-`lint-imports` clean, new behaviour covered) applies on top; don't restate
-it. Given/When/Then phrasing is welcome where it sharpens a criterion, and
+diff against exactly this list. The repo's definition of done (the
+project's configured checks pass, new behaviour covered) applies on top;
+don't restate it. Given/When/Then phrasing is welcome where it sharpens a criterion, and
 edge cases belong here too — boundaries, empty inputs, failure paths.
 
 - [ ] Something a reviewer can check without reading the diff