docs: draft agent-oriented linting paper#67
Draft
danielchen0 wants to merge 27 commits into
Draft
Conversation
arnavsurve
reviewed
May 17, 2026
arnavsurve
reviewed
May 27, 2026
arnavsurve
reviewed
May 27, 2026
arnavsurve
reviewed
May 27, 2026
arnavsurve
reviewed
May 27, 2026
arnavsurve
reviewed
May 27, 2026
arnavsurve
reviewed
May 28, 2026
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.
Summary
Drafts an arXiv-style paper for laint around agent-oriented linting for generated JSX/TSX applications. The current draft frames laint as both an expert-curated benchmark and a feedback-loop tool for surfacing framework-specific generated-app failures before slower build, preview, device, or runtime checks.
The PR now includes checked-in raw prompt-grid artifacts, generated result tables, and a repair-loop pilot. The repair results are framed as diagnostic-feedback compliance signals: 476 -> 101 reported findings, 375 net reduction, 445 rule-level findings resolved, and 70 introduced findings across the repair loop. The paper still treats these as raw benchmark signals until human precision/recall labeling and downstream build/runtime/user-acceptance checks are added.
Verification
npm run lintnpm run buildnpm run knipnpm testnpm run paper:tablesmake -C paperpaper/main.logfor undefined refs/citations and overfull/warning/error linesRemaining Before Submission