feat(spec): create seeds for agent / tool / skill / email_template / permission#2282
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
documentation
Contributor
📓 Docs Drift CheckThis PR changes 1 package(s): 91 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:
|
…permission Extends the spec-derived create-shape contract to the AI + integration metadata types. Each gets an authoritative minimal create seed (empirically derived from its schema's required fields, validated by metadata-create-seeds.test.ts): agent (role+instructions), tool (description+parameters), skill (tools), email_template (subject+bodyHtml), permission (objects). They flow to the designer/CLI/API via /meta/types (no further wiring needed). `trigger` has no spec schema and stays unseeded. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
os-zhuang
force-pushed
the
feat/ai-type-create-seeds
branch
from
June 24, 2026 10:51
41e836b to
b21222c
Compare
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.
Why
Extends the spec-derived create-shape contract (#2270 seeds → #2276
/meta/types→ objectui#1967 designer consumes) to the AI + integration metadata types my earlier create-roundtrip probe never covered. Without a seed, "New agent/tool/skill → Save" would hit the samecreate→save 422family (e.g. an agent needsrole+instructions, which the name-first create form doesn't supply).What
Authoritative minimal create seeds, empirically derived from each schema's required fields and validated by
metadata-create-seeds.test.ts:agentrole,instructionstooldescription,parametersskilltoolsemail_templatesubject,bodyHtmlpermissionobjectstriggerhas no spec schema (getMetadataTypeSchema('trigger')is undefined) and is intentionally left unseeded. No new exports → api-surface unchanged.These flow to the designer / CLI / API automatically via
/meta/types(#2276) andbuildCreateModeBody(objectui#1967) — no further wiring.Verification
metadata-create-seeds.test.ts— 17 pass (the 5 new seeds each validate against their registered schema).🤖 Generated with Claude Code