integration-by-batches-mobilelisted
Install: claude install-skill RonenMars/threadbase-mobile
# Integration by batches (mobile)
The method (hard rules, grouping, plan and log, QA findings, landing loop, cleanup) lives in the shared skill `threadbase-skills:integration-by-batches`. Read it first. This file holds only what is specific to this repo. Where it is stricter than the shared skill, follow it.
Origin: a 24-PR, 8-batch run on tb-mobile (2026-10-03 to 10-08).
## Building a batch
- Real `npm ci` in the batch worktree, which sits outside the repo (`../tb-mobile-worktrees/int-<date>-bN`).
- Reconcile "+N suites" with `git diff --name-status` (`A` files) and `jest --listTests`.
- Heavy suites report false failures in a batch run. Confirm any failure with `npx jest --ci --runInBand --testPathPattern <suite>` alone before classifying it.
- Register new test files in the shard manifest (`scripts/ci-*-shards.json`, and `ci-script-test-shards.json` for script tests) or CI goes red while the code is fine.
- After any change to `package.json`: `bundle exec pod install` (never bare), commit `ios/Podfile.lock` with it except the four path-dependent checksums, and use `scripts/reset-podfile-lock-path-noise.sh`, never `git checkout --`.
- Validate with `tsc --pretty false` (ANSI output defeats `grep -c`), eslint on changed files, the full jest suite against the baseline delta, and `npm run test:i18n` when locales moved.
- Grouping: a change that does not touch the app binary needs CI only, no device QA build. `jest-expo` pins jest 29; if a dependency bump drags jest 30 in,