docs: update README install steps (xcbeautify and init submodules)

[Rezisn]

Summary

• Clarify xcbeautify as a required dependency for building devicekit-ios.
• Ensure git submodules are initialized during setup (required for Opus).
• Updated Quick Start step to include parameters for device.screenshot.

[coderabbitai]

Walkthrough

The README documentation has been updated in two areas. The "Building from Source" section now includes explicit instructions to install the xcbeautify dependency via Homebrew and to initialize git submodules using git submodule update --init --recursive. In the "Quick Start" section, the example JSON-RPC request for device.screenshot was modified to pass format: "jpg" as a parameter instead of using an empty parameters object, with corresponding adjustments to the curl command output formatting.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main changes: updating README documentation with xcbeautify dependency and git submodule initialization instructions.
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	The pull request description directly aligns with the changeset, clearly documenting the three main updates: clarifying xcbeautify as a dependency, adding git submodule initialization, and updating the device.screenshot example.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 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 `@README.md`:
- Around line 83-86: The description for the device.screenshot example is
inconsistent: the JSON-RPC call sets "format": "jpg" but the text says it
returns a PNG; update the README so they match by either changing the params in
the example (the JSON string for method "device.screenshot" and params "format")
to "png" or change the descriptive sentence to state it returns a base64-encoded
JPEG; ensure references to "device.screenshot" and the "format" param are
updated accordingly.

🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b096ac97-f8d4-41ce-a068-45e5ba36bbc0

📥 Commits

Reviewing files that changed from the base of the PR and between 9562f3a and b5cf1ef.

📒 Files selected for processing (1)

• README.md

[Rezisn]

found that current implementation of device.screenshot (here) set format as mandatory parameters.