|
|
`status` becomes the one place to look (party/status.rs): everything
about the federation at the node but the values, which `get` and
`values` read.
* the store: its ID, checkpoint, heads, what it took, its stop;
* the node: its party, whether it votes by itself, the revisions it knows;
* the version: number, hash, federation, revision, how many pass a change;
* every party: the keys its version names and its key set, --key's
marked, and its nodes, each with its name, how long ago the node heard
from it, and what it runs (wire versions, newest revision);
* every proposal on the current version: how it stands, who voted what
and who not yet, who proposed it and what it does (version_lines, as
`show` says it), what moving to its checkpoint refuses, why no client
backs it;
* what the node refused of its own;
* the party the client works as: its --key, its record held against the
node's votes, what `again` signs again;
* the warnings of what may keep votes away (cut_off).
It is built as one JSON object (`model`), which `--json` writes, its
`format` (FORMAT, 1) raised where it changes otherwise than by more
members; what people read is rendered from it (`render`), and may change
from release to release. On a terminal, in colour (Paint): true colour
where COLORTERM says so, 256 where TERM does, else the basic eight; none
with NO_COLOR, TERM=dumb, or off a terminal. What is fine is green, what
needs a look yellow, what is wrong red; headings and the shortest prefix
naming a proposal bold.
|