docs: freeze generated preparation reference baseline (generated, mechanical)

[777genius]

Scope

Single commit, stacked on #176 (D2b/D3 preparation): docs: freeze generated preparation reference baseline.

This diff is machine-generated and mechanical, not hand-authored. 586 files, +29473/-1872 lines: the localized CLI/API reference tree produced by running the authoring-docs adapter (go run ./cli/plugin-kit-ai/tools/authoring-docs) against the pinned source commit, across all 5 supported locales (en/ru/es/fr/zh). Per this program's rule that generated content is explained separately from the manual authoring budget, it is isolated into its own PR rather than mixed into #176.

Why a separate commit/PR

• Keeps the manual-authoring diff in docs(authoring): prepare site consumer, historical routes, and locale corrections (D2b/D3) #176 reviewable on its own terms (content correctness, locale/preservation policy) without generated noise.
• Lets docs:check-drift regenerate and diff this exact output independently: after this commit, a fresh pnpm run docs:gen + drift check reproduces byte-identical output and the tree stays clean.
• The generated tree's inputs (source pin, adapter revision) are unchanged from docs(authoring): prepare site consumer, historical routes, and locale corrections (D2b/D3) #176's head, so this commit carries zero manual/product source changes - it is purely the frozen rendering of already-reviewed content.

Evidence

• docs:check-drift passed against this exact commit (regenerate -> diff -> clean tree, no manual edits required to match).
• Adapter assembly is real (no overlay/diagnostic shortcut); generated file hashes match the browser-evidenced production build from the parent commit.

Explicitly not claimed

• Not release-ready; same public-docs auto-deploy hold as docs(authoring): prepare site consumer, historical routes, and locale corrections (D2b/D3) #176 applies (draft, do not merge to main ahead of release gates).
• Does not change any hand-authored page content beyond what docs(authoring): prepare site consumer, historical routes, and locale corrections (D2b/D3) #176 already introduced.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}