docs: beta v2.13.0-beta.2 release update

[thieung]

Summary

Sync ak-docs beta channel to v2.13.0-beta.2 (docs-bundle
sha256:af6d56dd8e0ea8c09722c3368032e71f8a3433fa57449a275b52115adcc47a0a,
release commit e1f84b0b0203cb2578aad2e0c9b9b708233ec2c2).

Upstream delta from v2.12.1-beta.6 picks up 13 CLI/bundle claims, including:

• New CLI group — ak orchestrate (Darwin-only) with start, resume, status, stop subcommands: durable local worker supervising external CLI job graphs with process-group ownership, crash-safe reconnect, and no persisted-PID guessing.
• CLI update — ak config prefs set / unset gain the worktree.root leaf (project = relative path only; user = relative or absolute). Root ak config prefs index and the CLI root outcome table both updated to surface it.
• Deterministic sync — sync-release.mjs refreshed 171 generated reference files (reference-derived/ + reference-raw/), rewrote release-notes.mdx, and Layer A auto-rewrote 10 desktop-app pages across 4 platforms with fresh ak-gui_* asset metadata from the release page.

Audit trail

• V0 audit: plans/releases/2.13.0-beta.2/ — request REQ-C0394F50C15656F2, 13 surfaced claims, 174 ledger entries.
• from-ref = v2.12.1-beta.6 (last approved audit/* tag; channels.beta.tag at push-time was v2.12.1-beta.8 but its audit tag was never pushed, so the run resumed from the last verified snapshot rather than promotedFrom of stable).
• Owner approval statement received in-session for the proposed CLI prose scope; V1 authoring stayed within the approved nested paths.

Prose scope

Beta CLI only (EN + VI parity, technical tokens preserved):

• content/docs/beta/reference/cli/index.{en,vi}.mdx — outcome table gains an orchestrate row.
• content/docs/beta/reference/cli/config/prefs/index.{en,vi}.mdx — goals table gains worktree.root.
• content/docs/beta/reference/cli/config/prefs/set.{en,vi}.mdx — third key shape, scope-specific path rules, examples.
• content/docs/beta/reference/cli/config/prefs/unset.{en,vi}.mdx — third unsettable key, resolved-fallback semantics.
• content/docs/beta/reference/cli/orchestrate/{index,start,resume,status,stop}.{en,vi}.mdx + meta.{json,vi.json} — new command group.
• content/docs/beta/reference/cli/meta.{json,vi.json} — orchestrate inserted between mcp and plan.

Stable remains bound to channels.stable.tag = v2.12.0. The beta-only orchestrate routes and worktree.root prose are intentionally absent from content/docs/stable/** until the next stable promotion.

Quality contract updates

• scripts/cli-reference-routes.test.mjs — expected authored routes are per-channel (stable=165, beta=170); EN/VI remain equal within each channel, and stable must be a subset of beta.
• scripts/release-quality-shape.mjs — per-channel source/route baselines: stable 393/392, beta 398/397; cross-channel checks enforce stable ⊆ beta.
• scripts/release-quality-metrics.mjs — per-channel searchable-page baselines: stable 391, beta 396; cross-channel search checks enforce stable ⊆ beta while EN/VI parity remains strict.
• scripts/release-quality.test.mjs — regression coverage accepts beta-only searchable routes and rejects stable routes missing from beta.
• Channel navigation now preserves same-page switching when a counterpart exists and falls back to the target channel root for beta-only or stable-only routes, preventing broken cross-channel links.

Deferred to follow-up

The upstream delta from beta.6 → 2.13.0-beta.2 spans ~13 months and includes a full CK→AK rebrand, so several out-of-scope surfaces were intentionally left for follow-up PRs to keep review manageable:

• Kit prose drift — audit skill's body-diff pass identified drift in 15 engineer + 9 marketing SKILL.md bodies. Highest-signal candidates that need docs refresh: worktree (adds worktree.root priority slots — engineer + marketing docs currently miss the two config scopes), orchestrate engineer skill page (adds ak orchestrate process-lifecycle delegation and Darwin fallback caveat), plan engineer (adds --debate), and the --/references/handoff-gate.md cross-refs across design/frontend-design/show-off/slides. Author these under a separate docs: refresh engineer/marketing kit prose to 2.13.0-beta.2 PR.
• Desktop Layer B — release notes surface Trust Center MVP (#463), remote kit lifecycle controls (#610), beta control-center UX (#636), native Wails MCP bridge, MCP-page wiring, and CK UI phases 1–4. Feature-and-behavior authoring under owner gate; not batched here.
• Desktop Layer C — screenshots refresh (needs a running Desktop build).
• Maintainer contract cleanup — AGENTS.md:63, .agents/skills/ak-docs-release-audit/SKILL.md:47, and docs/workflows/release-and-deploy.md:116 still describe strict beta/stable shape mirroring. Align them with the enforced stable ⊆ beta contract and the beta-only guidance in kit-prose-drift.md before the next beta-only route addition.

Validation

• pnpm test — 173/173 pass locally.
• pnpm typecheck — clean.
• pnpm lint — clean.
• pnpm check:catalog — clean (engineer 102 source, marketing 81 source; identity registry unchanged).
• pnpm check:reference — 678 reference pages clean.

Full-build checks were blocked locally by disk-space exhaustion on the host. GitHub CI completed pnpm build, pnpm check:quality, pnpm check:assets, and pnpm check:links successfully against a fresh disk.

Test plan

• CI: pnpm build completes with beta 397 and stable 392 published routes per locale.
• CI: pnpm check:quality:shape accepts stable 393/392, beta 398/397, and stable ⊆ beta.
• CI: pnpm check:quality:metrics, pnpm check:assets, and pnpm check:links pass against fresh out/.
• Manual staging QA: beta reference/cli/orchestrate and all four subcommands load in EN + VI; beta config documents worktree.root; stable orchestrate returns 404 and stable config omits the key; beta-only channel links fall back to /en/stable or /vi/stable.
• Post-merge: PR merged to dev at 65378fc61abfc67b83a98c925078b6a3a3b78519; CI and staging deploy succeeded; docs/v2.13.0-beta.2 and audit/v2.13.0-beta.2 both point to the merged SHA.