wiki: use ASCII page names Six page names used the U+2010 hyphen, which the web editor writes to show a hyphen in the page title. Rename them to plain ASCII names which read well with each '-' shown as a space, and update the links. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
wiki: update the pages for nvme-cli 3.2 nvme-cli 3.2 is released. Drop the "(unreleased)" tags and match the pages to the 3.2 code: privilege separation and the decoder sandbox are technology previews now, nvme-discoverd and nvme-keysd install sample config files, the nvme-discoverd timers moved to [Discovery], --persistent force fails, discovered subsystems get their own KX-HMAC-CHAP secrets, and the build page lists libarchive, FreeBSD and the release binaries. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
wiki: match the pages to the current nvme-cli code nvme-keysd is implemented. Rewrite its page from nvme-keysd(8) and the README. The daemon is a oneshot unit, reads the credentials from /etc/nvme/creds/, and uses the file name as the credential name. nvme-cli 3.2 defaults --persistent to auto. nvme-discoverd honors persistent=force since 3.1. Update the PDC page. nvme-cli 3.2 builds nvme-discoverd by default and the legacy autoconnect only when nvme-discoverd is not built. The legacy units skip their connect step while nvme-discoverd runs. nvme-discoverd supports mDNS with systemd 258 or later. Update the nvme-discoverd and autoconnect pages. The sed and scaleflux plugins no longer issue raw ioctls. Update the Privilege Separation page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
wiki: add nvme-keysd and Privilege Separation pages Both features are in the design phase. Add a page for each, so users can see how they are planned to work and where to comment. nvme-keysd is discussed in linux-nvme/nvme-cli#3719. Privilege separation is discussed in linux-nvme/nvme-cli#3879. Link both pages from Home and the sidebar. Also add the missing nvme-discoverd link to the sidebar. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>