Mobile CI health: remaining gate failures after install repair

[RUKAYAT-CODER]

With installs repaired (lock file re-synced in #1075), the remaining CI gates now run and expose several independent, pre-existing failures. Tracking them here so they can be triaged separately from the install/workflow cleanup.

1. Type-check (CI workflow Typecheck)

tsc --noEmit reports ~499 errors across 264 files. Tracked in detail in #1074.

2. Dependency Audit (npm run audit)

scripts/security-audit.js fails: high/critical vulnerabilities present in the dependency tree. Needs dependency upgrades (or an explicitly reviewed allowlist). This aligns with the Dependabot backlog.

3. Dependency boundaries (architecture:check)

The dependency-cruiser@18 upgrade was never finished:

• The workflow pins Node 20, but dependency-cruiser@18 requires Node >= 22.
• dependency-cruiser.config.js is invalid under v18: enhancedResolveOptions must NOT have additional properties (the tsConfig key moved to the top-level options.tsConfig in v18).
• Once the config is migrated, real boundary violations (if any) still need resolving.
  Fix atomically: bump the workflow to Node 22, migrate the config, then address violations.

4. Native Build (iOS & Android)

Both native builds fail; likely downstream of the type/config issues above. Re-evaluate after 1–3 are resolved.

None of these are caused by #1075 — that PR restores installs and trims redundant/flaky workflows so these real issues are visible and fixable.

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in 3days

[Jafeth012]

I’d like to take on resolving these remaining CI gate failures; I have extensive experience optimizing React Native CI/CD pipelines, configuring architectural boundary tools like dependency-cruiser, and performing security audit remediations.

My plan to systematically address steps 2 and 3 includes:

• Dependency Boundaries (architecture:check): Update the GitHub Actions workflow to run on Node 22, migrate dependency-cruiser.config.js to v18 syntax by lifting tsConfig to top-level options, and resolve any architectural boundary rule violations.
• Security Audit (npm run audit): Upgrade vulnerable packages across the dependency tree, resolve lockfile vulnerabilities, and configure an explicitly reviewed audit allowlist/override strategy for unfixable transitive dependencies via scripts/security-audit.js.
• Native Build Validation: Re-evaluate iOS/Android native builds once dependency boundaries and audit steps pass to ensure clean artifact compilation across all CI gates.

Assign this to me and I will submit a PR right away!

[guptakumarranjeet150]

Hi everyone,

I can tackle Mobile CI health: remaining gate failures after install repair. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in rinafcode/teachLink_mobile
• Implementation: Trace the regression in rinafcode/teachLink_mobile causing Mobile CI health: remaining gate failures after install repair and implement a targeted, minimal fix.
• Testing: Add a reproduction test case to prevent any future regression.
• PR: Atomic commit with clean git hygiene and passing CI

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!