Imported from nkrasnogor/boot-template (AGENTS.md). Install upstream with npx skills add nkrasnogor/boot-template. Copyright stays with the author.

Boot Template Agent Operating Manual

This file defines persistent standards for any autonomous agent working in this repository.

Mission

Ship changes in small, reviewable increments with deterministic setup, repeatable CI, and minimal user intervention.

Access And Execution Policy

• Working directory: full read/write access within this repository only.
• Network: allowed for package installation, documentation lookup, GitHub operations, and CI/CD actions.
• Shell behavior: run non-interactive commands only. Never require prompts like "Press Y to continue".
• Safety: avoid destructive commands unless explicitly requested.

Canonical Commands

• Setup: make setup
• CI: make ci

Every code change must keep both commands green.

Standard Delivery Loop

1. Pull latest main and create a short-lived branch: codex/<topic>.
2. Pick the highest-priority unchecked item from TASKS.md.
3. Implement the smallest useful slice.
4. Run make ci locally.
5. Commit with a clear, tagged message and focused diff.
6. Push branch and open/update PR.

Git Standards

• Use incremental, well-scoped commits (one purpose per commit).
• Commit format:
  • Subject: [tag] Imperative summary
  • Tags: feat, fix, refactor, test, doc, style, chore.
• No force-push to main.
• Keep PRs small enough to review quickly.

Dependency And Build Standards

• Dependencies must be pinned in uv.lock.
• Use uv for environment sync (uv sync --all-groups --frozen).
• Do not introduce tooling that requires manual local setup steps without documenting it in README.md and wiring it into make setup.

Test And Reliability Standards

• Tests must be deterministic and fast.
• No network dependence in unit tests.
• Seed randomness explicitly when used.
• Mark or remove flaky tests before merge.
• CI failures block merges.

Lint/Format Standards

• Formatting and linting are automated through pre-commit and ruff.
• Pre-commit hooks run on commit/push and in CI.
• Keep the repository free from generated noise and transient files.

CI/CD Standards

• CI runs on every PR and every push to main.
• CD release workflow runs on version tags (v*) after CI passes.
• Any deployment workflow must be non-interactive and secret-driven.

Definition Of Done

• Relevant TASKS.md item updated.
• make ci passes locally.
• Docs updated for behavioral/tooling changes.
• Commit(s) pushed with clear messages.