feat(agents-canon): AGENTS.md canon everywhere — bootstrap v2.0.0 writes AGENTS.md + CLAUDE.md pointer; 15 skills retarget triggers/rule refs from CLAUDE.md to AGENTS.md (semver bumps); dist rebuilt

README.md

@@ -54,12 +54,12 @@ project's folder and it will, in one pass:
 - create a starter `README.md`
 - lay out `.wiki/` per the [Karpathy LLM Wiki pattern](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) (delegated to [`setup-wiki`](skills/setup-wiki/))
 - lay out `.tasks/` with the canonical task board (delegated to [`setup-tasks`](skills/setup-tasks/))
-- write `CLAUDE.md` with skill triggers (`use project wiki`, `use task management system`, `check across all projects`, `we're on Windows`)
+- write `AGENTS.md` (canon) with skill triggers (`use project wiki`, `use task management system`, `check across all projects`, `we're on Windows`) plus a `CLAUDE.md` legacy pointer
 - record the skill versions used in `.wiki/concepts/bootstrap-manifest.md` so cross-project layout drift stays debuggable
 
 Two modes, picked automatically: **init** for an empty folder, **upgrade**
 for an existing project (the skill only fills the gaps and never overwrites
-without explicit confirmation). On upgrade, `CLAUDE.md` is merged
+without explicit confirmation). On upgrade, `AGENTS.md` is merged
 idempotently — only canonical trigger lines that aren't already present are
 appended after explicit confirm, so re-running `project-bootstrap` after a
 template change picks up the new triggers without duplicating the old ones.
@@ -146,7 +146,7 @@ skills/
 │   └── build-hermes.py
 ├── .wiki/                  ← design docs, notes
 ├── .tasks/                 ← STATUS.md
-├── CLAUDE.md
+├── AGENTS.md              ← canon (CLAUDE.md is a legacy pointer)
 └── README.md               (this file — see README.ru.md for Russian)
 ```