Repository navigation
Eliminate 612 legacy any uses and enforce strict typing - #61
Merged
Merged
Conversation
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
Replace the 612 legacy explicit-any violations with database, middleware, SDK and domain types plus validated JSON boundaries. Delete the lint allowance and enable
noImplicitAny; existing ESLint rules remain intact.Correct the schema mismatches exposed by typing, including ownership, upload completion, OAuth token IDs, package tags and internal search-vector serialization. Execution telemetry writes once through the authoritative rate-limited RPC. Preserve the pinned Stripe gateway contract and token-only reauthentication emails.
Evidence
After: zero lint errors and zero explicit-any violations across 636 files; no rule suppressions added. Generated router exclusions are unchanged.
docs/testing/TYPE-SAFETY-RELEASE.md.Merge Danger
Door: two-way
Application code rollback; no database migration is applied.
Blast Radius: application
Broad type refactor across server functions, MCP, SDK and UI. Billing sends, real emails and paid model calls are covered with local fixtures rather than production execution.