Audit code style and analyzer configuration

Audit project style checkers and static analyzers

Identify linting rule gaps and tool suppression abuse in legacy projects without modifying code.

• · Project root directory
• · Demand files from sibling demands/ directory

• · Markdown report: per-tool config, per-demand coverage, prioritized improvements

Build manifest present (package.json, pom.xml, etc.); demands/ directory with .md files

• · Build manifest not found
• · No demands/ files
• · Unrecognized language ecosystem

• · Non-invasive read-only audit (no file modification)
• · Explicit demand file compliance tracking