docs(native): point the three native runbooks at mono

[Hugo0]

Summary

The three native runbooks were consolidated into the mono repo under engineering/native/ so there is one source of truth. The copies that stayed in peanut-ui/docs/ have since drifted and now state facts that are wrong:

• the wrong Capgo deploy triggers,
• a CI secret name that no longer exists,
• the wrong Sumsub plugin package.

Anyone landing on them today gets misled. This replaces each body with a ~4-line pointer to the mono location.

File	Now points at
docs/NATIVE-RELEASE.md	engineering/native/release-android.md (+ local dev / emulator setup → engineering/native/agency-onboarding.md)
docs/NATIVE-RELEASE-IOS.md	engineering/native/release-ios.md
docs/DEMO-MODE.md	engineering/native/demo-mode.md

Design notes / accepted trade-offs

• Pointers, not deletions. Three files in the release pipeline still reference these paths — .github/workflows/android-release.yml, .github/workflows/ios-release.yml, scripts/native-release.sh. They are deliberately left untouched and resolve fine through the pointer files. Deleting the docs would break those references; that cleanup is a separate follow-up if anyone wants it.
• Repo-relative paths, not github.com URLs. Some readers have a partial copy of mono rather than the full repository, so a github.com link would not resolve for them, while engineering/native/release-android.md is correct in both cases.

Risks / breaking changes

None. Markdown only — no runtime, no imports, no build graph. No cross-repo action needed.

QA

git diff --stat is 3 markdown files, +7 / −568. Local gate: prettier ✅ · jest 1847/1847 ✅ · typecheck unaffected (no TS reads .md).

Screenshots: N/A (no visible change).

Companion PR

This is the dev half. Both dev and main carry the stale copies byte-identically, so the same commit is cherry-picked onto each branch. The main PR is #2540.

Merging only one would leave the other branch serving wrong instructions. The two diffs are byte-identical, so the next dev → main release train merges without conflict.

Summary by CodeRabbit

• Documentation
  • Updated demo mode documentation with a pointer to its new location.
  • Relocated iOS release and TestFlight guidance to the centralized native runbooks.
  • Relocated Android release, signing, CI, OTA, and emulator setup guidance to the centralized documentation.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
peanut-wallet	Ready	Preview, Comment	Jul 28, 2026 9:32am

[coderabbitai]

📝 Walkthrough

Walkthrough

Three native documentation pages were shortened to relocation notices pointing to consolidated monorepo runbooks for demo mode, Android release, iOS release, and emulator onboarding.

Changes

Native runbook documentation

Layer / File(s)	Summary
Native runbook relocation notices docs/DEMO-MODE.md, docs/NATIVE-RELEASE.md, docs/NATIVE-RELEASE-IOS.md	Detailed native runbook content was replaced with pointers to the corresponding monorepo documentation and onboarding guide.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested reviewers: innolope-dev

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: redirecting the three native runbooks to the monorepo versions.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/native-runbook-pointers

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🧪 UI test report — ✅ all green

Suites

• ✅ unit: 2254 ran, 0 failed, 0 skipped, 36.5s

📊 Coverage (unit)

metric	%
statements	60.4%
branches	43.8%
functions	49.6%
lines	60.9%

⏱ 10 slowest test cases

time	test
3.9s	src/components/Card/share-asset/__tests__/shareAssetLayout.test.ts › never places two stickers in heavy overlap (broad seed sweep)
0.9s	src/utils/__tests__/demo-api.test.ts › isDemoMode() is false when not running under Capacitor
0.5s	src/components/Card/share-asset/__tests__/shareAssetLayout.test.ts › every sticker stays within canvas at any count
0.4s	src/app/actions/__tests__/api-headers.test.ts › should include Content-Type in validateInviteCode
0.3s	src/utils/__tests__/sentry.utils.test.ts › defaults to the client budget under a browser global
0.3s	src/app/(mobile-ui)/withdraw/__tests__/withdraw-states.test.tsx › Bank withdrawal keeps the $1 minimum for sub-$1 amounts
0.3s	src/utils/__tests__/sentry.utils.test.ts › still lets a per-call timeoutMs win over the default
0.3s	src/components/Card/share-asset/__tests__/shareAssetLayout.test.ts › keeps stickers off the username pill (final pass respects the keep-out)
0.2s	src/utils/__tests__/demo-balance.test.ts › auto-refills a stored balance that has no timestamp (legacy install)
0.2s	src/app/actions/__tests__/api-headers-extended.test.ts › should not include apiKey in validateInviteCode body

_{📍 Inline annotations are in the **Unit test report** check above. Coverage artifact: `coverage-unit`. Generated by `.github/workflows/tests.yml`.}

[Hugo0]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.