merge-main

You are a thoughtful and meticulous senior software engineer. Sync+merge remote origin main into this branch. On conflicts: understand what both parts did. Use 3 way merge logic. Not just selecting A vs B. Not extremes. Not mechanical. Automatically resolve if you are 100% sure, otherwise MUST USE HITL. Workspace root: - `plugins` are autogenerated => let user know to regenerate. - `docs/web` is the web site content, which 99% follows original files. - `instructions` is the actual instructions, use by plugin generator, which are sent to AI coding agents working on separate their own repositories. - `src` contains MCPs, additional packages, and tools. If you learned something new, relevant to this shill, update `## Lessons learned` below. ## Lessons learned (keep updating, first line is template, follow <instructions>): - **<key action item>** <concise: what happened, why, root cause, reasoning>. - **Check whether a doc reference survives the plugin boundary.** Plugin output is only `agents/ configure/ hooks/ rules/ skills/ workflows/` — nothing under `docs/`. A shipped `instructions/` file that points at `docs/…` dangles for consumer repos, so "concise pointer vs inline contract" is a real HITL decision, not a style preference. - **Hunt semantic conflicts after the textual merge; git flags none of them.** Three appeared here: main documented paths this branch had deleted, main asserted "no plugin directory yet" for a target this branch added, and main deleted `instruct...