Problem
Documentation text may legally come from localized resources (WritingErrorsGuide.en.md:10), which the literal-based Roslyn content rules (FCE005/FCE014/FCE015) structurally cannot see. A team that localizes its error documentation — a first-class scenario per Internationalization — silently loses all text-quality enforcement, and nothing documents the limitation. No CLI verb applies the BestPractices/WritingErrorsGuide checklists to the extracted, post-localization catalog.
Impact
The content-quality half of the analyzer suite has a systematic blind spot for exactly the users who invest most in the documentation.
Direction
- Add
fce lint (or fce catalog lint): run content checks over the extracted catalog per locale — generic titles/codes, empty descriptions, missing examples, short==detailed public messages, diagnostics without analysis leads.
- Reuse the existing extraction pipeline, exit-code conventions (0/1/2/130) and report formats (
--report text|markdown|json, --fail-on).
- Document the Roslyn-rules-vs-resources limitation where the rules are documented.
Acceptance criteria
- A resource-localized catalog with a generic title fails
fce lint while passing the build; CI can gate on it per locale; the verb is documented (EN+FR) alongside the other CLI references.
Context
Surfaced by the 2026-07-20 architecture, design & ecosystem audit (doc/handwritten/for-maintainers/audit/2026-07-20-firstclasserrors-architecture-and-design-audit.md, §13.3(e)/§14-HV5; branch claude/firstclasserrors-audit-83gap7).
Problem
Documentation text may legally come from localized resources (
WritingErrorsGuide.en.md:10), which the literal-based Roslyn content rules (FCE005/FCE014/FCE015) structurally cannot see. A team that localizes its error documentation — a first-class scenario per Internationalization — silently loses all text-quality enforcement, and nothing documents the limitation. No CLI verb applies the BestPractices/WritingErrorsGuide checklists to the extracted, post-localization catalog.Impact
The content-quality half of the analyzer suite has a systematic blind spot for exactly the users who invest most in the documentation.
Direction
fce lint(orfce catalog lint): run content checks over the extracted catalog per locale — generic titles/codes, empty descriptions, missing examples, short==detailed public messages, diagnostics without analysis leads.--report text|markdown|json,--fail-on).Acceptance criteria
fce lintwhile passing the build; CI can gate on it per locale; the verb is documented (EN+FR) alongside the other CLI references.Context
Surfaced by the 2026-07-20 architecture, design & ecosystem audit (
doc/handwritten/for-maintainers/audit/2026-07-20-firstclasserrors-architecture-and-design-audit.md, §13.3(e)/§14-HV5; branchclaude/firstclasserrors-audit-83gap7).