The node list carried the authentication method and the credential status as two
stacked elements, but a healthy credential says nothing the green tag does not
already say. Only an unhealthy one earns its own word, so rotating, unpaired and
revoked now replace the method name in a single tag.
Adding the Node Secret field to the node form left no way to read a stored
secret back out, which is what an operator needs when adopting further nodes.
Editing a node now reveals it through the same flow the protected settings use:
the list response carries only the redaction sentinel, and the value itself
comes from a dedicated endpoint that demands a verified secure session.
Submitting the form untouched echoes that sentinel back, so the mutation path
now reads it as "keep the stored value" instead of storing the sentinel as the
node's secret.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
