Description

Our ESLint configuration is not catching critical linting errors, resulting in inconsistent code quality and style across the codebase. We need to align our ESLint configuration with the core repository to ensure consistent standards.

Technical Details

• Current ESLint configuration is not enforcing organizational conventions (e.g., using type instead of interface)
• Many important linting rules are either disabled or set to warn instead of error
• We need to align with the core repository's ESLint configuration to maintain consistency across projects

Acceptance Criteria

• ESLint should enforce all critical organizational code conventions
• Configuration should properly align with the core repository's ESLint standards
• ESLint should correctly identify and report linting errors both locally and in CI
• Developers should receive consistent linting feedback across all repositories

References

• Core repository's ESLint configuration
• TypeScript best practices documentation