fix: add atlas parity - regex patterns, rules guidance, dotenv loading #2
+216
−32
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
Regex pattern support for coverage scope: Added ability to use raw regex patterns in coverage scope config by prefixing with
regex:(e.g.,regex:^src/app/.*\.(ts|tsx)$). This matches atlas's precise coverage targeting.Vapi Next.js preset: Added
coveragePreset: 'vapi-nextjs'option with atlas-matching patterns for:src/app/,src/components/,src/hooks/,src/lib/layout.tsx,page.tsx, UI components, barrel files, test filesDetailed rules guidance: Added
rulesGuidanceconfig with Vapi-specific conventions for:Dotenv loading: Added automatic loading of
.env.localon guardian initialization, matching atlas behavior.Test plan
npm run typecheckpassesnpm run lintpassesnpm run buildpassescoveragePreset: 'vapi-nextjs'and verify regex patterns work.env.localvalues are loadedLinear Issue
VAP-11522
Generated with Claude Code