trust_not_found
Diagnostic `nanook::cli::trust_not_found`
Summary
no trusted signer matches `{0}`
Help
known signers in {2}: {1}
Details
When this fires
nanook self trust remove or nanook plugins trust remove was called with a fingerprint that doesn't match any configured signer.
What to check
Run the matching list to see what's actually trusted:
The fingerprint match is by prefix, so SHA256:abc is enough as long as it's unambiguous. If your prefix matches more than one entry, you'll see trust_ambiguous instead — paste the full SHA256:<base64> form to disambiguate.