[devops] - Set Up Monorepo-Wide Type Coverage Reporting

[dark-sarge]

Location: .github/workflows/type-coverage.yml

Description

TypeScript's any type can silently erode type safety across the codebase. Tracking the percentage of type-covered code over time, and setting a minimum threshold, prevents gradual weakening of type safety as the codebase grows.

Acceptance Criteria

• type-coverage npm package is installed as a root devDependency.
• A pnpm type-coverage script runs type-coverage --detail --strict across all workspace packages and outputs a coverage percentage.
• A minimum type coverage of 95% is enforced — the script exits non-zero if coverage falls below the threshold.
• A type-coverage.yml GitHub Actions workflow runs the check on every PR and posts the coverage percentage as a PR comment showing the delta from the base branch.
• All existing explicit any casts in server/ and frontend/ are audited; those that cannot be removed immediately are annotated with // eslint-disable-next-line @typescript-eslint/no-explicit-any -- TODO #<issue> comments.
• The type coverage percentage is added as a badge in the repository README.

---

[basto01]

@basto01 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I understand the expected outcome and would love to work on this. I'll provide a solution that satisfies the acceptance criteria.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @basto01 to this issue.

[adewalere-ctrl]

@adewalere-ctrl has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I’m interested in taking on this task and can dedicate the necessary time to produce a clean and reliable solution within the expected timeframe.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @adewalere-ctrl to this issue.

[Steven2211]

@Steven2211 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello, I’d like to contribute to this issue and would appreciate the opportunity to work on it. Thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Steven2211 to this issue.

[Aswumi]

@Aswumi has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I understand the requirements and acceptance criteria. I’m ready to implement the requested changes and deliver a solution that meets the design specifications.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Aswumi to this issue.

[EbukaMoses]

@EbukaMoses has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer,

I’d like to apply to work on this issue.

I’m Ebuka Moses, a full-stack and blockchain developer with experience building, testing, and maintaining smart contracts, particularly using Rust and blockchain-based architectures. I’m comfortable working with contract logic, validation, access control, persistent storage, and event handling, and I always pay close attention to correctness, security, and edge cases.

I take time to fully understand the issue requirements before implementing a solution, and I ensure my work follows the project’s coding standards. I also write clear, well-tested code and submit clean pull requests with meaningful commits.

I’m confident I can deliver a solid solution that meets the acceptance criteria and adds value to the project.

Thank you for your consideration, and I look forward to contributing.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @EbukaMoses to this issue.