Extension model
Protocol operations and events
Section titled “Protocol operations and events”- Add domain request/result or event schemas in
packages/contracts. - Register method/event metadata in the centralized catalog.
- Add server handler, authorization, routing, and persistence behavior.
- Add UI client/reducer behavior.
- Negotiate capability where needed.
- Test schema rejection, role/routing, idempotency/retry, replay/recovery, and security boundaries.
Protocol v1 does not accept aliases, raw/private frames, or breaking changes disguised as optional fields. Additive evolution must preserve strict parsing and negotiated behavior.
Agent tools
Section titled “Agent tools”Define tool name/schema/risk/execution mode in the owning manifest, implement a bounded executor or host adapter, integrate availability/policy, add presentation when generic rendering is insufficient, and test destructive/concurrent/error boundaries. Shared tool names belong in contracts.
Content extensions
Section titled “Content extensions”Skills and AGENTS/SYSTEM resources extend instructions without code changes. Prompt suggestions add contextual reusable prompts and optional explicitly trusted predicates. Both require clear precedence and trust documentation.
Package boundaries
Section titled “Package boundaries”Put transport-neutral contracts below hosts. Keep UI kit contract-free and Workbench presentation free of feature/application effects. Prefer one owning source over adapter-level compatibility shims.