docs: sync beta to v3.0.0-beta.10 and document user-level route refusals

[mrgoonie]

Summary

• Syncs the Beta channel to AgentKit v3.0.0-beta.10 (source commit 7b4442c82fc37ebfb5094e4e49f860379a31e1e4, docs bundle generated 2026-10-08T17:11:59Z) with scripts/sync-release.mjs. The sync uses the release's own docs-bundle.tar.gz, verified against its .sha256 sidecar and the release-page digest. It updates the raw and derived ak kit init, ak kit install, ak kit refresh, ak kit uninstall, and ak uninstall reference, the Beta release notes, and channels.json.beta. It also adds Desktop Layer A evidence (release-evidence/desktop/v3.0.0-beta.10.json); no Desktop pages changed.
• Rebinds the Beta Kit catalog guard from v3.0.0-beta.9 to v3.0.0-beta.10. The rebind covers engineer and marketing evidence for all 8 runtimes in the release contract (claude-code, cloud-harness, codex, cursor, dsh, grok, omp, pi): manifests, sidecars, claude-code Skill members, and the runtime contract at the source commit. All 16 Kit archives are byte-identical to v3.0.0-beta.9, so the identity snapshots and their digests are unchanged (engineer 103, marketing 83). Stable is untouched.
• Updates human-owned Beta prose, EN and VI, for the beta.9→beta.10 behavior changes:
  • Project route onto the user-level install (#2190, #2192): a project-scope ak kit init, ak kit install, ak kit refresh, or ak kit uninstall (including --dry-run) now refuses, for every runtime, a route that resolves to the user-level install, and exits 6. Examples include a project directory that is the home directory, a project .agentkit that is the AgentKit home, and a project .claude, .codex, or Pi extension that is the user root. The refusal points to --global. Before this release only Codex was checked, and it exited 1. Updated pages: reference/cli/kit/{init,install,refresh,uninstall} (route paragraph and exit tables), guides/installing-kits (scope paragraph and the Codex note, now with exit 6), and troubleshooting/kit-installation (exit 6 row). Sources: kitcmd/project_route_global_home.go, the init.go/refresh.go/uninstall.go call sites, and project_route_global_home_test.go/project_uninstall_global_home_test.go, which assert exit 6 and the --global guidance. install shares the init RunE, so it gets the same refusal.
  • ak uninstall at the home directory (#2194): without --force, a home-directory project lists the files it would remove and exits 6, including with --dry-run. The orphan walk is skipped there. Every applied uninstall also snapshots the exact deleted files plus ownership.json. It reports files_snapshot_id and files_restore_command (ak backups restore <id> --allow-root <project>), deletes nothing if that snapshot fails, and appends the restore command to a partial-failure error. Updated page: reference/cli/uninstall. Sources: uninstallcmd/home_guard.go, uninstall.go, uninstall_scripted.go, and home_guard_test.go.

Evidence (verified hashes)

All 48 expected Kit assets (2 Kits × 8 runtimes × manifest/archive/sidecar) are present, with no extras. Each archive SHA-256 matches all four sources: the downloaded bytes, manifest.artifact.sha256, the sidecar (<sha> kit.tar.gz), and the release-page digest. Manifest and sidecar digests were also checked against the release page. For each manifest, channel, version, runtime, kitId, sourceCommit, createdAt (= syncedAt), requiredCliVersion, and githubAssets were checked.

Runtime	engineer archive SHA-256	marketing archive SHA-256
claude-code	efdece969beb5f78155294d3c6a2641ecb6aa0279799ec248ffc38e24dc0efe3	e6cd68204ee19cf1ad02891720c871e4d3c104ea2611b0341ff6c5057f4c9836
cloud-harness	0f9031183b8794c17e52ad4ab4444451bd90a94d05ba6658ac15daee7445ffc8	a6a00c4d0c34a516f09d62cc7cd27ab8210246c983d712006e7eccec85e7c70a
codex	9780061ad1d76ae7ce80a1c2984e7181b4c105837f517d0e90b2ca20153f0602	ca9aa9b7fe074656e6a6a0130bc58abcf3cb38f60fe869f2085fabcad49c9548
cursor	ab5de2109a0f1b771b7260b8c2e600c0ad772551754c0b4e6c5562025c8e31f7	49128bfd0281a9769af8f3e305ccf1a82f18c9bcafee57a331450fc4c1753558
dsh	6e35dda0fda793f4c9509e3b517e2a9cc381e31889bd315f6d5df99b9cebe639	cf8ff430f59c4440502af2799ed770002d42093499130a2f19dc7b035a830bdd
grok	4f0e4878c41b89b421e18a9b8472bfef028daa0a79db7d83ad818d43bfa39f2d	230071da378c995a06af7866ec756385c926ab6620958ab3f0e3ef36d5d394fe
omp	3b61c87703ae80077c21657acfe5479b6c05db93ef97f841f78ead8d87795720	9d5e4c9cc522ae8f82dc8fecc69fef1b82d9ec759ff2af37852cd0874d30b432
pi	385d7a226bca4821d739fa2b17edbda84e56919d539f7e96d37cc5457e7be8e4	59fd6003e2011a5df62e234e60f90880db9b90a044163ae8bc6fdc82d568a2dc

• Every archive hash above equals its v3.0.0-beta.9 counterpart. Expanding all 16 archive pairs found 0 added, 0 removed, and 0 changed files.
• Snapshot digests are unchanged: engineer 19ce73b137a123add4b5e5da64041c4c3878948959fc4100fc6e236518fee966, marketing 5579e1fd34bb4954d611b43e13696536d284bdfd370e8f68d6de636aee32709f.
• The runtime contract 7b4442c82…json is byte-identical to the beta.9 contract.
• Docs bundle: 2d2feb63c73e5f381ffade4965444eb1d4f5920f23f800b8dd36326d4f3ffa57. The sidecar and the release digest match.
• Desktop: the 4 ak-gui_3.0.0-beta.10_* assets match their .sha256 sidecars and the release digests.
• Public Skill disposition: there are no rows, because no Skill identity, SKILL.md body, or support file changed in any runtime.

Product commits in v3.0.0-beta.9...v3.0.0-beta.10

PR	Change	Disposition
#2190	Refuse project routes that land on the global install (kit init/install/refresh)	update: see Summary
#2192	Refuse project uninstall that lands on the global install	update: see Summary
#2194	Require --force for ak uninstall at the home directory, and snapshot deleted files	update: see Summary
#2196	Drop userinfo from --registry-url / AGENTKIT_REGISTRY_URL and warn once with the credential masked; the doctor remote_registry_config check warns instead of passing	no prose impact: no Beta page documents credentials in registry URLs or that doctor check, and the --registry-url option rows stay accurate. The release notes carry the change.
#2198	CI (setup-go cache)	No docs surface

Validation

• pnpm check:catalog: OK (beta/engineer total=103, beta/marketing total=83, artifacts=8)
• pnpm lint, pnpm typecheck, pnpm check:reference, pnpm check:prose: OK
• node scripts/check-kit-docs-ci.mjs origin/dev: OK (history route, no Stable diff)
• node scripts/generate-reference.mjs: no further diff
• pnpm build, pnpm check:links, pnpm check:seo: OK
• check:quality:shape: route parity OK, and route counts are unchanged, so no baseline update was needed. check:quality:metrics, check:assets, and pnpm test have known Windows path failures that also occur on an untouched dev, so this PR relies on Linux CI for them.

Docs impact

Yes:

• The Beta CLI reference and release notes are synced to v3.0.0-beta.10.
• The Beta Kit catalog guard is rebound.
• The user-level route refusal and home-directory uninstall behavior are documented in EN and VI.

Evidence layer: shipped release assets for v3.0.0-beta.10 (verified hashes) and the product source at the tag. Stable content is not edited.

Website impact

None for agentkit.best.

Follow-ups / mismatch disposition

• The human-owned CLI prose overlay drift since v2.20.0-beta.1 (carried over from docs: sync beta to v3.0.0-beta.8 and add ak:filmmaking guide #244) still needs a separate owner-approved release audit.
• getting-started/installation still says a completed uninstall preview exits 3. That remains true except for a home-directory ak uninstall project, which is covered on the ak uninstall reference page and was left unchanged here.

🤖 Generated with Claude Code