Repository navigation
schemas: publish external target protocol schemas #708
Description
Activity
🔗 Related PRs
#499 - test(stack): add Stack Witness 0001 fixture artifact shape [merged]
#513 - expand parity fixture coverage [merged]
#618 - feat: LE binary Rust codec emitter (le-binary-rust) + output-object codecs [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
Problem
#680 now has a documented protocol MVP and PR #707 shipped
wesley target verify, but target authors still lack canonical JSON Schemas for the external-process protocol envelopes.Without checked-in schemas, descriptor/request/response/artifact examples remain prose-only and downstream SDK templates cannot validate conformance fixtures mechanically.
Scope
Add machine-readable schemas for the external target protocol without adding target execution.
Acceptance Criteria
schemas/for:wesley.target-descriptor/v1wesley.target-request/v1wesley.target-response/v1wesley.target-diagnostic/v1or an embedded diagnostic definitionwesley.target-artifact-manifest/v1cargo test -p wesley-core --test generated_json_artifacts.schemas/README.mdanddocs/reference/external-target-protocol.mdto point at the schema files.wesley target run, target process execution, sandboxing, or artifact copy-out in this issue.Related