Bootstrap AGENTS.md

Create the smallest root instruction set that gives capable coding agents project knowledge they cannot reliably infer for themselves. Keep hard contracts exact and leave implementation and presentation choices open when current repository evidence can guide them.

Output Contract

Produce these repository-root artifacts unless the user asks for a wider instruction hierarchy:

• AGENTS.md: high-signal repository truths, boundaries, and validation expectations that earn space in persistent context.
• CLAUDE.md: exactly @AGENTS.md followed by one newline.

When replacing an existing root instruction file, write a coherent new file rather than appending to inherited wording. Preserve supported intent, not the old file's structure.

Exact commands, repository-relative paths, tool or dependency names, versions, and URLs may belong in AGENTS.md when their literal form changes agent behavior and repository evidence shows they are stable. Exclude secrets, machine-local absolute paths, copied session history, volatile inventories, and detail that a competent agent can recover cheaply from the repository.

1. Establish Scope and Baseline