TRF010

Direct config definitions must use @strict(accept_kwargs=True).

Default	Enabled
Scope	All models
Source	mlinter/trf010.py
Show in terminal	mlinter --rule TRF010

What it does

Checks direct PreTrainedConfig/PretrainedConfig subclasses in configuration_*.py and modular_*.py for an explicit @strict(accept_kwargs=True) decorator.

Why is this bad?

Without strict, new config classes miss the repo’s runtime type-validation contract and drift from the dataclass-based config standard.

Example

+@strict(accept_kwargs=True)
 class AcmeConfig(PreTrainedConfig):
     ...

Suppressing this rule

Add a # trf-ignore: TRF010 comment on the flagged line or the line directly above it. See Suppressing rules for whole-file directives and when a suppression is the wrong answer.

Allowlisted models

2 models are exempt from TRF010 in mlinter/rules.toml, because they predate the convention and cannot be changed without breaking backward compatibility.

Show the 2 allowlisted models

• nemotron_h
• vibevoice_asr