Repository navigation
Conversation
…untime Describe the attended project update that refreshes the kits/ tree and then each installed runtime of each project kit: --target filtering at project scope, skipped_targets, runtime-only projects, preview rows, the home-directory skip, background auto-update notice, project --force and legacy Codex archival, and the new exit 1/2 cases. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Apply the verified upstream docs bundle for v3.0.0-beta.9 (source 638464def28ec495f89d56e133a4dd70de4a6a9c) with sync-release.mjs and record the verified Desktop Layer A evidence for its 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.9 release assets for all eight runtimes, and bind the runtime contract at the release source commit. Identity sets are unchanged (engineer 103, marketing 83). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…guidance Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: sync beta to v3.0.0-beta.9 and document project runtime refresh
This branch was successfully deployed
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
1 participant
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
Publish the reviewed Beta documentation on
devto production. Beta becomesv3.0.0-beta.9; Stable staysv2.19.0(no AgentKit stable release after v2.19.0, no Stable diff).Included: #253 — Beta sync to
v3.0.0-beta.9(verified docs-bundle, 48 Kit assets across 8 runtimes, Desktop evidence) plus projectak updaterefreshing every installed runtime (#249, source agentkit#2188 contained in the tag).Production Kit gate
On the actual
main+devmerge tree (6c109054, clean merge):node scripts/check-kit-catalog.mjs: stable and beta engineer/marketing allartifacts=8; beta 103/83 identities.node scripts/check-kit-docs-ci.mjs 82c87c0e: routehistory(no Stable diff), historical reconciliation record valid.#253 passed CI
buildon Linux before merge. This PR must pass its own CI.Not included
#243 (
ak kit init --fresh, draft #251) and #234 (Desktop Devices, draft #252) remain held: their source PRs (agentkit#2171, agentkit#2146, ak-web#551) are unmerged and not in any release.🤖 Generated with Claude Code