jschoubben 63de1f7e0d nox cleanup delete confirms with the holder's name, as the vault asks ...

The vault deletes a retired holder only when confirm repeats its name, so
sending confirm "true" could never delete anything. The stand-in console now
also says which machine answered as a block of its own, as node-tools does.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

2026-11-02 10:47:56 +01:00

..

commands.go

nox cleanup delete confirms with the holder's name, as the vault asks

2026-11-02 10:47:56 +01:00

console.go

nox calls the seats that own each job, not the unassigned controller

2026-11-02 10:41:32 +01:00

enrol_test.go

nox calls the seats that own each job, not the unassigned controller

2026-11-02 10:41:32 +01:00

enrol.go

mesh-cli: nox enrol open opens a sealed enrolment token locally with the operator's private key

2026-11-02 01:42:19 +01:00

main_test.go

nox cleanup delete confirms with the holder's name, as the vault asks

2026-11-02 10:47:56 +01:00

main.go

nox calls the seats that own each job, not the unassigned controller

2026-11-02 10:41:32 +01:00

manifest_test.go

mesh-cli requires the console's endpoint and writes its address

2026-11-02 10:42:03 +01:00