feat(androidtv): add Projectivy deployment helper

[bakerboy448]

Summary

• add a generic Projectivy deployment helper for host or containerized ADB
• use the verified Projectivy package and launcher component
• add checksum-pinned Android TV app fleet sync with downgrade protection
• audit Play-managed packages without sideloading over them
• identify offline and unauthorized ADB states with bounded timeouts
• document persistent ADB-key and manifest conventions

Intended fleet split

• Play-managed/audited: Projectivy, Plex, YouTube TV, and SeerrTV on Shield/Google TV
• pinned sideload: SmartTube and SeerrTV on Amazon Fire TV

Validation

• mocked host and container ADB paths for the Projectivy helper
• missing-APK failure handling
• repository pre-commit hooks, ShellCheck, shfmt, and CI

No site-specific hosts, credentials, endpoints, or secrets are included. The existing authoritative infrastructure source remains unchanged.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 54 minutes

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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: a6b01ace-b270-4e90-ba6d-08a0648a89a4

📥 Commits

Reviewing files that changed from the base of the PR and between 1dccf15 and 60fdfff.

📒 Files selected for processing (4)

• CLAUDE.md
• README.md
• androidtv-app-sync.sh
• projectivy-deploy.sh

Walkthrough

Adds projectivy-deploy.sh, an ADB-based Android TV installer/configurator supporting launcher-only mode, backup, restore, and default-home configuration. README and CLAUDE.md contents lists now document the script.

Changes

Projectivy deployment

Layer / File(s)	Summary
CLI and ADB setup projectivy-deploy.sh, README.md, CLAUDE.md	The script parses deployment options, selects Docker or host ADB, connects to the Android TV device, and cleans up the connection; repository contents lists document the script.
Projectivy installation and validation projectivy-deploy.sh	The script optionally installs the APK and verifies the Projectivy package when required.
Backup, restore, and launcher configuration projectivy-deploy.sh	The script supports TV-confirmed restore, backup creation, and setting Projectivy as the default home activity.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Operator
  participant projectivy_deploy_sh
  participant ADB
  participant Android_TV
  Operator->>projectivy_deploy_sh: Select install, restore, backup, or launcher-only mode
  projectivy_deploy_sh->>ADB: Resolve and invoke adb
  ADB->>Android_TV: Connect and wait for device
  projectivy_deploy_sh->>Android_TV: Install or validate Projectivy
  projectivy_deploy_sh->>Android_TV: Perform backup or restore when requested
  projectivy_deploy_sh->>Android_TV: Set Projectivy as default home activity
  Android_TV-->>Operator: Launcher is available from Home

Loading

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The summary is solid, but it omits the required Script(s) affected section and the checklist items from the template.	Add the Script(s) affected section with the new file, and include the checklist items for shellcheck, target OS testing, secrets, and README updates.

✅ Passed checks (4 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.
Title check	✅ Passed	The title clearly matches the main change: adding a Projectivy deployment helper for Android TV.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/projectivy-deploy

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@projectivy-deploy.sh`:
- Line 9: Replace the site-specific default in projectivy-deploy.sh at lines 9-9
with a generic ADB container name, and update the description at lines 3-3 and
EOF help text at lines 16-16 to reference the same new default.
- Around line 42-45: Update the containerized `adb_cmd` flow so host paths are
not passed directly to `docker exec`: copy `$APK_PATH` and `$RESTORE_PATH` into
a temporary container directory before install/restore, and copy the backup
produced by `adb backup` back to `$BACKUP_PATH` before the existing size check.
Apply this only when using the `ADB_CONTAINER` branch while preserving direct
host-path behavior for local adb execution.
- Line 96: Replace the GNU-specific stat invocation in the backup-size printf
with a POSIX-compatible wc -c approach, preserving the existing “missing”
fallback when the backup file cannot be read.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: d1cf3d89-8f58-4909-aece-ce07013f8bd3

📥 Commits

Reviewing files that changed from the base of the PR and between 30729dd and 1dccf15.

📒 Files selected for processing (3)

• CLAUDE.md
• README.md
• projectivy-deploy.sh

All three findings were addressed in commit 60fdfff: generic container default, host/container file staging, and portable backup sizing.