Front-panel status strip for the browser page

[LinuxJedi]

Summary

The browser build had no drive or power feedback. This adds a status strip below the canvas on the /try page with the same front-panel readouts as the desktop status bar:

• PWR and FDD LEDs (HDD/CD LEDs appear only on machines fitted with those drives), using the desktop bar's exact LED palette.
• Three-digit floppy track counter, latching the last track like the desktop bar so it does not flicker back to --- between accesses.
• Inserted disk name per connected drive (DF0: name.adf), with ellipsis + hover tooltip for long names.

No controls -- the page already has insert/eject/volume -- and the strip only appears once a machine boots.

How

• WebEmu gains flat scalar getters wrapping the core's existing Bus::front_panel_status() snapshot: power_led(), fdd_led(), fdd_track(), hdd_led(), cd_led(), drive_connected(n), disk_name(n). Option returns map to undefined in JS (no drive selected / hardware absent / drive empty).
• try.js builds the strip lazily like the fullscreen UI. LEDs and the track counter poll every animation frame with change guards (steady frames do no DOM writes); disk names refresh at the 1 Hz stat tick and immediately on insert, eject and boot.
• Optional page-shell hook: a #ledbar element hosts the strip and the page owns its layout; without one the strip inserts itself after the canvas shell, so the hosted page works with no markup change.
• Docs: new getters in the WebEmu embedding API section, #ledbar in the page-shell hooks list, and a mention in the hosted-page section of docs/guide/browser.md.

Also fixes a pre-existing rustfmt drift in the web crate and adds a cargo fmt --check step for it to the wasm CI job -- the crate is a standalone workspace, so the root Formatting step never reached it.

Testing

• cargo check --target wasm32-unknown-unknown --locked and cargo clippy clean; cargo fmt --check now clean on the web crate.
• Rebuilt pkg/ with wasm-bindgen 0.2.126 and confirmed the generated .d.ts signatures (fdd_track(): number | undefined, disk_name(drive: number): string | undefined, ...).
• Drove the unchanged production try/index.html locally in Chrome: booted AROS with a ?df0= disk queued and watched PWR light red, the FDD LED go amber during the disk load and off after, the track counter step --- -> 000 -> 001 and hold, the disk name appear at boot, and Eject clear it synchronously. HDD/CD rows stay hidden on the A500, no console errors, and the #ledbar host path renders into a page-provided element without creating the fallback strip.

[Copilot]

Pull request overview

Adds a front-panel style status strip to the browser /try page, bringing the web demo closer to the desktop frontend by exposing and rendering core “front panel” state (LEDs, floppy track, and inserted disk labels) once a machine is running.

Changes:

• Extend WebEmu’s wasm API with front-panel status getters (power/FDD/HDD/CD LEDs, selected floppy track, drive connectivity, and disk names).
• Build and update a DOM status strip in try.js (per-frame LED/track updates; 1 Hz + event-driven disk label refresh; optional #ledbar host element).
• Update browser docs and tighten CI by adding cargo fmt --check for the standalone web workspace.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
docs/guide/browser.md	Documents the new status strip behavior, new embedding API getters, and the optional #ledbar hook.
crates/copperline-web/www/try.js	Implements the front-panel status strip UI and hooks it into boot/tick/insert/eject flows.
crates/copperline-web/src/lib.rs	Adds wasm-exposed WebEmu getters wrapping the core front_panel_status() snapshot and floppy metadata.
.github/workflows/ci.yml	Ensures rustfmt is available and enforces formatting for the web crate workspace in CI.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.