git:20260916.a045fa9 to git:20260922.83b942f

Guidance for AI coding agents working in this repository. Human teammates should be able to follow every line too. Only rules an agent CANNOT deduce from the code live here; if a rule becomes obvious from reading the code, delete it from this file.

## Security

- Never bypass a git hook or a check: no `--no-verify`, no `-n` on commit, no `HUSKY=0`.

- Never silence a linter: no `noqa`, `@ts-ignore`, `eslint-disable`, `nosec`.

- No secrets, no personal data, no machine-specific absolute paths in any file.

## Code style

- KISS, YAGNI, DRY, SOLID, TDD, Clean Code.

- Explain it so someone who doesn't code can follow along.

## Build and test commands

## Workflow

- Green gate before "done": show the output of the check that proves it.

- A decision that always comes out the same is code, not a prompt.

- Task status convention (when a todo list exists): mark each task 🟢 done (paste the proving output) · 🟡 pending (name the next action) · 🔴 blocked on you (ask the exact question). No todo list → state status inline: done-with-proof, pending, or blocked.

## Lifecycle

- Every skill declares its own contract — lane, artifact, successor — in a `## Lifecycle` block inside its SKILL.md: follow the `Next:` a skill hands you instead of asking what comes first.

- The lanes are light (spike and bounded work — no contract), standard (`spec.html` + `plan.html`) and full (architectural, with the triggered nodes).

- Approvals are spoken: the human says approve, ok, go or close, and **you** run `ai-eng spec approve` or `ai-eng spec close` underneath. Never ask the human to type a command; never run an approval on your own initiative.

## Architecture layers

You may edit `src/**` freely; the arch-test reads `.ai-engineering/arch.rules.json` — propose layer changes there via PR, never by editing the test in silence.

## Session hygiene (context economy)

`/clear` between tasks · `/compact` before stopping, not after · batch prompting · check `/usage` when the context inflates.

## Pull requests

- Run lint and the full test suite before committing; the commit must pass everything it will face in CI.

- Add or update tests for the code you change, even if nobody asked.

- After moving files or changing imports, re-run lint and typecheck.

- Title format: `<area>: <imperative summary>` (e.g. `chain: cache verdicts per tool_use_id`).

- Commit messages: subject ≤ 50 chars; body explains WHY when it is not obvious.

## Anti-drift

This list contains only what the agent CANNOT deduce from the project.