chore(lint): enforce anti-slop rules - #141
Merged
Merged
Conversation
Vendor the anti-slop Oxlint plugin and enable its full rule set across application, worker, processor, migration, and test code.\n\nReplace broad runtime narrowing and unsafe assertions with explicit JSON boundary parsing, precise contracts, and structurally typed test doubles so the stricter policy starts from a clean baseline.
HazAT
marked this pull request as ready for review
August 15, 2026 23:05
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 30b1bb1. Configure here.
Force Vite+ to resolve the same pinned Oxlint and plugin versions as the vendored anti-slop integration. This removes the nested older runtime so lint execution and plugin loading share version 1.78.0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

JavaScript and TypeScript linting now enforces the vendored anti-slop rules across the app, worker, video processor, migration tooling, and tests. The existing codebase is migrated to that policy with explicit JSON boundary parsing and narrower domain contracts, preserving current user-facing behavior while making low-evidence casts, broad input types, runtime representation checks, and conditional omission patterns fail future checks.
Reviewers should start with
vite.config.tsandsrc/shared/json.tsto establish the policy and parsing model, then focus on migration reconciliation and video processing where replacing open dictionaries and assertion chains required the most structural change. The plugin is intentionally project-owned and its Oxlint runtime is pinned; the main review risk is whether the stricter boundary parsing exactly preserves accepted payloads and processor results.