chore(docs): update AGENTS.md to reflect recent changes

[RedStar071]

Summary

Weekly AGENTS.md audit. No pull requests merged into main in the review window (2026-09-07 to 2026-09-14) — the most recently merged PR is #99 (2026-08-15).

While verifying AGENTS.md's current accuracy against the live codebase, I found the "Cursor Cloud specific instructions → Infrastructure (PostgreSQL)" section references a compose.dev.yml file that has never existed anywhere in this repo's history — the actual Docker Compose file is .docker/compose.yml. An agent following the doc verbatim gets a no configuration file provided error and can't start Postgres.

This was previously flagged and a fix attempted in #93, but that PR was closed unmerged (draft, blocked) before landing a correction.

While fixing the path, I also verified against .docker/compose.yml that its postgres-data volume is declared external: true, meaning docker compose ... up postgres -d fails on a fresh environment unless the volume is created first — nothing else in the repo creates it. Added docker volume create postgres-data as a one-time prerequisite step so the corrected command actually succeeds end-to-end.

Everything else in AGENTS.md / .github/copilot-instructions.md was cross-checked against package.json scripts, src/main.ts / src/lib/setup/all.ts env loading, and @wolfstar/env-utilities's actual .env.local override behavior, and remains accurate.

Changes

• AGENTS.md: fix compose.dev.yml → .docker/compose.yml, and document the postgres-data external-volume prerequisite.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XQphY6Eend9vygFaeFRkNQ

---

Generated by Claude Code

Confidence Score: 5/5

Safe to merge: the documented PostgreSQL startup flow matches the repository configuration.

No issues were found, and the documented volume, Compose file, and service name were checked against the configuration.

Files Needing Attention: None.

T-Rex Logs

What T-Rex did

• Authored a narrow contract-check that compares the PostgreSQL commands in AGENTS.md with the relevant service and volume declarations in .docker/compose.yml, and verified that postgres-data is declared external, mounted by PostgreSQL, created by the documented command, and that the documented Compose invocation targets the postgres service; the five contract checks passed with exit code 0.
• Executed the authored validation script from the repository; it passed all five contract checks with exit code 0.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "docs(agents): fix stale compose.dev.yml ..." | Re-trigger Greptile}

[coldtea-pr-lens]

◈ PR Lens

🟢 +0 new · 🟠 ~1 changed · 🔴 -0 removed · 0 flows · 1 file · commit 47eb1a3

Architecture

1 component touched across 2 lanes.

Open the interactive canvas

Data flow

No data-flow sequence changed in this PR.

View

• Architecture lens
• Data flow lens
• Expand every detail

Tip

Push a commit and the comment redraws for the new head. A slow older run never overwrites a newer one.

🪧 More tips

• Run npx skills add coldteadotai/pr-lens, then tell your coding agent: "Diagram the change you just made with PR Lens and attach it to the pull request."
• Run npx @coldtea/pr-lens-cli analyze --base origin/main on a branch, then npx @coldtea/pr-lens-cli render .pr-lens/graph.json. Same lenses, your own model key, before the pull request exists.
• Untick Architecture lens or Data flow lens under View to hide a diagram, or tick Expand every detail to open every section. The comment redraws in a few seconds.
• Click the link under each diagram to open it on a canvas you can zoom, pan and step through.
• The diagrams are links. Click one to open it on the canvas, then press W or click play to walk through the change.
• Open a diagram on the canvas, then press W or click play to walk through the change one step at a time.
• The CLI's render reads .github/pr-lens.yml and applies your renames, exclusions and lane pins at draw time.
• Set github.comment.collapsed: true in .github/pr-lens.yml to fold the comment behind one View architecture and data flow row. Drawing still runs on every push.
• Add .github/workflows/pr-lens.yml with coldteadotai/pr-lens/packages/action@v0 and your model provider's key as its api-key to run PR Lens from your own CI. Any /chat/completions endpoint works.
• Switch GitHub to dark mode and the diagrams follow. The moving dots are this pull request's data in motion.

---

Thanks for using PR Lens! It's built by Coldtea, free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn