tools capa

tools-cli-conformance

One function, `assert_conforms(clap::Command)`, that a tool's own test suite calls against its CLI definition: every subcommand has `about` text, every argument has help text, bare invocation shows usage instead of an error, and no subcommand redeclares a global argument (the B-030 class — see crates/tools/browser-test/src/main.rs, mod cli_definition_tests, for the incident this generalizes). A tool's CLI must describe itself; this is the mechanical check that it does.

One function, `assert_conforms(clap::Command)`, that a tool's own test suite calls against its CLI definition: every subcommand has `about` text, every argument has help text, bare invocation shows usage instead of an error, and no subcommand redeclares a global argument (the B-030 class — see crates/tools/browser-test/src/main.rs, mod cli_definition_tests, for the incident this generalizes). A tool's CLI must describe itself; this is the mechanical check that it does.

Tiertools
Roleunclassified (baselined)
Pathcrates/tools/cli-conformance
Edition2021
Targetstools_cli_conformance
Public items1 across 0 modules
Tests8

What it is for

One function: assert_conforms. A tool's own test suite calls it with its clap::Command and gets back either nothing (the definition conforms) or a panic naming the offending subcommand/argument.

The spec this enforces, in one sentence: a tool that refuses for want of an argument must show the form that would have worked, and every tool's CLI definition must be self-describing.

Capabilities

crate root

One function: assert_conforms. A tool's own test suite calls it with

Item
fn assert_conforms(cmd : Command)

How to use it

No examples/ target and no doctest in this crate's rustdoc. The tests listed under Verification are the closest executable usage.

Module structure

No public modules: the crate root is its whole surface.

Public surface

`crate root`

ItemWhat it is
fn assert_conforms(cmd : Command)Assert that cmd is a conforming CLI definition

No pub use re-exports: every item above is declared in this crate.

Boundary

Depends on no other workspace tier.

Shares tier tools with 84 other crates: tools-advisory-reach, tools-archive-guard, tools-artifact-scaffold, tools-ask-ai-core, tools-ask-ais, tools-ask-gemini, tools-book, tools-book-report, … (84 total).

_What this crate deliberately does NOT own is a judgment. No committed registry records one for it, so none is stated here._

Where it sits

Tier (ontology)tools
Architectural role (taxonomy)unclassified (baselined)
Locationcrates/tools/cli-conformance
Vocabulary in force (lexicon)current

Dependencies

Runtime, from outside the workspace.

CrateRequirementFeaturesOptionalOnly on
clap^4noalways

Development. None.

Build. None.

Depended on by. 39 workspace crates.

Signal flow — what reaches this crate, and what it reaches.

flowchart LR
  consumers["39 consumer crates"] -->|uses| SELF
  SELF["tools-cli-conformance"]
  classDef self fill:#1f883d,stroke:#1f883d,color:#fff;
  class SELF self;

Feature flags

No Cargo features are defined: every capability is unconditional, so no consumer can receive a half-wired crate.

Targets

KindNameSource
libtools_cli_conformance`src/lib.rs`

Error model

No public error type was detected: no public item declares a type named *Error, and no public signature returns one.

Operational characteristics

PropertyEvidence
async public surfacenone detected
async runtimenone detected
database accessnone detected
network I/Onone detected
unsafe codenone detected
environment variablesnone detected

No unsafe block, unsafe fn, unsafe impl or unsafe trait was found by the parser anywhere in this crate's source.

Configuration

No environment variable is read with a literal name anywhere in this crate. A variable whose key is computed at run time cannot be listed here, and is not claimed to be absent.

39 workspace crates depend on this one: application-wiki, domain-prose-shard, domain-table-shard, domain-transcript-shard, foundation-text-deidentify, tools-artifact-scaffold, tools-book, tools-book-report, tools-browser-test, tools-consolidate-worktrees, tools-corpus, tools-crate-capability-audit, … (39 total).

Verification

KindCount
Unit tests8
Integration tests0
Examples0
Doctests0

Evidence by module. How often each public module is named by something executable.

ModuleTestsExamplesConsumers
crate root1039

What the tests establish, by name:

Documentation coverage

MeasureDocumentedTotal
Public items with rustdoc11
Public modules with a //! block00
pie showData
    title Public items with rustdoc
    "Documented" : 1
    "No rustdoc detected" : 0

Metrics

MetricValue
Rust source files1
Source lines255
Code lines182
Public API items1
Public modules0
Tests8
Examples0
Cargo features0
Direct runtime dependencies1
Workspace reverse dependencies39
pie showData
    title Public API by kind
    "function" : 1
pie showData
    title Rust source composition
    "Code" : 182
    "Blank or comment" : 73

Generation

Rendered by tools-corpus corpus readme from repository evidence alone, renderer schema 2, lexicon current. No model, network service or database was consulted. Regenerate with tools-corpus corpus readme --write; verify with --check.

Todas las tools · Manual