docs(aeon skill): refresh ci-tests triggers and the new-skill gate count

.claude/skills/aeon/SKILL.md

@@ -207,7 +207,7 @@ They just did something in this chat and want it to happen on a schedule.
 
    This is the one sanctioned exception to "never hand-edit the YAML". Validate after: `node scripts/validate-config.js`. It checks structure and schedule format, but not whether a `model:`/`harness:` override is quoted.
 
-5. **Regenerate BOTH catalogs, add the eyebrow entry, then ship it as a PR.** A new skill trips four CI gates, and **a red gate blocks the merge**: `main` requires the `gate` check, which `ci-gate` fails whenever any other check on the PR is red. Run them locally first. Commit `SKILL.md` on its own before regenerating (the catalog's `sha`/`updated` are git-derived):
+5. **Regenerate BOTH catalogs, add the eyebrow entry, then ship it as a PR.** A new skill trips six CI gates (see `references/ci.md`), and **a red gate blocks the merge**: `main` requires the `gate` check, which `ci-gate` fails whenever any other check on the PR is red. Run them locally first. Commit `SKILL.md` on its own before regenerating (the catalog's `sha`/`updated` are git-derived):
 
    ```bash
    bash scripts/check-skill-categories.sh   # category is one of the six

.claude/skills/aeon/references/ci.md

@@ -14,7 +14,7 @@ Fifteen `ci-*.yml` workflows. Fourteen are **path-filtered** and fire on `pull_r
 | `ci-packs-json` | `catalog/packs.config.json`, **`catalog/skills.json`**, `bin/generate-packs-json`, `catalog/packs.json` | pack catalog == fresh regen; every skill in exactly one pack | `bin/generate-packs-json` |
 | `ci-skill-integrity` | `skills/**`, `eyebrowlock.json`, `eyebrow.policy.json` | **every skill has an `eyebrowlock.json` entry** (hard coverage gate), then `eyebrow verify` fails on a new egress host or new critical finding | `eyebrow scan` / `eyebrow verify` (see below) |
 | `ci-readme-catalog` | `.github/README.md`, `catalog/*.json`, `docs/skill-packs.md`, `docs/aeon-setup.md`, `docs/examples/README.md`, the hero SVG | README skill tables and skill counts match the catalog | `node scripts/validate-readme-catalog.mjs` |
-| `ci-tests` | `scripts/**`, `bin/**`, `aeon.yml`, `.github/workflows/aeon.yml`, `harness-adapter/adapters/**` | the `scripts/tests/` suites + config validation | see below |
+| `ci-tests` | `skills/**`, `scripts/**`, `bin/**`, `harness-adapter/**`, `aeon.yml`, `.github/workflows/{aeon,messages,scheduler,chain-runner}.yml`, `apps/dashboard/lib/{constants,gateway-registry,harness-auth}.ts` | the `scripts/tests/` suites + config validation | see below |
 | `ci-shellcheck` | `aeon`, `scripts/**`, `bin/**`, `harness-adapter/**`, `skills/**/*.sh` | shellcheck on the tracked shell surface | `bash scripts/lint-shell.sh` |
 | `ci-harnesses-json` | `harness-adapter/adapters/**`, `harness-adapter/bin/generate-harnesses-json`, `harness-adapter/harnesses.json`, `harness-adapter/gateways.json` | committed harness + gateway manifests == fresh regen | `harness-adapter/bin/generate-harnesses-json` |
 | `ci-capabilities-parity` | `bin/install-skill-pack`, `docs/CAPABILITIES.md` | capabilities taxonomy in sync across both | `bash scripts/check-capabilities-parity.sh` |
@@ -28,7 +28,7 @@ The pack security scan in `bin/install-skill-pack` runs at *install* time, not i
 
 ## Checklist: adding or editing a skill
 
-This is the common case (Modes 4 and 5). A **new** skill trips four gates. Run all of it from the repo root before opening the PR:
+This is the common case (Modes 4 and 5). A **new** skill trips six gates: `ci-skill-category`, `ci-skills-json`, `ci-packs-json`, `ci-skill-integrity`, `ci-readme-catalog` (via the catalog files) and `ci-tests` (via `skills/**`). Run all of it from the repo root before opening the PR:
 
 ```bash
 bash scripts/check-skill-categories.sh    # category is valid

plugin/skills/aeon/SKILL.md

@@ -207,7 +207,7 @@ They just did something in this chat and want it to happen on a schedule.
 
    This is the one sanctioned exception to "never hand-edit the YAML". Validate after: `node scripts/validate-config.js`. It checks structure and schedule format, but not whether a `model:`/`harness:` override is quoted.
 
-5. **Regenerate BOTH catalogs, add the eyebrow entry, then ship it as a PR.** A new skill trips four CI gates, and **a red gate blocks the merge**: `main` requires the `gate` check, which `ci-gate` fails whenever any other check on the PR is red. Run them locally first. Commit `SKILL.md` on its own before regenerating (the catalog's `sha`/`updated` are git-derived):
+5. **Regenerate BOTH catalogs, add the eyebrow entry, then ship it as a PR.** A new skill trips six CI gates (see `references/ci.md`), and **a red gate blocks the merge**: `main` requires the `gate` check, which `ci-gate` fails whenever any other check on the PR is red. Run them locally first. Commit `SKILL.md` on its own before regenerating (the catalog's `sha`/`updated` are git-derived):
 
    ```bash
    bash scripts/check-skill-categories.sh   # category is one of the six

plugin/skills/aeon/references/ci.md

@@ -14,7 +14,7 @@ Fifteen `ci-*.yml` workflows. Fourteen are **path-filtered** and fire on `pull_r
 | `ci-packs-json` | `catalog/packs.config.json`, **`catalog/skills.json`**, `bin/generate-packs-json`, `catalog/packs.json` | pack catalog == fresh regen; every skill in exactly one pack | `bin/generate-packs-json` |
 | `ci-skill-integrity` | `skills/**`, `eyebrowlock.json`, `eyebrow.policy.json` | **every skill has an `eyebrowlock.json` entry** (hard coverage gate), then `eyebrow verify` fails on a new egress host or new critical finding | `eyebrow scan` / `eyebrow verify` (see below) |
 | `ci-readme-catalog` | `.github/README.md`, `catalog/*.json`, `docs/skill-packs.md`, `docs/aeon-setup.md`, `docs/examples/README.md`, the hero SVG | README skill tables and skill counts match the catalog | `node scripts/validate-readme-catalog.mjs` |
-| `ci-tests` | `scripts/**`, `bin/**`, `aeon.yml`, `.github/workflows/aeon.yml`, `harness-adapter/adapters/**` | the `scripts/tests/` suites + config validation | see below |
+| `ci-tests` | `skills/**`, `scripts/**`, `bin/**`, `harness-adapter/**`, `aeon.yml`, `.github/workflows/{aeon,messages,scheduler,chain-runner}.yml`, `apps/dashboard/lib/{constants,gateway-registry,harness-auth}.ts` | the `scripts/tests/` suites + config validation | see below |
 | `ci-shellcheck` | `aeon`, `scripts/**`, `bin/**`, `harness-adapter/**`, `skills/**/*.sh` | shellcheck on the tracked shell surface | `bash scripts/lint-shell.sh` |
 | `ci-harnesses-json` | `harness-adapter/adapters/**`, `harness-adapter/bin/generate-harnesses-json`, `harness-adapter/harnesses.json`, `harness-adapter/gateways.json` | committed harness + gateway manifests == fresh regen | `harness-adapter/bin/generate-harnesses-json` |
 | `ci-capabilities-parity` | `bin/install-skill-pack`, `docs/CAPABILITIES.md` | capabilities taxonomy in sync across both | `bash scripts/check-capabilities-parity.sh` |
@@ -28,7 +28,7 @@ The pack security scan in `bin/install-skill-pack` runs at *install* time, not i
 
 ## Checklist: adding or editing a skill
 
-This is the common case (Modes 4 and 5). A **new** skill trips four gates. Run all of it from the repo root before opening the PR:
+This is the common case (Modes 4 and 5). A **new** skill trips six gates: `ci-skill-category`, `ci-skills-json`, `ci-packs-json`, `ci-skill-integrity`, `ci-readme-catalog` (via the catalog files) and `ci-tests` (via `skills/**`). Run all of it from the repo root before opening the PR:
 
 ```bash
 bash scripts/check-skill-categories.sh    # category is valid