Makefile section: credit pre-AI origin, authoritative because it IS the tooling

OPENCLAW_TRICKS.md

@@ -542,13 +542,22 @@ the repo works:
 > developer would do regularly. If someone checks out the repo and types
 > `make<tab>`, they should see every meaningful operation available.
 
-This matters for AI agents because:
+This isn't an AI-specific pattern — it predates agents entirely. A Makefile in
+every repo has always been good engineering practice because it gives any new
+developer (human or AI) a plain, direct, authoritative reference for how to
+interact with the repo. It's authoritative _because it's how we actually invoke
+the tools_ — it's not documentation that can drift from reality, it IS the
+reality. `make<tab>` shows you everything you can do. No wikis to read, no
+READMEs to hope are up-to-date.
 
-- The agent always uses `make test`, never `go test ./...` directly
+For AI agents specifically, this is even more valuable:
-- If the test command needs flags, timeouts, or environment setup, it's in the
+
-  Makefile — the agent doesn't need to know the details
+- The agent always uses `make test`, never `go test ./...` directly — the
+  Makefile encapsulates flags, timeouts, environment setup
 - A new sub-agent spawned on any repo can immediately see every available
-  operation
+  operation without reading docs or asking questions
+- The human never has to explain "how to run the tests" — it's always
+  `make test`, everywhere, every repo
 
 #### Pre-Commit Hooks