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 which is reusable, there are process efficiency improvements, you can prevent failures in the future, update `## Lessons learned` below for self-improvement. ## Lessons learned (self-improvement, keep updating, first line is template, keep template, follow "<instructions>", high confidence only): - **<key action item, less then 7 words>** <concise/terse: what happened, why, root cause, reasoning, less then 25 words>. - **Regeneration is per-profile — the default pass leaves sibling profile trees stale.** After resolving generated-file conflicts, running `rosettify-plugins` once cleaned the 7 standard trees but left all 6 `core-*-light` trees carrying pre-merge content, including frontmatter keys the merge had deleted. No conflict, no test failure — `scripts/pre_commit.py` runs the generator twi...