docs: clarify custom launcher execution policy

[wizzomafizzo]

Warn users that installing a custom launcher authorizes programs and scripts to run as Core’s user. Explain that configured controls no longer require allow_execute, while direct scripts and existing restrictions remain unchanged.

Next-only: documents unreleased Core behavior; stable docs stay unchanged.

Companion to ZaparooProject/zaparoo-core#1458.

Summary by CodeRabbit

• Documentation
  • Added a security warning explaining that custom launchers run with Zaparoo Core’s permissions and do not require allow_execute approval.
  • Clarified execute-command authorization for configured control scripts.
  • Documented that direct token and Run API commands still require allowlist approval, configured controls respect block_commands, and remotely fetched ZapScript cannot bypass execution restrictions.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 3812adab-4e29-4eed-a906-0c0e968acd01

📥 Commits

Reviewing files that changed from the base of the PR and between d5dd0a8 and 5f738f1.

📒 Files selected for processing (1)

• docs/features/custom-launchers.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The custom launcher documentation adds a warning about launcher permissions and clarifies allow_execute behavior for configured controls, tokens, the run API, block_commands, and remotely fetched ZapScript.

Changes

Custom launcher security documentation

Layer / File(s)	Summary
Execution security guidance docs/features/custom-launchers.md	Adds a warning that custom launcher files run with Zaparoo Core permissions and do not require allow_execute approval. Clarifies execution rules for configured controls, direct token or run API commands, block_commands, and remotely fetched ZapScript.

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

Merge Risk: ⚪ Minimal · up to 5f738

The documentation now explains that custom launchers run with Core permissions and clarifies execution-control behavior without changing runtime code. No merge-blocking risk remains.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the documentation change to the custom launcher execution policy.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

---

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.}