Expand description
Analyzer manifests and the flat ParamSpec list. One manifest is the
single source feeding the CLI listing, the HTTP /analyzers route, MCP
listing, param validation, docs, and the console’s analyzer cards
(proposal §11). Hand-rolled with serde_json only — no JSON-Schema dep.
Structs§
- Analyzer
Manifest - An analyzer’s self-description.
- Params
- A fully resolved parameter set: manifest defaults with validated overrides applied. Typed getters never panic — an absent key means the manifest is out of sync, which is an engine bug, so they fall back to the type zero.
Enums§
- Auto
Apply Class - Whether an analyzer’s structural proposals are eligible for auto-apply. Eligibility is necessary, never sufficient — the engine still requires host opt-in, policy allowlisting, and per-draft shape verification (§6.3).
- Cadence
Class - How often an analyzer is worth running; rides per-analyzer time budgets.
- Capability
- Optional substrate capability an analyzer may require.
- Param
Spec - One declared parameter. Six kinds, hand-rolled (proposal §11).
- Target
Class - Target classes an analyzer may propose against.
- Tier
- Analysis tier: T0 pure statistics, T1 embedding-assisted, T2 LLM.
- Trust
Class - Trust class of the analyzer’s code path (drives the console badge).
Functions§
- analyzer_
family publisher.name/major→publisher.name.