Update Docs

Slash trigger: /update-docs

Capture new knowledge from the current session into onboarding state files. Do not re-explore the codebase unless a fact needs verification.

Hard rules

• MUST read relevant state files before writing.
• MUST only add or update information that is new or changed — never rewrite entire files unnecessarily.
• NEVER duplicate the same fact across multiple state files.
• NEVER trigger a full codebase scan.
• If docs/onboarding/ is missing, tell the user to run /start first.

State file roles (write to the correct file only)