[Repo Assist] Add FsDocsAllowExecutableProject setting to fsdocs

[github-actions]

🤖 This PR was created by Repo Assist, an automated AI assistant.

Fixes the constraint in ProjectCracker.fs that unconditionally skipped non-library projects from API documentation generation.

Root cause: The crackProjects function filtered out any project where OutputType != "library", with no way to opt in.

Fix: Adds a new --allowExecutableProjects CLI flag. When set, the OutputType check is skipped and executable projects (Exe/WinExe) are included in documentation generation alongside libraries.

Changes:

• ProjectCracker.fs: Extended crackProjects signature with allowExecutableProjects parameter; added that parameter to the filter condition; improved the skip message to hint at the flag.
• BuildCommand.fs: Added --allowExecutableProjects CLI option and wired it through to crackProjects.
• RELEASE_NOTES.md: Added entry under [Unreleased].

Trade-offs: This is opt-in via the flag so existing users are unaffected. Executable projects that expose public modules/types (like FsAutoComplete) work identically to libraries for API doc purposes.

Test Status

Build: ✅ dotnet build src/fsdocs-tool/fsdocs-tool.fsproj --configuration Release — succeeded with 0 errors.
Format: ✅ Fantomas applied cleanly.

Closes #918

Generated by Repo Assist for issue #918

To install this workflow, run gh aw add githubnext/agentics/workflows/repo-assist.md@828ac109efb43990f59475cbfce90ede5546586c. View source at https://github.com/githubnext/agentics/tree/828ac109efb43990f59475cbfce90ede5546586c/workflows/repo-assist.md.

[github-actions]

✅ Pull request created: #997

[dsyme]

@nojaf I think this should be a project file setting too right, like the other one. Agree with Repo Assist's assessment that it should be opt-in

[dsyme]

/repo-assist This should be a project file setting rather than a command line flag. Obviously opt-in. Make sure docs get updated. Update this PR

[github-actions]

Commit pushed: b3cf5b7

Generated by Repo Assist

[github-actions]

🤖 Repo Assist here. Done — I've updated this PR to use a per-project file setting instead of a CLI flag.

What changed:

• Removed --allowExecutableProjects CLI option from fsdocs build
• Added FsDocsAllowExecutableProject MSBuild property, read per-project (matching the pattern of FsDocsWarnOnMissingDocs, IsTestProject, etc.)
• The filter now checks info.FsDocsAllowExecutableProject on each individual project rather than a global flag
• Updated the skip message to hint at the project file setting
• Updated RELEASE_NOTES.md and docs/commandline.md

Usage: add to any .fsproj or Directory.Build.props:

(FsDocsAllowExecutableProject)true(/FsDocsAllowExecutableProject)

Generated by Repo Assist for issue #997

To install this workflow, run gh aw add githubnext/agentics/workflows/repo-assist.md@b87234850bf9664d198f28a02df0f937d0447295. View source at https://github.com/githubnext/agentics/tree/b87234850bf9664d198f28a02df0f937d0447295/workflows/repo-assist.md.