Repository navigation
Conversation
- spec.yaml -> simspace.yaml (+ simspace.dockerfile): v3 descriptor with agent-skill@1 per skill, agent-context (@1 and @2), network-policy@1 and port@1 capabilities. The skills move from files/home/ to skills/ and are copied into an overlay layer; v3 has no implicit file copy. - Publish with `docker buildx build --push` using the docker/sandbox-kit:3 frontend instead of `sbx kit push`; the workflow sets up buildx rather than installing sbx. The unused SIGN option is removed. - Update AGENTS.md and the kit README. Verified: descriptor + recipe build, and `kit-tck validate` passes all checks on the exported OCI layout. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This branch has not been 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
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.
What
Moves
kit/from kit spec v2 to v3.spec.yamlbecomessimspace.yamlplussimspace.dockerfile. The descriptor declaresagent-skill@1per skill,agent-context(@1 and @2 via a YAML anchor, as the spec's own examples do during the runtime rollout),network-policy@1andport@1.files/home/.claude/skills/toskills/and are copied into an overlay layer. v3 has no implicit file copy, so each skill needs anagent-skill@1entry. The agent's own kit decides where skills land, so this isn't Claude-specific.docker buildx build --pushwith thedocker/sandbox-kit:3frontend instead ofsbx kit push. The workflow sets up buildx instead of installingsbx. The existence check, immutable-tag rule and by-digestlatestretag are unchanged.SIGNoption is removed. v3 signing is a separate cosign step.AGENTS.mdandkit/README.mdare updated.Verification
kit-tck validatepasses all 19 checks on the exported OCI layout, and layer ownership is all0/0.DRY_RUN=1 ./scripts/publish-kit.sh v3.0.0runs end to end locally.sbxin my environment) or the workflow in CI. The PR run is a dry run, so it will exercise the build.Before merging
Merging publishes v3 to
latest. v3 kits can't compose with v1/v2 kits, so any repo pairingsimspace-authoring-kit:latestwith a v2 agent kit (simspace-starter's.sbxenv.yaml, for one) will stop resolving. Consider cutting akit/v3.0.0tag first, or moving the starter in step.Also unconfirmed: the minimum
sbxversion. The Docker Learn guide says Kits v3 need at least v0.45, but I couldn't confirm that from the spec repo.🤖 Generated with Claude Code