AC1: nox licence and nox licence list call the licence manager's licences and bindings and print one table of each, every time local.
AC2: nox licence usage [<licence>] prints the usage readings as a table.
AC3: --json prints the raw answer on every rendered line, nox nodes included; for the two calls one object {licences, bindings}.
AC4: every retired controller line (the instead lines and the unowned map) is deleted with its text; a retired line answers "is not a command" with exit 2, and nothing nox prints names the controller. Comments, help and README no longer name the controller or issue 1126 (the operator, 2026-11-22 20:41: "why are there still references to the controller?").
Also under: one-question-one-tool; principle 4, a module is steered by its tools.
Reviewed-by: mesh-code-reviewer@shanks at 3ff4df5c6e
Builds issue 1126 (note 151, answers 1-5, and note 152), acceptance 1126/AC1-AC4:
- **AC1**: `nox licence` and `nox licence list` call the licence manager's licences and bindings and print one table of each, every time local.
- **AC2**: `nox licence usage [<licence>]` prints the usage readings as a table.
- **AC3**: `--json` prints the raw answer on every rendered line, `nox nodes` included; for the two calls one object `{licences, bindings}`.
- **AC4**: every retired controller line (the `instead` lines and the `unowned` map) is deleted with its text; a retired line answers "is not a command" with exit 2, and nothing nox prints names the controller. Comments, help and README no longer name the controller or issue 1126 (the operator, 2026-11-22 20:41: "why are there still references to the controller?").
Also under: one-question-one-tool; principle 4, a module is steered by its tools.
Reviewed-by: mesh-code-reviewer@shanks at 3ff4df5c6ef7ac0b0d7254757d3626d5bdc5f022
The operator typed `nox licence` and got the retired controller's refusal
instead of the licences. `nox licence` and `nox licence list` now call the
licence manager's licences and bindings and print one table of each, every
time local (1126/AC1); `nox licence usage [<licence>]` prints the usage
readings as a table (1126/AC2). `--json` prints the raw answer on every
rendered line, `nox nodes` included: one behaviour for one flag; for the
two calls one object {licences, bindings} (1126/AC3).
In the same change, the operator (2026-11-22 20:41): "why are there still
references to the controller?". Every retired controller line nox answered
with "this was the controller's" (its `instead` lines and the `unowned`
map) is deleted with its text: none has a seat verb of the same job; a
retired line now answers "is not a command" with exit 2, and nothing nox
prints names the controller (1126/AC4). The comments, help and README no
longer name the controller or issue 1126.
Builds: issue 1126 note 151, answers 1-5, and the note after it (acceptance
1126/AC1..AC4, the operator's 20:41 line); one-question-one-tool;
principle 4, a module is steered by its tools.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Builds issue 1126 (note 151, answers 1-5, and note 152), acceptance 1126/AC1-AC4:
nox licenceandnox licence listcall the licence manager's licences and bindings and print one table of each, every time local.nox licence usage [<licence>]prints the usage readings as a table.--jsonprints the raw answer on every rendered line,nox nodesincluded; for the two calls one object{licences, bindings}.insteadlines and theunownedmap) is deleted with its text; a retired line answers "is not a command" with exit 2, and nothing nox prints names the controller. Comments, help and README no longer name the controller or issue 1126 (the operator, 2026-11-22 20:41: "why are there still references to the controller?").Also under: one-question-one-tool; principle 4, a module is steered by its tools.
Reviewed-by: mesh-code-reviewer@shanks at
3ff4df5c6eThe operator typed `nox licence` and got the retired controller's refusal instead of the licences. `nox licence` and `nox licence list` now call the licence manager's licences and bindings and print one table of each, every time local (1126/AC1); `nox licence usage [<licence>]` prints the usage readings as a table (1126/AC2). `--json` prints the raw answer on every rendered line, `nox nodes` included: one behaviour for one flag; for the two calls one object {licences, bindings} (1126/AC3). In the same change, the operator (2026-11-22 20:41): "why are there still references to the controller?". Every retired controller line nox answered with "this was the controller's" (its `instead` lines and the `unowned` map) is deleted with its text: none has a seat verb of the same job; a retired line now answers "is not a command" with exit 2, and nothing nox prints names the controller (1126/AC4). The comments, help and README no longer name the controller or issue 1126. Builds: issue 1126 note 151, answers 1-5, and the note after it (acceptance 1126/AC1..AC4, the operator's 20:41 line); one-question-one-tool; principle 4, a module is steered by its tools.