Skip to main content

Module command_surfaces

Module command_surfaces 

Source
Expand description

One row per analysis subcommand: its JSON kinds and the surfaces that must know about it. Drift tests across the workspace read this table. One row per analysis subcommand: the JSON kinds it writes and the surfaces that must know about it.

A new analysis command must reach the root FallowOutput schema, fallow report --from, the MCP server, the GitHub Action, the GitLab CI template and the drift harness. Each of those surfaces has a test that reads COMMAND_ENVELOPES, so a command that is added to the CLI without a row, or a row without a surface, fails a test instead of shipping a silent gap. Every other visible subcommand is listed in COMMANDS_WITHOUT_ANALYSIS_ENVELOPE with the reason it has no row.

Structs§

CommandEnvelope
The machine contract of one analysis subcommand.

Enums§

CiIntegration
How the GitHub Action and the GitLab CI template treat a command.
ReportFrom
How fallow report --from treats a saved envelope of a command.

Constants§

COMMANDS_WITHOUT_ANALYSIS_ENVELOPE
Visible subcommands that write no analysis report, with the reason.
COMMAND_ENVELOPES
Every analysis subcommand with its JSON kinds and surfaces.

Functions§

command_envelope
The row of command, when it is an analysis subcommand.