wheeler-service-creator

Scaffold a NEW Wheeler service adapter that integrates an external tool into Wheeler end to end. Reach for this whenever the user wants to "create a wheeler service", "add a new tool adapter", "scaffold an integration", "wrap a service for wheeler", "onboard <some CLI/API/agent> into the graph", "ingest a new tool's output", or otherwise connect an external research tool (a search API, a generator, an analyzer, an agent card) to Wheeler so its results land in the knowledge graph with provenance, even if they do not say the word "adapter". Given the tool (interview the scientist, or read its --help / agent card), it produces four pieces: (a) the declarative registry contract the router reads (.wheeler/services.yaml or the bundled default), (b) a marshal-out ingest module wired to the shared _marshal.py helpers with BOTH provenance sides (Execution -[USED]-> inputs, produced nodes -[WAS_GENERATED_BY]-> Execution), (c) the marshal-in act /wh:<provider>-<tool> that reads graph context, passes --used source ids, and shells out, and (d) a parse-unit + live-Neo4j e2e test stub. A bundled scaffolder emits the skeleton files; the human then captures one real output, fills the parser against it, and runs the adversarial review to land it. Do NOT trigger for RUNNING an existing adapter (that is the /wh:asta-* acts), for graph lookups or queries, or for generic coding unrelated to wiring up a new external service.