COOL IDEA™: publish a reusable Wesley target for generated domain SDKs

[flyingrobots]

Opportunity

v19.0.1 can document and prove generated domain SDKs honestly, but each application still owns a renderer that maps Wesley operation metadata to git-warp Intents and bounded Observers. The checked-in users renderer is executable reference evidence, not a universal consumer tool.

A reusable, versioned git-warp Wesley target could remove most copy-and-adapt work while preserving the domain-free compiler boundary.

Product boundary

• Wesley continues to own GraphQL structure, deterministic IR, request types, and directive metadata.
• The git-warp target owns an explicit versioned directive vocabulary and the mapping from supported directives to runtime-backed Intent and Observer constructors.
• Unsupported intent kinds, readings, decoders, cardinalities, or unbounded plans fail generation with structured diagnostics.
• The target never guesses application semantics that are absent from the schema or target configuration.
• Applications may still provide extension mappings for domain-specific validation and decoders.

Possible workflow

wesley target run git-warp \
  --schema src/warp/users.graphql \
  --out src/generated/users.generated.ts

The concrete command should follow Wesley's supported external-target protocol rather than hard-coding a private integration.

Acceptance sketch

• Publish a versioned target descriptor and input/output contract.
• Generate deterministic request types, runtime validators, Intents, and bounded Observers from the supported directive subset.
• Import only supported root and /advanced git-warp surfaces.
• Emit stable diagnostics for every unsupported or ambiguous mapping.
• Prove byte-stable regeneration, consumer typechecking, and packed-package execution against a disposable real-Git Runtime.
• Update the migration guide from the application-owned renderer recipe only after the reusable target is published and its version is pin-able.

Dependency posture

This is follow-up developer-experience work after #807 and the v19.0.1 migration-guidance milestone. It is not a v19.0.1 release blocker.

[coderabbitai]

🔗 Related PRs

#702 - Fix: harden Wesley deterministic codec boundary [merged]
#726 - Move graph exports behind v19 public API boundary [merged]
#797 - Generate validated v19 Intent and Observer SDKs [merged]
#799 - Enforce one generated v19 vocabulary contract [merged]
#813 - Define streaming indexed recursive WARP architecture [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command 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!