Add LintLang linter plugin

[roli-lpci]

Summary

Disclosure: We are the developers and maintainers of LintLang at Hermes Labs.

• add the released LintLang 0.8.2 Python-runtime linter plugin
• emit its native SARIF diagnostics for supported Markdown, YAML, JSON, and Python instruction/config inputs
• include clean and finding fixtures plus the required README entry
• retain the 0.6.0 snapshots and add version-specific 0.8.2 snapshots

Validation

• PLUGINS_TEST_LINTER_VERSION=KnownGoodVersion npm test -- linters/lintlang --runInBand --verbose: 2 tests and 2 snapshots passed, exercising Trunk installation, execution, and SARIF parsing with LintLang 0.8.2
• npm test -- tests/repo_tests --runInBand --verbose: 236 tests passed
• trunk check --upstream=upstream/main --filter=definition-checker --output=json --no-fix: passed
• commit hook: 3 modified files checked, no issues

The command intentionally preserves LintLang's SARIF distinction between scanner findings and input-error invocation notifications.

This contribution was produced by agents through Hermes Labs’ engineering infrastructure. Rolando Bosch is the responsible human contributor and authorized publication from his personal GitHub account.

[trunk-io]

Merging to main in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

[roli-lpci]

/trunk merge

[trunk-io]

An error occurred while submitting your PR to the queue: Only users that are a part of this repo's Trunk organization or have write permissions to the repo can submit a PR to the queue

[roli-lpci]

This PR looks code-complete and mergeable, but CI has not actually run yet: both "Pull Request" and "Code Scanning - Action" are sitting at action_required, which needs a maintainer to approve workflow runs for an outside contributor. Separately, /trunk merge from a non-member cannot submit to the merge queue. Could a repository member approve the workflow runs, and if the results look good, submit it to the queue?