iOS: prepare privacy, metadata, and TestFlight release assets

[milind-soni]

Summary

• set the native app to version 1.0.0 / build 1 and Productivity category
• declare export compliance and embed an Apple privacy manifest
• add a public privacy policy and App Store privacy answers
• add polished en-US subtitle, keywords, description, promotional text, and release notes
• add App Review setup notes and a TestFlight-first release checklist
• add a Debug-only product-page fixture and a real 1320×2868 iPhone 6.9-inch simulator screenshot

Validation

• 84 CompanionCore Swift tests passed
• unsigned iOS simulator target built successfully
• built app contains PrivacyInfo.xcprivacy and StorePreview.json
• built Info.plist reports 1.0.0, build 1, Productivity, and no non-exempt encryption
• privacy manifest passes plutil validation
• metadata fields are within App Store character limits
• screenshot verified at 1320×2868

Still requires owner credentials

A TestFlight upload needs an enrolled Apple Developer team, ownership of the bundle ID, an App Store Connect app record, review contact details, and signing/API-key secrets. None are invented or committed here.

[coderabbitai]

Warning

Review limit reached

@milind-soni, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 minutes

Limit details: You’ve used all 3 included reviews currently available under your plan.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b62f9ea9-fcd4-406b-bb96-44f994cc1ed7

📥 Commits

Reviewing files that changed from the base of the PR and between 01ab295 and aae2ba1.

⛔ Files ignored due to path filters (1)

• ios/AppStore/screenshots/iPhone-6.9-roster.png is excluded by !**/*.png

📒 Files selected for processing (14)

• docs/ios-privacy.md
• ios/App/PrivacyInfo.xcprivacy
• ios/App/Session.swift
• ios/App/StorePreview.json
• ios/AppStore/RELEASE.md
• ios/AppStore/en-US/description.txt
• ios/AppStore/en-US/keywords.txt
• ios/AppStore/en-US/promotional_text.txt
• ios/AppStore/en-US/release_notes.txt
• ios/AppStore/en-US/subtitle.txt
• ios/AppStore/privacy-answers.md
• ios/AppStore/review-notes.md
• ios/AppStore/screenshots/README.md
• ios/project.yml

---

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