Repository navigation
docs: sync beta v3.0.0-beta.11 - #257
Merged
Merged
Conversation
Apply the verified v3.0.0-beta.11 docs bundle with sync-release: refresh the raw and derived ak kit init and ak kit install reference, the Beta release notes, and channels.json.beta, and record Desktop Layer A evidence for the four ak-gui assets. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replace the Beta engineer and marketing manifest, sidecar, and skill-member evidence with the verified v3.0.0-beta.11 release assets for all eight runtimes, and bind the runtime contract at the release source commit. Only ak-ak/SKILL.md changed inside the Kit archives, so the identity sets are unchanged (engineer 103, marketing 83); the snapshots are re-keyed to the new claude-code archive digests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ages Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
v3.0.0-beta.11(source commitc47bad84279eec9ac201d5e7984826b9f0dbbcbb, docs bundle generated 2026-10-09T01:35:32Z) withscripts/sync-release.mjs. The sync uses the release's owndocs-bundle.tar.gz, verified against its.sha256sidecar and the release-page digest. It updates the raw and derivedak kit initandak kit installreference (--fresh,--accept-risks, exit3), the Beta release notes, andchannels.json.beta. It also adds Desktop Layer A evidence (release-evidence/desktop/v3.0.0-beta.11.json); no Desktop pages changed.v3.0.0-beta.10tov3.0.0-beta.11for engineer and marketing across 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 (byte-identical to the beta.10 contract). Unlike beta.10, every Kit archive changed. The only changed file in all 16 archive pairs isak-ak/SKILL.md(plus its runtime-native copy under.cursor/.dsh/.grok/.omp/.pi). The Skill member sets and identities are unchanged (engineer 103, marketing 83), so the identity snapshots were only re-keyed to the new claude-code archive digests: engineerc5ee11044ac9790b402d0352c1fdd432cfb19ea24ca0fb1331c1ae8e3891eb31, marketing4a7260980871d806204c703c8cad338e9a5b9300e441c7f6dfa3645c40bf4cf3. Stable is untouched.ak:akSkill--freshrisk-token guidance (#2171): the Skill body now tells the agent to show each listed risk and its files, rerun with--accept-risks <token>only after the user accepts that exact list, and never reuse or save a token. Added to step 5 of the safe operating protocol onkits/{engineer,marketing}/skills/ak(EN + VI), with a link to theak kit init --freshsection. Source:kits/core/skills/ak-ak/SKILL.mdat the tag and the shipped archives.ak kit init --fresh/ak kit install --fresh(#2171): already documented by docs(kits): document ak kit init --fresh selected-target reset #251. Re-verified againstv3.0.0-beta.11(kitcmd/fresh_plan.go,fresh_reset.go,init.go,render/json.go,recovery_output.go): risk kinds,reasonvalues, thekit.init_fresh_plananddata.freshJSON fields, theReset this target? [y/N]prompt, the 25-entry text cap, thepi/grok/omp/dsh--forcefallback, plugin-mode reset, exit2/1/3/6refusals, and the recovery output lines (includingUNVERIFIED, may be incomplete) all match. docs(kits): document ak kit init --fresh selected-target reset #251 was written against the same commit, so no drift was found and no reference page was changed.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,requiredCliVersion,artifact.size, andgithubAssetswere checked. The release-kits workflow run 37870535991 completed successfully before verification.55f1d1cf236cd6001979cb53b6125001f02b2d535f3812c083421adf6d27ce3a4e089f6ae58fa30ad555af671b9dcb0e349b8bfd62def90d7ccfa7004a0370d92c92803d8bf751627dfbc1adc53495a800a774e6f57e4fcd754463046d941331e06ce8b9416b9b493f47b7574345e87950c70d301045f9719db2e695ae9bdfcc0d7aea6652685a7eefa26c82e03d74447608d6bc9cd3b7105a61612d640ee8171be07759963ad8c498bb72f8c7ddffa847c82afb9ca938301e2524e4349252e256fb97afcd4f990928fbd2b9102293a41b8822a9772a506b7f5a2687595069aa34308957ddf4633fccbf7b129f921f9fa8f337405926e695d15dd81e76840988b2d04b06011e0cfa141252d27b4938f5bb1c43076508a5df67a962c352a2301ba4799f83eb0d310a45f1e106355ba2d18597d6bee437b4cef5fa8fdcfa54243fb71def7dabecfc77c95fc810c228f80044318bbe373ae712bd804bfa456bc25ac1566ea6da979d73e5cc4acdd0675fc117fe9366130c472497de15746c6d99803346fdc7916869a1d11433d86097c764cce19f15fb7e7ccc2674669f24df7a2e4f60fbcc464ebfeb3c58a9b98e6397418a95e9d005d6cb3aaa42c7872941af2bbe446089219930cf44da3165b25fb6806985e26330a1a74deabd062e1770890d6cdd270b3401823c215f71b07a1bc2628c476c619a892545e02a6f6f00560dd1125d5263cd74aa0eb18fb9b73210fb3b6a9dabe7f993833d7b3a8e6f488b7c49. The sidecar and the release digest match.ak-gui_3.0.0-beta.11_*assets match their.sha256sidecars and the release digests.v3.0.0-beta.10(all 16 pairs expanded): 0 added, 0 removed; onlyak-ak/SKILL.mdchanged.Public Skill disposition
ak:ak(engineer, marketing)content/docs/beta/kits/{engineer,marketing}/skills/ak.{en,vi}.mdxNo other public Skill identity,
SKILL.mdbody, or support file changed.Product commits in
v3.0.0-beta.10...v3.0.0-beta.11ak kit init --freshsnapshot-backed selected-target reset,--accept-risks, exit3,unverifiedrecovery snapshot field,ak:akSkill guidanceak:akSkill pages above;--freshreference prose already shipped in #251 and re-verifiedValidation
pnpm check:catalog: OK (beta/engineer total=103, beta/marketing total=83, artifacts=8)pnpm lint,pnpm typecheck,pnpm check:reference,pnpm check:prose: OKnode scripts/check-kit-docs-ci.mjs origin/dev: OK (history route, no Stable diff)node scripts/generate-reference.mjs: no further diffpnpm build,pnpm check:links,pnpm check:seo: OK; the new EN and VI anchors resolve in the built pagescheck:quality:shape: route parity OK; route counts unchanged.check:quality:metrics,check:assets, andpnpm testhave known Windows path failures that also occur on an untoucheddev, so this PR relies on Linux CI for them.Docs impact
Yes:
v3.0.0-beta.11.ak:akSkill pages document the--freshrisk-token handling in EN and VI.Evidence layer: shipped release assets for
v3.0.0-beta.11(verified hashes) and the product source at the tag. Stable content is not edited.Website impact
None for
agentkit.best.Follow-ups / mismatch disposition
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.dev) documents the Desktop Devices page andak license devices. That command is not inv3.0.0-beta.11: the implementing product commit is only on the unmergedfeat/desktop-license-devicesbranch. Beta now describes behavior that no release ships. This PR leaves it alone; the owner should decide whether to holddev→mainor revert until the feature ships.Refs #243
🤖 Generated with Claude Code