Open Config File works and every item is audited; Adwaita settings; shadow fix; onboarding extensions; arm64; cargo-deny; pinned actions

[hanthor]

Fixes #244, #245, #246, #247, #248, #249, #250, #251, #252, #253, #254.

Launcher and Settings

• Launcher window has a weird shadow along the bottom edge #251, the bottom-edge shadow. The card's shadow (16 px offset, 32 px blur) needed 48 px below the card, but the window has 24 px of padding. A full-height list left a hard band of alpha 29 on the window's last row. The shadow is now a 6 px offset with an 18 px blur, the window size is unchanged, and a const assertion checks that offset + blur ≤ padding. A new paint test, the_card_shadow_fades_out_before_every_edge, checks a short and a full-height card in light and dark. It fails with the old values on both wgpu and tiny-skia.

• Settings controls look out of place on GNOME #252, Adwaita-style Settings. A new compass_ui::adwaita module styles Settings, with every colour taken from the palette:

  • boxed lists with 12 px corners and separators
  • flat neutral buttons, with an accent "suggested" button
  • pill switches with a white knob
  • filled entries with a 2 px focus ring
  • button-like dropdowns
  • a neutral selection in the sidebar

  No behaviour changes.

Commands (#253, #254)

• Open Config File. Four separate failures:

  • there was no compass.json on a fresh profile, so it is now created first
  • GNOME's editors don't claim JSON, so text-like files now fall back to the text editor
  • terminal editors were started without a terminal
  • the engine acknowledged the open before launching, so failures only reached the log

  Opening now waits for the launch. If that fails it falls back to the OpenURI portal, which uses an fd and works from the Flatpak. Otherwise the launcher shows the reason and stays open.

• The other file commands. Show Log File used the pre-rename vicinae state dir. Open Default Config File wrote into the sandbox-private $XDG_RUNTIME_DIR. Both are fixed.

• Audit. 306 items are each run by app/tests/action_audit.rs, and any item that has no observable effect fails the test:

  • 59 builtin commands
  • 85 view-panel actions
  • 52 root-row actions
  • 104 Settings controls
  • 6 tray entries

  The inventory is generated into docs/rust-engine/ACTION-AUDIT.md. Dead items that were fixed: the three file commands, Show in File Browser, and the refusals of 19 power and media commands, which were drawn in a hidden window and now go to the HUD.

• Settings sweep. The Settings audit finds controls by clicking a grid. The unscrolled pass now rebuilds the simulator for every grid line, so earlier clicks no longer hide controls further down. Before this, the restyle had dropped Quick launch and the appearance preset from the inventory.

Onboarding (#248–#250)

• Onboarding 'Open Docs' button should open Compass docs on tunaos.org #248. "Open Docs" opens tunaos.org/docs/compass/getting-started#set-a-keyboard-shortcut, served from the new docs/getting-started.md. tunaos.org syncs top-level docs/*.md daily. The guide covers install, the shortcut setup for GNOME, KDE, Sway, Hyprland and niri, extensions, config paths, privacy and compass doctor, and was checked against the code.
• Onboarding 'Setup complete' page links to vicinaehq instead of Compass #249. Every button on the last step goes to Compass, and a Simulator test asserts that none of them leads to Vicinae. There is no Sponsor button in onboarding; the tray still has "Sponsor Upstream Vicinae".
• Onboarding should recommend extensions to enable #250. A new "Add extensions" step recommends five extensions, all of which render in Suite 1 and need no account: Bluetooth, Wifi Commander, Process Manager, Flathub and Google Translate. Installing uses the store's own install path. When the install fails, for example offline, the button says "Try Again" with the store's reason, and Continue still works. The onboarding version was not bumped, so people who have already finished setup don't see it again.
• Links. The remaining links to docs.vicinae.com either point at the guide or say they lead to the Vicinae SDK docs.

CI and supply chain

• [Feature] Publish aarch64/arm64 builds #246, aarch64. flatpak.yaml builds and smoke-tests on both ubuntu-24.04 and ubuntu-24.04-arm. publish-flatpak.yaml exports both bundles, checks each image's config architecture, pushes latest-x86_64, latest-aarch64 and latest, and updates the index once per arch. The build checks are renamed build (x86_64) and build (aarch64).
• [sec-check] Missing cargo-deny configuration for supply chain security #244, cargo-deny. A new deny.toml plus a CI job that runs on dependency changes and daily. The results:
  • no vulnerabilities
  • five unmaintained crates, each pulled in through Iced, syntect or rhai with no upgrade available, ignored with a reason
  • yoke-derive 0.8.3 was yanked, so it is bumped and the cargo sources are regenerated
• [sec-check] GitHub Actions use unpinned version tags instead of commit SHAs #245, [sec-check] GitHub Actions not pinned to commit SHAs #247, pinned actions. 92 third-party uses: are pinned to SHAs taken from git ls-remote. The org's own publish-flatpak-index@main stays unpinned so org-wide fixes still reach this repo. A new dependabot.yml keeps the pins updated.

Verification

• Local checks: cargo fmt, workspace clippy with -D warnings, and cargo doc with -D warnings all pass.
• Tests: cargo test --workspace passes, with 4,690 passing before the audit fix. The compass-ui suite passes after it, 576 of 576.
• Extension tests: the engine e2e suite passes with a freshly built extension runtime (98/98, including Brew).
• Parity: the score stays at 152/152. cargo deny check passes, and actionlint reports nothing new.

Visual checks, all looked at:

• Paint tier: before and after for the shadow and every Settings page, in light and dark.
• Real binary on headless Sway: Settings in light and dark, plus a 4x zoom of the shadow edge.
• Onboarding on headless Sway: each step, a real store install, and the offline retry.
• Open Config File on headless Sway: opening the config, the log and the default config with a fake editor, and the "No application opens this kind of file" case.

Only CI can show that the aarch64 build and its smoke tests work.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UtGVEzDmYTdpsuEQErmmLn

---

Generated by Claude Code