agent-context-bootstraplisted

# Agent Context Bootstrap ## Goal Create or improve repo-local agent context so future agents can work from the repository's real commands, docs, issue tracker rules, domain language, ADRs, validation commands, and skill routing without overwriting existing instructions. ## When to use - A repository lacks `AGENTS.md` or agent-facing docs. - The user wants Codex, Claude Code, Cursor, or another agent to follow local workflow rules. - A repo needs issue tracker notes, triage labels, domain docs, ADR locations, or validation commands documented. - A downstream repo needs predictable first-run agent setup before using workflow skills. ## When not to use - The user only wants a one-time handoff; use `handoff`. - The user wants a repo health report without changing context files; use `repo-health-audit`. - The repository already has clear agent instructions and the user did not ask for edits. - The user wants to publish a skill catalog; use `skill-repo-curator`. ## Inputs to inspect - Existing `AGENTS.md`, `CLAUDE.md`, `.codex/`, `.cursor/`, `CONTEXT.md`, `CONTEXT-MAP.md`, and docs files. - `README.md`, package files, validation scripts, CI workflows, issue templates, labels, and `.github/`. - `docs/adr/`, architecture docs, domain docs, and existing `docs/agents/`. - Maintainer-provided issue tracker, triage labels, validation commands, runtime conventions, and domain-specific workflow notes. - `git status --short` before editing. ## Workflow 1. Inspect current agent in