git:20260818.7d50313 to git:20260818.4293a53

23 added, 12 removed. Audit A to A.

# TARSy - agent guide

- Default branch: `master`.

+ TARSy is a hybrid Go + Python SRE system: Go orchestrator (alerts, sessions, MCP tools), a stateless Python LLM service over gRPC, and a React dashboard.

- ## Commands

+ Default branch: `master`. Architecture and package map: `CLAUDE.md`.

- - Lint: `make lint`

- - Test: `make test`

- - Full local gate: `make check-all`

- - Never invent alternate package-manager commands if the above work.

+ ## Commands

- Stack notes (do not invent substitutes):

+ Never invent alternate package-manager commands if these work.

- - Go backend: `make test-unit`, `make test-go`, `make build`

+ - Full local gate: `make check-all`

+ - Lint: `make lint` (`make lint-fix` to auto-fix)

+ - Test: `make test`

+ - Format: `make fmt`

+ - Dev: `make doctor`, `make setup`, `make dev`, `make dev-stop`

+ - Go: `make test-unit`, `make test-go`, `make build`

- Python LLM service: `make test-llm`

- Dashboard: `make test-dashboard`

- - Format: `make fmt`

+ - Codegen: `make ent-generate`, `make proto-generate`

+ - Migrations: `make migrate-create NAME=add_feature` — then apply the `db-migration-review` skill

- Also read `CLAUDE.md` and skills under `.cursor/skills/` (symlinked for Claude Code) before substantive edits.

+ ## Skills

+ Project skills live in `.cursor/skills/` (symlinked as `.claude/skills/`). Load a skill when its description matches the task. Do not preload all of them.

+ ## How we work

+ - Don't assume; surface tradeoffs and ask when unclear

+ - Minimum code that solves the problem; no speculative features or abstractions

+ - Touch only what you must; no drive-by refactors

+ - Define success criteria and verify before finishing

## Commits and PRs

- Never commit, amend, or push unless the user explicitly asks in this turn

- “Make the change”, “fix the tests”, or finishing a task is not permission to commit

- If it is unclear, leave changes uncommitted and ask

- Prefer small, focused PRs

- Fixes should reference an issue: `Fixes #123`

## Style

- Match existing code; do not reformat unrelated files

- Prefer clear names over clever abstractions

- No AI walls of text in PR descriptions

- - Avoid drive-by refactors

## Safety

- Do not commit secrets

- Do not weaken CI, auth, or permission checks without an explicit human request

- Ask before large architectural changes

## Learnings

- When using `/learn`, append **non-obvious** discoveries to the nearest relevant `AGENTS.md` (package-level preferred over root).

+ When using `/learn`, append **non-obvious** discoveries to the nearest relevant `AGENTS.md` (package-level preferred over root). Do not create empty nested files.