Roll out real device screenshots across the Edge Component docs

[lessevv]

Summary

• Adds docs:capture-screenshots, which drives a local super-native checkout via native:run/native:screenshot to regenerate every Edge Component doc screenshot from real iOS/Android devices, with --crop/--crop-percent/--crop-offset to trim OS chrome and a --dry-run/--publish flow
• Wires real device screenshots into 18 Edge Component docs pages (top-bar, bottom-nav, side-nav, bottom-sheet, modal, menus, list, refreshable, virtual-list, slider, toggle, checkbox, select, radio-group, web-view, gesture-area, tab-row, text), tracked in a DocsScreenshotManifest for future regeneration
• Fixes the device-chrome mockup (<x-docs.edge-preview>): adds a live clock, switches the Dynamic Island/camera cutout and home indicator to percentage-based sizing so they scale with the screenshot instead of a fixed pixel size, and adds sidebarWidthIos/sidebarWidthAndroid props so the fake status/home-indicator bars can match a partial-width drawer's dimming scrim
• Fixes a browser layout bug where pairing a percentage width with aspect-square on the Android bottom-nav icons made the fake chrome bar's shrink-to-fit width diverge from the actual screenshot width

Test plan

• php artisan test --filter=Docs passes (95 tests)
• Pint passes
• Manually verified rendering (both platforms, light/dark, mobile/desktop viewports) in-browser for every newly-wired page

🤖 Generated with Claude Code

[shanerbaner82]

Eyes @simonhamp - I think the idea is great but I don't believe it should belong here, let's discuss

[simonhamp]

@shanerbaner82 where should it live if not here? The command should be able to run inside of a GH Action or anywhere else - feels very flexible

My only issue is that it's using the super-native repo which is a bit of a mess and more of a scratchpad. It's not really ideal for a polished set of images for the docs. I'd really like a repo dedicated to presenting the components cleanly. That would also make the source references cleaner

But this is a great start imo.

I have a feeling that in its current form though, it would break how the interactive demos work in the Jump app

[simonhamp]

I pushed a commit to this branch. The docs API (used by Jump and MCP clients) strips Blade components from page content, but its self-closing tag rule couldn't match a tag with a / inside it. Every <x-docs.edge-preview> has one in source, so the tag survived on 18 pages and Jump showed the attribute lines as a paragraph under Overview.

stripBladeComponents() now handles slashes, bound attributes and multi-line tags, and runs the self-closing rule before the paired one. Tests are in DocsMcpServerPageTest.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 83295771-4e82-4493-9b82-853a633dcca4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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