Verify snap GSettings schema precompile on next snap rebuild (F1 follow-up)

[edonahue]

Context

PR #27 added a GSettings schema precompile step to snap/snapcraft.yaml (glib-compile-schemas in override-prime, guarded best-effort) to address the repeated GLib schema symlink/compile warnings on first snap launch.

This change could not be verified in CI — the snap runtime isn't reproducible in the build environment, so it was scoped as the only low-risk, additive change to the live auto-publishing snap.

What to verify

On the next snap build/publish:

1. Build the snap (or let snap_publish.yml publish on the next v* tag).
2. Run snap run spinner-for-discogs from a terminal.
3. Confirm the repeated GLib schema symlink / compile warnings are gone.

Notes

• The residual libproxy / COSMIC dconf / IM-module warnings originate in the host desktop environment and are not fixable from the package — those remain expected cosmetic noise.
• If the schema warnings persist, the next steps are documented in docs/STORE_SUBMISSIONS.md → "Channel 4: Snap Store" (Current status + Future Snap polish goals).

Tracking issue created as a follow-up to the FTUX polish PR (#27).

[edonahue]

Build-verified — awaiting runtime confirmation.

Triggered snap_publish.yml on main (commit 20f54f9, which includes the schema-precompile change from #27). The run completed green:

• Build snap ✅ — the new glib-compile-schemas override-prime step + the libglib2.0-bin build-package built cleanly (this is the part that had never been built before).
• Publish to stable ✅ — the fix is now live on the Snap Store stable channel.

Run: https://github.com/edonahue/Discogs_Spinner/actions/runs/28311881614

So the build-time half of this fix is confirmed working. The remaining step is the runtime check on a Linux desktop:

sudo snap refresh spinner-for-discogs
snap run spinner-for-discogs 2>&1 | grep -i 'schema\|gsettings'

If the repeated GLib schema symlink/compile warnings are gone, this can be closed. The residual libproxy / COSMIC dconf / IM-module messages originate in the host desktop and are expected to remain.

---

Generated by Claude Code