[Bugs5382]

What and why

Docs companion for CryptOS-PKI/cryptos-manager#150 and CryptOS-PKI/cryptos-web#143. When the Fleet Manager adopts a node, the adoption now pauses after the node reboots until an admin confirms the installed node's fingerprint against the Mgmt SHA-256 line on its console. Before, the manager pinned that certificate on first use.

• Fleet Manager overview, "Adopting a new node": a new step 6 for the confirm, with a caution callout for a mismatch. The phase table gains awaiting-fingerprint-confirmation (waits up to 15 minutes). "Re-adopting a node" says a retry confirms again, and that a root that finished its ceremony presents a CA-signed certificate by then.
• Node trust, "What adoption records": the pin is written only after the confirm. The page covers what stops an adoption with nothing recorded (mismatch, 15-minute timeout, cancel), the two audit events, and a warning that a confirmation must reach the replica running the adoption.
• Web UI, "Adopt": a new step 4 names the Fingerprint matches the console and Does not match: cancel adoption buttons, plus a screenshot placeholder.

Refs CryptOS-PKI/cryptos-manager#144
Refs CryptOS-PKI/cryptos-manager#135

Merge order: merge together with CryptOS-PKI/cryptos-manager#150 and CryptOS-PKI/cryptos-web#143.

Verification

• Lint clean
• Tests pass
• Build succeeds
• Documentation updated (if behavior or API changed)

How this was verified

• npm run build passes with no broken links.
• The text was checked against the manager and web changes: the streamed detail text, the 15-minute wait, the error codes, the audit event kinds and the button labels.

[Bugs5382]

Merging for the v0.1.0 test run: CI green and mergeable at merge time.