git:20260521.7be4545 to git:20260530.b7ff066

2 added, 26 removed. Audit A to A.

---

name: agents

description: Always-loaded project anchor. Read this first. Contains project identity, non-negotiables, commands, and pointer to ROUTER.md for full context.

last_updated: 2026-05-15

---

- # [Project Name]

- ## What This Is

- <!-- One sentence. What does this project do?

- Length: 1 sentence maximum.

- Not a tagline — a factual description of what the software does.

- Example: "A REST API for managing inventory across multiple warehouse locations." -->

- ## Non-Negotiables

- <!-- Hard rules the agent must never violate. Not preferences — rules.

- These are the things that, if broken, cause real damage to the codebase.

- Length: 3-7 items maximum. More than 7 means the list has not been prioritised.

- Example:

- - Never write database queries outside of the repository layer

- - Never commit secrets or API keys

- - Always handle errors explicitly — no silent failures -->

- ## Commands

- <!-- The exact commands needed to work on this project.

- Include: run dev server, run tests, run linter, build.

- Use the actual commands from this codebase — not placeholders.

- Example:

- - Dev: `npm run dev`

- - Test: `npm test`

- - Lint: `npm run lint`

- - Build: `npm run build` -->

+ # Metagit

## After Every Task

After completing any task: update `.mex/ROUTER.md` project state and any `.mex/` files that are now out of date. If no pattern existed for the task you just completed, create one in `.mex/patterns/`.

**Before you tell the user the work is done** — if this conversation introduced or edited project files under this repo — run **`task qa:prepush`** from the repository root (`scripts/prepush-gate.py` via `scripts/prepush-gate.zsh`). Fix failures and re-run until green. Only skip when the task was strictly read-only (no writes) or the user explicitly waived the QA gate in this thread.

## Commands (minimum)

- QA gate before hand-off / “work complete”: `task qa:prepush` (format, lint, tests, integration tests, context-aware pip-audit/bandit; optional `gitleaks` when installed)

- Full unit tests only: `task test`

## Navigation

At the start of every session, read `.mex/ROUTER.md` before doing anything else.

For full project context, patterns, and task guidance — everything is there.

+ Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.