FFFF
Skip to content

feat(migration): isolate static correctness analyzer - #454

Draft
Vijaypepakayala wants to merge 2 commits into
mainfrom
codex/pr318-analyzer
Draft

feat(migration): isolate static correctness analyzer#454
Vijaypepakayala wants to merge 2 commits into
mainfrom
codex/pr318-analyzer

Conversation

@Vijaypepakayala
Copy link
Copy Markdown

Summary

This draft isolates the static migration correctness analyzer requested to be split from #318. It is intentionally separate so the team can decide whether this analyzer should land at its current size, be reduced, or use a different ownership model.

Scope

  • Required-messaging-profile call-site analysis for the supported source languages.
  • Syntax-aware source filtering used by the correctness linter.
  • JavaScript scanning inside Vue, Svelte, and Astro component files.
  • Dedicated analyzer-only regression coverage and CI workflow.
  • Canonical, Claude, and Cursor provider synchronization.

Not included

Validation

  • python3 tests/test_twilio_migration_analyzer.py -v117/117 passed at 3a1b7d3.
  • The latest component-file regression was rerun independently and passed.
  • Shell syntax, Python compilation, provider parity, git diff --check, and clean-worktree checks passed.

Draft for architecture, size, and ownership discussion; not proposed for immediate merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0