Exclude Capacitor sync output from codebase context

[riderx]

Summary

• exclude Capacitor-synced web bundle copies from codebase extraction
• keep actual Android and iOS source files available in context
• add regression coverage for both native Git and isomorphic-git collection paths

Why

Capacitor sync copies the built web app into native folders like android/app/src/main/assets/public and ios/App/App/public. Those files are generated artifacts and can drastically inflate token usage in Dyad after mobile syncs.

Addresses #1149.

Testing

• npm test -- src/tests/git_utils.test.ts src/tests/codebase.test.ts
• npm run lint
• npm run fmt:check
• npm run ts

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[gemini-code-assist]

Code Review

This pull request introduces a mechanism to exclude Capacitor-generated artifacts from the codebase extraction process to prevent token inflation. It defines specific path prefixes for Android and iOS Capacitor build outputs and implements path normalization and exclusion logic in both native and isomorphic git collection methods. Additionally, a new test suite was added to verify these exclusions. I have no feedback to provide.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 3 additional findings.

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.