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§
- Command
Envelope - The machine contract of one analysis subcommand.
Enums§
- CiIntegration
- How the GitHub Action and the GitLab CI template treat a command.
- Report
From - How
fallow report --fromtreats 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.