Skip to main content

Module cli

Module cli 

Source
Expand description

The abstractcore CLI subprocess client — the console’s only lane into Python-derived views (and, in M2, into every coupled write).

Runs ONLY on the worker thread. Machine surfaces only: JSON stdout from config … --json subcommands and exit codes; human output (--status, wizard prose) is never scraped (risk-map fact #9).

Structs§

CliError
CliInfo
Where the binary came from — rendered in the header/overview so “which abstractcore am I driving” is always answered.
CliOutput
A successful CLI run: the JSON payload PLUS any labeled degradation the Python side printed to stderr while exiting 0. The #FALLBACK lane is load-bearing (adversarial review P1-1): when Python cannot load the config file it backs it up, runs on DEFAULTS, prints one #FALLBACK … stderr line — and the JSON body still says ok: true. Dropping that line made the mirror vouch for a file Python refuses.
CoreCli

Enums§

CliErrorKind

Functions§

resolve_bin
How the console finds abstractcore, first hit wins:
resolve_bin_from_env
resolve_chat_bin
The chat binary ships in the same bin dir as abstractcore; a sibling lookup keeps both binaries from the SAME install (a PATH hit from a different venv would test a different abstractcore) — the PATH fallback is flagged so the mismatch never goes silent.