cli¶
Command-line entry point: argument parsing, project scaffolding, and the run summary.
cli
¶
Command-line entrypoint for the crossverify verification harness.
A thin wrapper over :mod:crossverify.api: it parses arguments, calls the API,
and renders the result as a one-screen summary plus an exit code. All the
orchestration lives in the API so the CLI and the MCP server behave identically.
Examples:
python -m crossverify --project examples/project.yaml
python -m crossverify --project examples/project.yaml --skip-r
python -m crossverify --project examples/project.yaml --phases 1,3,5
python -m crossverify --init my_study/
main(argv=None)
¶
Parse arguments, run the verification via the API, and print a summary.
Either scaffolds a new project (--init) or runs the selected phases on the
named project and prints a one-screen per-phase summary. The verification
itself is delegated to :func:crossverify.api.verify.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
argv
|
Argument vector to parse; when |
None
|
Returns:
| Type | Description |
|---|---|
|
Process exit code: |
|
|
project failed validation. The |
Raises:
| Type | Description |
|---|---|
SystemExit
|
Raised by |
FileNotFoundError
|
If the project file does not exist (via the API). |
ValueError
|
If the project file is missing the required |
Source code in crossverify/cli.py
_print_summary(result)
¶
Print a one-screen, per-phase pass/fail/info summary and the output location.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
result
|
A :func: |
required |
Returns:
| Type | Description |
|---|---|
|
None. Output is written to stdout. |
Source code in crossverify/cli.py
_print_scaffold(result)
¶
Print the result of scaffolding a new project (--init).
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
result
|
A :func: |
required |
Returns:
| Type | Description |
|---|---|
|
None. Output is written to stdout. |