Documentation
¶
Overview ¶
Command unboundops reports GraphQL operations that hadron-server exposes and the CLI does not wrap (hadron-cli#397).
The gap it exists to catch: a server operation ships, the schema snapshot is refreshed, and nothing notices that no CLI command reaches it. That is not hypothetical — installAgentIntoApp had been in the schema since spec 023 when #389 was filed as "no surface attaches an existing Agent to an existing App", and the worklog contract sat duplicated in the client for months after recordTeamWork shipped (#396).
Why a committed BASELINE rather than a plain report: the CLI wraps roughly half of the server's surface (148 of 284 root fields when this landed), so an unfiltered list is noise nobody reads, and an allowlist of 148 hand-written reasons is worse. The baseline turns the inventory into a DIFF — a schema refresh that adds an unbound operation shows up as an added line in review, and accepting it is one commit. Deliberate omissions carry their reason in the file itself.
go run ./scripts/unboundops # print the baseline to stdout go run ./scripts/unboundops -check # diff against the committed baseline
Source Files