docs(processor): update comments for anlmdn-based noise profile usage

[flexiondotorg]

No description provided.

[cubic-dev-ai]

2 issues found across 3 files

Confidence score: 5/5

• Both issues are low-severity documentation mismatches in internal/processor/processor.go with no direct runtime impact, so risk is minimal.
• The most notable item is the inaccurate pass descriptions (Pass 3/4 loudnorm and Pass 2 filter-chain order), which could mislead maintainers but won’t affect behavior.
• Pay close attention to internal/processor/processor.go - update pass-description comments to match the current processing pipeline.

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="internal/processor/processor.go">

<violation number="1" location="internal/processor/processor.go:42">
P3: The Pass 2 filter-chain comment is incomplete and no longer reflects the actual Pass2FilterOrder (it omits downmix, DS201 high/low-pass, and analysis/resample). This makes the documentation misleading for maintainers relying on this summary.</violation>

<violation number="2" location="internal/processor/processor.go:43">
P3: The comment says loudnorm is applied in Pass 3, but Pass 3 is measurement-only and loudnorm (with optional Volumax-style limiter) is applied in Pass 4. This pass description is inaccurate relative to the implementation.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}