invalid-field-types not showing file path

[sbp-bvanb]

ERRO[0000] invalid-field-types: Field 'tag' references undefined type 'Tag' (line 210)
ERRO[0000] Available types: [ID String Int Float Boolean TagInput Any PageInfo Measurement MeasurementsWithoutPagination AggregateFunction Quantity DateTime Query Measurements Subscription]

as filepath is not included, one cannot quickly resolve the issue

[sbp-bvanb]

Adding detail so this can be picked up without guessing.

What happens

invalid-field-types prints via log.Errorf directly instead of going through the collected-error reporting path, so it never gets a file path:

ERRO[0000] invalid-field-types: Field 'tag' references undefined type 'Tag' (line 210)
ERRO[0000]   Available types: [ID String Int Float Boolean TagInput ...]

Repro

Run the linter against a directory containing more than one schema file where one field references an undefined type. The reported line 210 cannot be attributed to a file.

Expected

path:line: invalid-field-types: Field 'tag' references undefined type 'Tag' — same shape as every other rule, i.e. appended as a models.DescriptionError with FilePath set so it flows through report.printDetailedErrors and is counted in the error-type summary.

Where in the code

• internal/app/graphql-linter/data/base/rules/rules.go:831-838 — the two direct log.Errorf calls (references undefined type and Available types:).
• Contrast with e.g. the suspicious-enum path around rules.go:690, which appends models.DescriptionError{FilePath: schemaPath, LineNum: line, Message: ..., LineContent: ...}.
• internal/app/graphql-linter/application/report/report.go:122 — where correctly-collected errors get their path:line: prefix.

Scope — this is not just one rule

rules.go has 5 direct log.Errorf calls, all with the same defect. Some of them additionally double-report: they log immediately and append a DescriptionError, so the same problem is printed twice. Fixing only the invalid-field-types path leaves the siblings broken; they should all be converted to DescriptionError in one go.

grep -n "log.Errorf" internal/app/graphql-linter/data/base/rules/rules.go

Done when

• grep -c "log.Errorf" internal/app/graphql-linter/data/base/rules/rules.go returns 0.
• Output for an undefined-type violation includes the file path.
• No error is printed twice.
• task remote:test and task remote:test-component pass.

Related: #8 (same reporting path, output formatting).