* Add man page generation from the command-line model
Add CommandSet.OutputManPage (string and file overloads), a ManPageInfo
type for document-level metadata, a reference ManPage feature invoked as a
man command, and UserInput.FormatManPage which reuses FormatFlags so the
page cannot drift from --help. Output uses only portable man(7) macros and
validates warning-free under groff and mandoc -T lint.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* Address review feedback on man page generation
Rename the man page API to the single-word "Manpage" spelling throughout
(Manpage feature, ManpageInfo, CommandSet.OutputManpage,
UserInput.FormatManpage) for consistency with the "manpage" convention.
- Drop the redundant null check in OutputManpage; info is non-nullable
under the enabled nullable context.
- Move the tests that exercise CommandSet.OutputManpage into
CommandSetTests as a "Manpage Output" region, and relocate the Manpage
feature test into a path-synced Features subfolder
(SabreTools.CommandLine.Test.Features). Private test helpers now sit at
the bottom of their classes.
- Fix the Manpage feature doc example to use the actual "man" command.
Builds clean across all target frameworks; the 235 tests pass and the
generated page still validates warning-free under groff -man -ww and
mandoc -T lint.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
