@softspark/ai-toolkit 2.11.0 → 3.0.0

package/kb/history/completed/ecosystem-deep-sweep-20260423.md

@@ -0,0 +1,273 @@
+---
+title: "Plan: Ecosystem Deep Sweep — All 12 Supported Tools"
+category: planning
+service: ai-toolkit
+doc_type: plan
+status: completed
+tags: [ecosystem, editors, generators, deep-sweep, orchestrate, drift, integration]
+created: "2026-04-23"
+last_updated: "2026-04-23"
+completed: "2026-04-23"
+completion: "100%"
+description: "Orchestrate-ready plan for a deep per-tool documentation sweep across all 12 supported tools (Claude Code + 11 editors). Each agent owns 2-3 tools: fetches docs, diffs against our generators, proposes minimal patches. Consolidation step collects results into a single changeset."
+---
+
+# Plan: Ecosystem Deep Sweep — All 12 Supported Tools
+
+**Status:** :yellow_circle: PROPOSED
+**Invocation:** `/orchestrate deep ecosystem sweep per kb/planning/ecosystem-deep-sweep-2026-04-23.md`
+**Estimated effort:** 4-6 hours orchestrated (1-1.5 h per agent in parallel)
+**Deliverable:** Per-tool drift report + concrete generator/skill patches + updated registry
+
+---
+
+## 1. Objective
+
+For every supported tool in `scripts/ecosystem_tools.json`:
+
+1. Read the current official documentation end-to-end (not just landing page)
+2. Identify every feature that ai-toolkit could integrate with but does not currently
+3. Classify each gap using the ecosystem-sync SOP taxonomy (class A-F)
+4. Produce minimal, reviewable patches for class B/D/E/F gaps
+5. Update the registry (`ecosystem_tools.json`) with new capability markers and config paths
+6. Refresh the snapshot (`benchmarks/ecosystem-doctor-snapshot.json`)
+
+**Explicit non-goals:** complete feature parity, deep refactor of generators, adding new editors to the roster.
+
+---
+
+## 2. Parallelization Strategy
+
+12 tools → **4 agents × 3 tools each** by affinity and complexity:
+
+| Agent | Role | Tools | Rationale |
+|-------|------|-------|-----------|
+| `backend-specialist` | Deep CLI / config analysis | `claude-code`, `codex-cli`, `opencode` | CLI + config.toml + agents/commands/plugins — backend integration depth |
+| `frontend-specialist` | Editor UI integrations | `cursor`, `windsurf`, `google-antigravity` | Editor-embedded AI, rule files, MCP-via-UI |
+| `devops-implementer` | Pipeline + rules tools | `github-copilot`, `cline`, `roo-code` | Rules directories, MCP JSON variants, mode configs |
+| `ai-engineer` | LLM-native tools | `gemini-cli`, `aider`, `augment` | Pure LLM workflows, minimal IDE coupling |
+
+Each agent works **in parallel**, independent file scopes (different generators). Cross-file coordination only at the registry update (single JSON file).
+
+---
+
+## 3. Per-Tool Task Template
+
+Every agent applies the **same 7-step protocol** per tool in their bucket:
+
+### Step 1 — Baseline our current integration
+
+Read these files (read-only):
+- `scripts/generate_<tool>_*.py` — every generator targeting this tool
+- `scripts/ecosystem_tools.json` — the tool's registry entry
+- `kb/reference/supported-tools-registry.md` — human docs section
+- `benchmarks/ecosystem-doctor-snapshot.json` — last-seen headings/markers/version
+
+Produce a 3-line summary: "we currently generate X, Y, Z for this tool".
+
+### Step 2 — Fetch official docs
+
+Primary URL is in `ecosystem_tools.json::urls.docs`. Additionally fetch:
+- `urls.release_notes` — recent changes (last 6 months)
+- `urls.changelog` — if distinct from release notes
+- Any deep-link from the docs landing page that corresponds to an integration surface (rules, hooks, MCP, agents, commands, plugins, config schema)
+
+Use `WebFetch` (for general) or `gh api` (for GitHub-hosted docs like Codex CLI, opencode).
+
+### Step 3 — Extract the feature surface
+
+For the current version of the tool, enumerate:
+- Config file paths (the tool's OWN paths, not ours)
+- Rule / instruction / prompt formats
+- Hook / lifecycle event names (if any)
+- MCP config target path (if supported)
+- Agent / custom-mode / preset concepts (if any)
+- Slash command / CLI subcommand surface
+- Supported model providers (note, do not integrate)
+- Authentication / API-key mechanisms
+
+Produce a structured markdown table: `Feature | Since version | Stable? | Our integration?`
+
+### Step 4 — Diff against our output
+
+For each feature in the table, compare against:
+- What our `generate_<tool>_*.py` produces
+- What fields are in our registry's `capability_markers`
+
+Mark each row with one of:
+- `✅ supported` — we already emit / track it
+- `⚠️ partial` — we emit a subset; specific sub-feature missing
+- `❌ missing` — we do not support at all
+- `➖ out of scope` — tool has it, but not applicable to ai-toolkit's mission
+
+### Step 5 — Classify each gap
+
+For each `⚠️` / `❌` row, assign one of the SOP drift classes:
+
+| Class | Name | Action |
+|-------|------|--------|
+| A | Cosmetic | No code change; update snapshot only |
+| B | New feature — integrate | Patch generator(s), add tests |
+| C | New feature — not adopted | Note in registry, no code |
+| D | Deprecation | Migration warning in generator + CHANGELOG |
+| E | Feature promoted to default | Simplify generator; keep fallback comment |
+| F | Newly globally available | New generator / extended generator |
+
+### Step 6 — Produce patches (class B/D/E/F only)
+
+For every class B/D/E/F gap:
+1. Edit the relevant generator in `scripts/generate_<tool>_*.py`
+2. If a new capability marker emerges, add to `ecosystem_tools.json::capability_markers`
+3. If a new config path emerges, add to `ecosystem_tools.json::config_paths`
+4. If a hook event or skill frontmatter field emerges (for Claude Code), update:
+   - `app/skills/hook-creator/SKILL.md` (hooks table)
+   - `app/skills/skill-creator/SKILL.md` (frontmatter reference)
+   - `scripts/validate.py` (allowlist)
+5. Add a bats test under `tests/test_<tool>.bats` covering the new output
+6. Update the tool's section in `kb/reference/supported-tools-registry.md`
+
+**Constraints on patches:**
+- One generator change per logical feature (no "big bang" commits)
+- Preserve existing output format for backward compatibility
+- New output opt-in via flag if it would change existing user-visible state
+- Every new capability marker must pass the doctor's probe on the live docs page
+
+### Step 7 — Report
+
+Each agent emits a single markdown report with:
+- Feature matrix table (step 3+4+5 combined)
+- List of patches applied (files changed, bats tests added)
+- List of class B/D/E/F gaps NOT patched (with reason: "out of scope", "requires user decision", "blocker")
+- Registry diff (before/after for the tool's JSON entry)
+
+---
+
+## 4. Consolidation (after all agents finish)
+
+Run in order:
+
+1. Merge registry entries — single edit to `ecosystem_tools.json` combining all 12 per-tool updates
+2. Regenerate human registry doc: manually update `kb/reference/supported-tools-registry.md` from JSON
+3. `python3 scripts/ecosystem_doctor.py --update` — baseline new capability markers
+4. `python3 scripts/validate.py --strict` — must pass
+5. `npm test` — must pass (includes the newly added bats tests per tool)
+6. `python3 scripts/ecosystem_doctor.py --check` — exit 0
+7. Regenerate downstream artifacts:
+   ```bash
+   npm run generate:all
+   ```
+8. Collect all per-agent reports into `kb/learnings/ecosystem-sweep-2026-04-23.md`
+
+---
+
+## 5. Success Criteria
+
+- [ ] All 12 tools covered (no "skipped for time" items)
+- [ ] Every class B/D/E/F gap has either a patch OR a documented reason for deferral
+- [ ] Registry `capability_markers` list grew for at least 6 of 12 tools (signals real gap coverage)
+- [ ] `validate.py --strict`: 0 errors, 0 warnings
+- [ ] `npm test`: all green (including new per-tool bats tests)
+- [ ] `ecosystem_doctor.py --check`: exit 0 after snapshot refresh
+- [ ] Single consolidated commit per agent-bucket, plus one final consolidation commit
+
+---
+
+## 6. Known Traps (from prior ecosystem work)
+
+- **SPA docs** (Cursor, Antigravity, some Augment pages): `urllib` gets empty HTML skeleton. Agents should note this and do a **manual browser visit** or use a JS-aware fetcher. Do not treat "0 headings" as "nothing new".
+- **GitHub docs** rate-limit aggressively on repeated reads. Space out fetches or use `gh api`.
+- **Feature gates** vary by user plan. Copilot Business vs Individual vs Enterprise have different surface. Integrate with the OSS surface; document gated features as C (not adopted).
+- **Version skew** on config schemas. A setting that existed in v1.x may be deprecated in v2.x. When docs reference "available since v1.5" and we don't know what version users run, default to generating the newer form with a comment.
+- **Markdown vs MDX**: Cursor uses `.mdc`, Claude Code uses `.md`, Cline uses `.md` in `.clinerules/`, Roo uses `.md` in `.roo/rules/`. Don't assume one format fits all.
+
+---
+
+## 7. Orchestrate Invocation
+
+In a fresh Claude Code session (to avoid context rot from this session):
+
+```
+/orchestrate deep ecosystem sweep for ai-toolkit per kb/planning/ecosystem-deep-sweep-2026-04-23.md
+
+Spawn 4 agents in parallel:
+- backend-specialist: claude-code, codex-cli, opencode
+- frontend-specialist: cursor, windsurf, google-antigravity
+- devops-implementer: github-copilot, cline, roo-code
+- ai-engineer: gemini-cli, aider, augment
+
+Each agent follows the 7-step per-tool protocol in section 3.
+After all 4 report, run consolidation (section 4) and produce the sweep summary.
+```
+
+---
+
+## 8. Deliverables (per agent)
+
+Each agent's final output to orchestrator:
+1. **Feature matrix** — one table per assigned tool (step 3+4+5)
+2. **Patch log** — list of commits staged (not committed yet — orchestrator consolidates)
+3. **Registry delta** — proposed JSON diff for `ecosystem_tools.json`
+4. **Gaps not patched** — with rationale (out-of-scope, blocker, deferred)
+5. **Test additions** — bats test file names + test count
+
+Orchestrator's final output:
+1. Consolidated commit with message `feat(ecosystem): deep sweep 2026-04-23 — N class B/F integrations`
+2. Version bump decision (minor if any class B/F, patch if only class A updates)
+3. `kb/learnings/ecosystem-sweep-2026-04-23.md` — retrospective noting which tools needed most work (informs priority for next sweep)
+
+---
+
+## 9. Safety Rails
+
+- **Do not** silently upgrade default behavior — every user-visible change lands behind a flag OR goes through a minor version bump with CHANGELOG mention
+- **Do not** rewrite generators wholesale — incremental additions only
+- **Do not** commit during the sweep — orchestrator consolidates at the end
+- **Do not** modify files outside the tool's scope (e.g., backend-specialist touching frontend-specialist's files requires a handoff)
+- **Do** preserve existing symlinks and file-path expectations — the installer depends on them
+
+---
+
+## 10. Related
+
+- [Ecosystem Sync SOP](../procedures/ecosystem-sync-sop.md) — the process this plan instantiates
+- [Supported Tools Registry](../reference/supported-tools-registry.md) — source of truth for tool list
+- `scripts/ecosystem_doctor.py` — drift detector consumed by orchestrator consolidation
+- `scripts/ecosystem_tools.json` — registry file edited by every agent
+
+---
+
+## 11. Retrospective — 2026-04-23
+
+### Execution summary
+
+- 4 parallel agents, 3 tools each — full 12/12 coverage, one consolidation pass.
+- 161 new bats tests (679 → 840); validate.py 0 errors / 0 warnings; `ecosystem_doctor --check` exit 0.
+- 14 files modified, 12 new test files, 2 registry docs updated, 1 snapshot rebaselined.
+
+### What worked
+
+- **Bucket-level file ownership** eliminated merge conflicts entirely. Agents that flagged cross-bucket edits (`ecosystem_tools.json`, registry markdown) correctly left them for the orchestrator.
+- **The 7-step protocol** caught high-impact bugs we would have shipped otherwise — Windsurf rules missing `trigger:` frontmatter (silent invisibility to Cascade), Aider's default `attribute-co-authored-by: true` violating our own git policy, Roo modes lacking `whenToUse` (invisible to Orchestrator).
+- **SPA-wall compensation patterns** (Antigravity bundle strings, Cursor/Windsurf llms.txt mirrors, GitHub release notes as fallback) were reusable across buckets.
+
+### What surprised us
+
+- **Claude Code 2.1.x grew ~14 new hook events** and 3 new handler types since our last sync. Our validate.py allowlist was the bottleneck, not any generator.
+- **Cross-editor compat reads**: Cursor, Windsurf, and opencode now natively read `.claude/skills/` and `.claude/agents/` — we get skill/agent discovery in those editors "for free" without emitting duplicates. Saved ~300 generated files.
+- **Copilot tier-gating is heavy**: half of the upstream surface (custom agents, repo MCP, org instructions) is Business/Enterprise-only and was classified as C (documented non-integration).
+- **Test #755 regression** from the Codex `PermissionRequest` addition: the test counted `guard-destructive.sh` occurrences with `== 1`. Fixed by updating the expected count to 2 with a comment explaining why base hooks legitimately register it twice now.
+
+### Open items flagged for future passes
+
+1. **Native `.codex/skills/*/SKILL.md` emission** (class B) — would write ~99 skill directories. Needs opt-in flag + minor bump.
+2. **`.opencode/skills/` duplication** — deferred indefinitely; `.claude/skills/` fallback already works.
+3. **New generators needed**: `generate_gemini_hooks.py`, `generate_augment_agents.py`, `generate_augment_commands.py`, `generate_augment_hooks.py`.
+4. **Cross-editor hooks unification**: Cursor and Windsurf both shipped `.cursor/hooks.json` and `.windsurf/hooks.json` — worth a dedicated shared-schema pass rather than per-editor copies.
+5. **Roo `.roomodes` YAML variant** — upstream-preferred; deferred until a YAML multi-line helper is added.
+6. **Copilot install wiring**: new `.github/instructions/` and `.github/prompts/` directories are emitted when `generate_copilot.py` is called with a target dir, but `install_steps/ai_tools.py` doesn't invoke that path yet. Wire behind minor bump.
+
+### Process refinements for next sweep
+
+- **Add a "class B/F deferred" register**: buckets produced these ad-hoc; a structured list in the plan would make prioritization for the next sweep trivial.
+- **Cross-bucket test impact**: adding per-tool bats tests inflates the test count and trips the README badge validator. Next time, bump the badge at the start of consolidation, not at the end.
+- **Search docs via llms.txt first** when the vendor publishes one — bypasses SPA walls with zero fallback logic.

package/kb/procedures/ecosystem-sync-sop.md

@@ -0,0 +1,255 @@
+---
+title: "SOP: Ecosystem Sync"
+category: procedures
+service: ai-toolkit
+tags: [sop, ecosystem, editors, generators, drift-detection, sync]
+version: "1.0.0"
+created: "2026-04-23"
+last_updated: "2026-04-23"
+description: "Quarterly (or event-triggered) sync procedure that detects documentation and capability drift in supported tools (Claude Code + 11 editors), analyses our generators and skills for missing features, and walks through the migration + generator-update workflow."
+---
+
+# SOP: Ecosystem Sync
+
+Keeps ai-toolkit aligned with the tools it integrates with. When an editor adds a new hook lifecycle, makes a feature globally available, changes a config path, or deprecates a flag, this SOP surfaces it before it surprises users.
+
+**When to run:**
+- **Every quarter** as a baseline health check (calendar reminder)
+- **Before every minor release** of ai-toolkit (Phase 0 of release prep)
+- **Whenever an editor ships a major version** (subscribe to their changelogs)
+- **On demand** if a user reports "feature X exists but toolkit doesn't support it"
+
+**Time:** 30 minutes for drift review + variable for any generator updates
+
+---
+
+## Quick Reference
+
+```bash
+# Full check (all 12 tools, online)
+python3 scripts/ecosystem_doctor.py --format text
+
+# Single tool
+python3 scripts/ecosystem_doctor.py --tool cursor --format text
+
+# First-ever run — baseline the snapshot
+python3 scripts/ecosystem_doctor.py --update > /dev/null
+
+# CI / gating mode
+python3 scripts/ecosystem_doctor.py --check
+
+# Offline (no network) — validates our side only
+python3 scripts/ecosystem_doctor.py --offline --format text
+```
+
+---
+
+## Inputs
+
+| File | Purpose |
+|------|---------|
+| `scripts/ecosystem_tools.json` | Authoritative registry: 12 tools with doc URLs, config paths, our generators, capability markers |
+| `benchmarks/ecosystem-doctor-snapshot.json` | Last-seen state (headings, content hash, markers, version) — updated via `--update` |
+| `scripts/ecosystem_doctor.py` | Drift detector |
+| `kb/reference/supported-tools-registry.md` | Human-readable view of the registry |
+
+---
+
+## Phase 1: Run the Doctor
+
+```bash
+python3 scripts/ecosystem_doctor.py --format text > /tmp/eco-report.txt
+cat /tmp/eco-report.txt
+```
+
+The report classifies every tool into:
+
+- **Clean** — doc page, headings, and markers match the last snapshot; no action
+- **Drift** — something changed upstream. Each drift entry has a `kind`:
+  - `headings_added` — the doc grew new sections (new features? reorg?)
+  - `headings_removed` — a section disappeared (deprecation? renaming?)
+  - `marker_flips` — an expected capability marker appeared (`+`) or vanished (`-`)
+  - `content_changed_no_heading_delta` — prose edits, reorder, minor rewrites, OR HTML churn (timestamps, ads, CSRF nonces). Reported but **not** treated as drift by `--check` — too noisy on dynamic pages.
+  - `version_changed` — the CLI version bumped (for tools that expose `--version`)
+- **Errored** — couldn't fetch docs (timeout, 404, auth wall). Doctor does not overwrite
+  the snapshot for errored tools; the last-known-good state persists.
+
+---
+
+## Phase 2: Classify Each Drift
+
+For every drifting tool, read its docs URL and classify the change into exactly one bucket:
+
+| Drift class | What it means | Action owner |
+|-------------|---------------|--------------|
+| **A. Cosmetic reword** | Prose edited, same feature set | Update snapshot (`--update`), no code change |
+| **B. New feature — we should integrate** | New hook event, new config key, new CLI flag, new rule surface | Update the relevant generator in `scripts/generate_<tool>_*.py`; extend `app/skills/*` or `app/agents/*` if the feature maps onto our skills; document in `kb/reference/supported-tools-registry.md` |
+| **C. New feature — not our concern** | Enterprise SSO, billing, proprietary UI-only features | Note in registry `capability_markers` as "not adopted"; update snapshot |
+| **D. Deprecation** | Flag or path removed / renamed | Open migration issue; coordinate with `ai-toolkit install` and generator output; add deprecation warning to CLAUDE.md rules if user-facing |
+| **E. Feature promoted to default** | Was behind a flag, now global | Remove the flag from generator output; simplify our installer |
+| **F. Global availability** | Was editor-only, now also available via CLI / hooks / settings.json | Map new config surface; may require a new generator or extending an existing one |
+
+Write one line per drift in `/tmp/eco-report.txt` with its class. Example:
+
+```
+cursor: headings_added [AGENTS.md support] -> class B (integrate: extend generate_cursor_mdc.py)
+aider:  version_changed 0.70 -> 0.72          -> class A (cosmetic, --update)
+windsurf: marker_flips +Cascade               -> class B (already supported, verify snapshot)
+```
+
+---
+
+## Phase 3: Execute Changes
+
+### For class B (new feature — integrate)
+
+1. Read the tool's docs section that introduced the feature. Note the exact config key / hook name / file path.
+2. Open the relevant generator (`scripts/generate_<tool>_*.py`) and add output for the new surface.
+3. If the feature is a **hook event**, also update:
+   - `app/hooks.json` (if Claude-Code-native)
+   - `app/skills/hook-creator/SKILL.md` — add the event to the Supported Hook Events table
+   - `scripts/inject_hook_cli.py` — if the hook target path differs
+4. If the feature is a **skill/agent schema extension**:
+   - Update `app/skills/skill-creator/SKILL.md` and `app/skills/command-creator/SKILL.md` templates
+   - Update `scripts/validate.py` field allowlists
+   - Update `kb/reference/agent-skills-spec.md` (if the change is an upstream spec change)
+5. Add a bats test under `tests/test_<tool>.bats` covering the new output.
+6. Regenerate artifacts: `npm run generate:all`.
+
+### For class D (deprecation)
+
+1. Open a migration issue in GitHub with "class: deprecation" and a link to the upstream changelog.
+2. In the generator, mark the deprecated output path as emitting a comment: `# DEPRECATED: <link>, removed in <version>`.
+3. If deprecation affects `ai-toolkit install --local --editors <tool>`, add a doctor check that warns when a user's repo still contains the deprecated file.
+
+### For class E / F (feature promotion)
+
+1. Simplify the generator to emit the new-default form; keep a fallback comment for users on older tool versions.
+2. Update `kb/reference/supported-tools-registry.md` config-paths column.
+
+### For class A / C (no code change)
+
+1. Run `python3 scripts/ecosystem_doctor.py --update --tool <id>` to refresh that tool's snapshot.
+
+---
+
+## Phase 4: Update the Registry
+
+If new capability markers, config paths, or doc URLs emerged during Phase 3, edit `scripts/ecosystem_tools.json`:
+
+```bash
+${EDITOR:-nvim} scripts/ecosystem_tools.json
+```
+
+Fields to consider updating:
+- `urls.docs` — if the vendor moved their docs
+- `urls.release_notes` — if the changelog location changed
+- `config_paths` — if new files now ship in our install output
+- `our_generators` — if a new generator was added
+- `capability_markers` — if a new feature was adopted
+- `version_probe.command` — if the CLI binary was renamed
+
+After editing, increment `last_updated` in the registry and save the snapshot:
+
+```bash
+python3 scripts/ecosystem_doctor.py --update
+```
+
+---
+
+## Phase 5: Validate
+
+```bash
+python3 scripts/validate.py --strict
+python3 scripts/audit_skills.py --ci
+python3 scripts/ecosystem_doctor.py --check              # exits 0 after --update
+npm test
+```
+
+All four must pass before committing generator / registry changes.
+
+---
+
+## Phase 6: Commit
+
+Use a structured commit per change class:
+
+```bash
+git add scripts/ecosystem_tools.json benchmarks/ecosystem-doctor-snapshot.json
+git add scripts/generate_<tool>_*.py                  # if class B/D/E/F
+git add app/skills/<skill>/SKILL.md                   # if templates touched
+git add kb/reference/supported-tools-registry.md
+git commit -m "chore(ecosystem): sync <tool> — <brief summary>"
+```
+
+Recommended commit messages by class:
+
+| Class | Template |
+|-------|----------|
+| A | `chore(ecosystem): refresh <tool> snapshot (cosmetic docs update)` |
+| B | `feat(<tool>): add support for <feature>` |
+| C | `chore(ecosystem): note <tool> <feature> as not-adopted` |
+| D | `feat(<tool>): deprecation warning for <old-path>` |
+| E | `refactor(<tool>): remove flag for <feature> (now default)` |
+| F | `feat(<tool>): add <new-surface> generator` |
+
+---
+
+## Gotchas
+
+- **First run has no baseline.** On a machine where `benchmarks/ecosystem-doctor-snapshot.json` does not exist, every tool shows as clean (no prior state to diff against). Run `--update` once to seed, then run again to see real drift.
+- **Documentation sites use client-side rendering.** Aider, opencode, and Antigravity serve most content via JavaScript. `urllib` fetches the bare HTML skeleton — the doctor only sees a few headings. Combine the automated check with a manual visit to the docs on these tools.
+- **Release notes pages change structure more often than docs.** Cursor and Windsurf refactor their changelog layouts periodically; a heading delta from a changelog page is often a presentation change, not a feature change. Classify as A when in doubt.
+- **Version probes require the CLI to be installed locally.** `gemini --version`, `aider --version`, etc. are skipped silently when the binary isn't on `$PATH`. The snapshot therefore omits version drift for tools you haven't installed — that is intentional, not a bug.
+- **GitHub release pages have anti-scraping.** `github.com/<org>/<repo>/releases` works via `urllib` but rate-limits aggressively. If the doctor errors on repeated runs, wait 10 minutes or manually review the release page.
+- **Marker list is intentionally small.** Capability markers are a "did we adopt this?" checklist, not a feature coverage map. Adding every sub-feature bloats the JSON and produces noisy flips — keep markers at the top-level-capability tier.
+- **`--check` only gates on structural drift.** Heading/marker/version changes and fetch errors exit `1`. Pure content-hash differences (`content_changed_no_heading_delta`) exit `0` — otherwise dynamic pages with timestamps or rotating ads would page you every run. If you want the strictest possible gate, grep for `Content changed` in the text report instead.
+
+---
+
+## Scheduling
+
+Recommended cadence:
+
+| Trigger | Action |
+|---------|--------|
+| Every Monday morning | `python3 scripts/ecosystem_doctor.py --format text` — scan during coffee |
+| Before a minor release | Full sync + clean snapshot before tagging |
+| After any drift report | Act within 1 week or record explicit "ignore, low priority" in the commit message |
+| New tool added to the registry | Baseline with `--update --tool <id>` |
+| Tool removed from support | Delete its entry from the registry AND from the snapshot JSON |
+
+An optional GitHub Action can run `--check` weekly and open an issue on drift. Template:
+
+```yaml
+# .github/workflows/ecosystem-doctor.yml  (proposed, not yet committed)
+on:
+  schedule:
+    - cron: '0 9 * * 1'        # Mondays 09:00 UTC
+  workflow_dispatch: {}
+jobs:
+  doctor:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - run: python3 scripts/ecosystem_doctor.py --format text | tee /tmp/doctor.txt
+      - run: python3 scripts/ecosystem_doctor.py --check
+```
+
+---
+
+## When NOT to Use
+
+- For **runtime** user support (user hit a bug with an editor) — use `/debug` or `/triage-issue`
+- For **picking** an editor to add — that is a product decision, not a sync; use `/architecture-decision`
+- For **one-off** testing of a specific tool's install flow — use the release-verification SOP
+- For **scaling up** the supported-tools list — add the new tool to the registry, then run the SOP to baseline it
+
+---
+
+## Related Documentation
+
+- [Supported Tools Registry](../reference/supported-tools-registry.md) — human-readable per-tool breakdown
+- [MCP Editor Compatibility](../reference/mcp-editor-compatibility.md) — MCP-specific adapter table
+- [Maintenance SOP](maintenance-sop.md) — general toolkit upkeep
+- [Release Preparation SOP](release-preparation-sop.md) — run the doctor before tagging

package/kb/procedures/maintenance-sop.md

@@ -3,9 +3,9 @@ title: "SOP: Claude Toolkit Maintenance"
 category: procedures
 service: ai-toolkit
 tags: [sop, maintenance, agents, skills, install]
-version: "1.4.4"
+version: "3.0.0"
 created: "2026-03-23"
-last_updated: "2026-04-13"
+last_updated: "2026-04-23"
 description: "Standard operating procedures for installing, maintaining, and evolving the ai-toolkit."
 ---
 
@@ -91,6 +91,17 @@ What `install` and `update` do (merge-friendly — user content never overwritte
 
 Re-running updates only toolkit content. Old whole-directory symlinks are auto-upgraded to per-file on next run.
 
+### Install Profiles (v3.0.0)
+
+| Profile | Claude Code core | Editor rules | Gemini hooks | Copilot dir layout | Per-editor hooks / sub-agents / commands | Git hooks |
+|---------|:---------------:|:------------:|:------------:|:------------------:|:---------------------------------------:|:---------:|
+| `minimal` | yes | pointer only | no | no | no | no |
+| `standard` (default) | yes | yes | **yes** (new in v3) | **yes** (new in v3) | no | no |
+| `strict` | yes | yes | yes | yes | no | yes |
+| `full` | yes | yes | yes | yes | **yes, all editors** | optional |
+
+`--codex-skills` is orthogonal to `--profile` and materializes the full skill catalog under `.agents/skills/` for Codex. See `kb/reference/global-install-model.md` for the full semantic breakdown.
+
 ---
 
 ## Update Toolkit