chore(agents): refresh the dogfood AGENTS.md and pin it to the packaged block

[PathGao]

Summary

The repo's own AGENTS.md carried an older revision of the always-on block than what graphify install writes for users from graphify/always_on/agents-md.md: it still told agents to read GRAPH_REPORT.md first and to navigate wiki/ unconditionally, while the packaged block moved to query-first rules and the "if wiki exists" soft-guard. (The unconditional wiki wording is the same surface #2006 flags.)

Two changes:

1. Refresh: AGENTS.md is regenerated by applying the real splice (_replace_or_append_section + _always_on("agents-md")) — byte-for-byte what an install would produce.
2. Pin: a new test runs that same splice against the checked-in file and requires a no-op, so any future edit to the packaged block forces the dogfood copy along in the same PR. Verified it fails against the pre-refresh file and passes after.

No behavior change for users — the packaged block is untouched; only the repo's own copy catches up.

🤖 Generated with Claude Code

[graphify-labs]

Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).

Graphify reviewed this change.

Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).

---

Graphify review — findings

This PR updates the repo's AGENTS.md graphify section, rewriting the rules to emphasize a query-first workflow (graphify query/path/explain) and adding guidance about the /graphify command and handling dirty graph files. It also adds a new test (tests/test_always_on_dogfood.py) that runs the real install splice logic against the repo's own AGENTS.md and asserts it matches the packaged graphify/always_on/agents-md.md block. The intent is to keep the dogfooded AGENTS.md in sync with the packaged block that gets installed for users.

No blocking issues surfaced. 1 lower-confidence candidate did not survive cross-model review.

Analysis details — impact, health, verification

Impact & health

Graphify review

Impact — 5 functions depend on the 5 node(s) this change touches.

Health — grade A; no new coupling hotspots.

Verification — 5 functions in the blast radius were not formally verified this run (proofs are advisory here).

Gate & verification

graphify gate

PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.

Advisory (not blocking):

• verification_scope: 5 function(s) in the blast radius were not formally verified this run