Meridian.Analyzer 0.2.1

Meridian.Analyzer

Meridian.Analyzer is the canonical implementation surface for Meridian-owned backend Roslyn analyzers.

Documentation

• Usage examples: docs/usage-example.md
• Maintainer guide: docs/guide.md
• Rule docs: docs/rules/MER0001.md
• Rule docs: docs/rules/MER0002.md
• Rule docs: docs/rules/MER0003.md
• Rule docs: docs/rules/MER0004.md
• Rule docs: docs/rules/MER0005.md
• Rule docs: docs/rules/MER0006.md
• Rule docs: docs/rules/MER0007.md
• Rule docs: docs/rules/MER0008.md
• Rule docs: docs/rules/MER0009.md
• Rule docs: docs/rules/MER0010.md
• Rule docs: docs/rules/MER0011.md
• Rule docs: docs/rules/MER0012.md
• Rule docs: docs/rules/MER0013.md
• Rule docs: docs/rules/MER0014.md
• Rule docs: docs/rules/MER0015.md
• Rule docs: docs/rules/MER0016.md
• Rule docs: docs/rules/MER0017.md
• Rule docs: docs/rules/MER0018.md
• Rule docs: docs/rules/MER0019.md
• Rule docs: docs/rules/MER0020.md
• Rule docs: docs/rules/MER0021.md
• Rule docs: docs/rules/MER0022.md
• Rule docs: docs/rules/MER0023.md
• Rule docs: docs/rules/MER0024.md
• Rule docs: docs/rules/MER0025.md

Current Surface

• Analyzer project: Meridian.Analyzer.csproj
• Test project: tests/Meridian.Analyzer.Tests/Meridian.Analyzer.Tests.csproj
• Diagnostic prefix: MER
• Category namespaces: Meridian.Readability, Meridian.Security, Meridian.Architecture, Meridian.Reliability, Meridian.Performance
• Packaging status: packable analyzer package published through nuget.org after the release PR lands; Meridian can consume it locally through a sibling project reference during development
• Current rollout: MER0001 stays wrapper-scoped to apps/backend/Meridian.API/Features/Dev/Controllers/DevController.Diagnostics.cs; MER0002 stays wrapper-default for explicit format and inventory lanes; MER0003, MER0004, MER0005, MER0006, MER0012, and MER0021 are warning in apps/backend/.editorconfig for analyzer-scope backend projects during live analysis and explicit analyzer-enabled lanes; MER0007, MER0008, MER0009, MER0010, MER0011, MER0013 through MER0020, and MER0022 through MER0025 remain inventory-driven unless explicitly scoped by wrapper input

Validation Entry Points

• Local test run: dotnet test tests/Meridian.Analyzer.Tests/Meridian.Analyzer.Tests.csproj -c Release
• Local package smoke check: dotnet pack Meridian.Analyzer.csproj -c Release -o artifacts
• Meridian consumer validation: rtk pnpm backend:analyzers:validate

Use dotnet test and dotnet pack from this repo to validate the standalone package itself. Use backend:analyzers:validate and backend:analyzers:inventory from the Meridian repo when you need consumer-side rollout or inventory evidence. Use backend:analyzers:validate:build against a consumer project to prove analyzer loading during build. Building Meridian.Analyzer.csproj itself is compile validation only, because the analyzer project intentionally does not consume itself. In Meridian, normal backend builds keep analyzers disabled through apps/backend/Directory.Build.props; warning-enabled Meridian rules surface during live analysis and explicit analyzer-enabled lanes such as backend:analyzers:validate, backend:analyzers:inventory, or backend:analyzers:validate:build. Use --diagnostics to scope runs to specific Meridian rules; default diagnostics are MER0001,MER0002.

Staged candidate inventory examples:

• rtk pnpm backend:analyzers:inventory -- --diagnostics MER0003,MER0004,MER0005,MER0006,MER0007,MER0008,MER0009,MER0010,MER0011,MER0012,MER0019,MER0021,MER0022,MER0023,MER0024,MER0025 --project apps/backend/Meridian.API/Meridian.API.csproj
• rtk pnpm backend:analyzers:inventory -- --diagnostics MER0014,MER0015,MER0016,MER0017,MER0018,MER0020 --project apps/backend/Meridian.Infrastructure/Meridian.Infrastructure.csproj
• rtk pnpm backend:analyzers:inventory -- --diagnostics MER0013 --project apps/backend/Meridian.Analytics/Meridian.Analytics.csproj

Current Rules

Rollout State

The current replayable Meridian.API inventory for the narrowed payload-branch contract surfaces 13 candidate diagnostics. The analyzer remains in a bounded pilot until those cases are reviewed and remediated deliberately.

The current replayable MER0002 inventory surfaces 1 candidate in Meridian.Analytics and 0 candidates in Meridian.API. MER0002 remains part of the wrapper-default diagnostic set for explicit format and inventory lanes, with broader inventory review still focused on the remaining Analytics signal.

MER0003, MER0004, MER0006, MER0008, and MER0013 are staged from the first 2026-05-07 backend custom analyzer candidate implementation. MER0003 and MER0004 are now warning in committed .editorconfig for analyzer-scope live analysis and explicit analyzer-enabled lanes, while MER0008 and MER0013 remain inventory-driven. Their first replayable inventory artifact is docs/analysis/2026-05/2026-05-07-backend-custom-analyzer-staged-inventory.md.

MER0005, MER0007, and MER0009 through MER0025 were added from the remaining Roslyn-suitable candidates in the same audit. MER0005, MER0006, MER0012, and MER0021 are now warning in committed .editorconfig for analyzer-scope live analysis and explicit analyzer-enabled lanes; the remaining rules in this packet stay inventory-driven until their queues are classified. Their first replayable inventory artifact is docs/analysis/2026-05/2026-05-07-backend-custom-analyzer-remaining-candidates-inventory.md.

Ownership Notes

• Meridian owns payload-branch initializer conditionals through MER0001.
• Meridian owns broad nested try/catch fallback flow through MER0002.
• Meridian owns unsafe output-cache endpoint metadata drift through MER0003.
• Meridian owns high-signal controller policy presence through MER0004; exact policy correctness stays in tests.
• Meridian owns admin controller shape drift through MER0005; exact admin policy names stay in tests.
• Meridian owns controller-action service location through MER0006; broader runtime service-location review needs allowlists.
• Meridian owns raw configuration/environment read inventory through MER0007; config-file conflicts stay in validators.
• Meridian owns MERIDIAN_SKIP_* raw-read containment through MER0008.
• Meridian owns async controller cancellation exposure through MER0009; overload correctness remains inventory-led.
• Meridian owns deterministic time/delay source drift through MER0010.
• Meridian owns static mutable controller/auth state inventory through MER0011.
• Meridian owns source-level health-check registration parity through MER0012.
• Meridian owns source-level Clean Architecture boundary drift through MER0013; MSBuild/package graph checks stay outside Roslyn.
• Meridian owns obvious model ownership drift through MER0014.
• Meridian owns in-memory string helper usage inventory through MER0015; EF query expressions stay excluded.
• Meridian owns ad hoc JSON option construction inventory through MER0016.
• Meridian owns unbounded EF materialisation inventory through MER0017.
• Meridian owns raw SQL API placement/interpolation inventory through MER0018.
• Meridian owns direct ProblemDetails construction in controller actions through MER0019.
• Meridian owns direct controller repository/DbContext access inventory through MER0020.
• Meridian owns backend logging contract source drift through MER0021.
• Meridian owns direct Redis keyspace scan inventory through MER0022.
• Meridian owns detached runtime task/cancellation inventory through MER0023.
• Meridian owns StringExtensions-in-queryable predicate drift through MER0024.
• Meridian owns empty property-pattern brace guard inventory through MER0025.
• Sonar keeps broader nested-ternary ownership through S3358.
• Broader catch quality remains shared with Sonar and SDK analyzers; MER0002 stays narrow to avoid duplicate exception-handling noise.
• Future backend rules should go through an overlap review before rollout.

Rule-Addition Checklist

Before landing MER0002+ or any later rule, update these four surfaces in the same change:

1. Analyzer + tests:
   • add the analyzer implementation at the repo root beside Meridian.Analyzer.csproj
   • add positive and negative tests under tests/Meridian.Analyzer.Tests/
   • this is allowed by docs/reference/2026-05/2026-05-07-agent-test-creation-policy.md because analyzer tests are the rule contract, not speculative product-behavior tests
2. Operator rollout:
   • update apps/backend/.editorconfig in the Meridian repo
   • confirm the intended wrapper lane in scripts/tooling/run-backend-analyzers.py in the Meridian repo
3. Package docs:
   • add the rule file under docs/rules/
   • add the rule row and rollout state note in this README.md
   • update docs/guide.md or docs/usage-example.md if the workflow changed
4. Replayable evidence:
   • if the rule is inventory-driven or pilot-only, save one dated docs/analysis/ artifact for the candidate queue and link it from the rule doc before any broader warning promotion