last update

AGENTS.md

@@ -48,4 +48,43 @@ Update only the relevant files in:
 - docs/
 - specs/
 
-Keep documentation aligned with the real implementation, not assumptions.
+Keep documentation aligned with the real implementation, not assumptions.
+
+## Git Commit Messages
+
+Use this format:
+```text
+TYPE - Short summary
+
+- First concrete change
+- Second concrete change
+- Third concrete change
+```
+Allowed types:
+`ADDED, IMPROVED, FIXED, CHANGED, REFACTORED, OPTIMIZED, REMOVED, UPDATED,
+SECURED, TESTED, DOCUMENTED, STYLED, CONFIGURED, RENAMED, MOVED, CLEANED,
+REVERTED`
+
+Rules:
+- Write commit messages in English.
+- Use uppercase type names.
+- Keep the title concise.
+- Add a blank line before the bullet list.
+- Describe only the actual changes in the commit.
+- Inspect `git diff --cached` before writing the message.
+- Do not add AI attribution or Co-Authored-By.
+- Do not create commits unless explicitly requested (see Core Rules above).
+
+## graphify (when present)
+
+- For codebase questions, if `graphify-out/graph.json` exists, run
+  `graphify query "<question>"` first. Use `graphify path "<A>" "<B>"` for
+  relationships and `graphify explain "<concept>"` for focused concepts —
+  these return a scoped subgraph, usually much smaller than
+  `GRAPH_REPORT.md` or raw grep output.
+- If `graphify-out/wiki/index.md` exists, use it for broad navigation
+  instead of raw source browsing.
+- Read `graphify-out/GRAPH_REPORT.md` only for broad architecture review or
+  when query/path/explain don't surface enough context.
+- After modifying code, run `graphify update .` to keep the graph current
+  (AST-only, no API cost).