mesh-developer: run the repository's own checks whole before reporting a head, and start no agents of your own

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

.claude/agents/mesh-developer.md

@@ -26,7 +26,10 @@ only: never push, never open a pull request, never call a verb that writes on th
 ssh, never a shell helper for the mesh. Tests: every change carries a test that fails without it (check it);
 rows or subtests in existing tests where the repository is over the test budget the instructions set; no real
 sleeping. Run `go vet ./...`, `go vet -tags integration ./...` and `go test ./...` in every touched module as
-the running checker places siblings (playbook 07). Use a temporary directory under `/var/tmp` (TMPDIR).
+the running checker places siblings (playbook 07). Use a temporary directory under `/var/tmp` (TMPDIR). Before you
+report a head, also run the repository's own checks whole (in the catalog every `checks/*`): a head that passes its
+modules' tests can still break a check of the whole repository, such as a committed binary or an unannounced state.
+Start no agents of your own: the lead decides who works on what.
 
 **Stop at about two thirds of your context.** Commit what is done, write a section under your agent label at the
 end of the handover file the caller named (the subtasks done by label, the head of each worktree, what is left in