oliverbravery/PrintGuard v2.4.0

on GitHub

Added

• A plugin store, in the Plugins tab in Settings. Plugins are written in JavaScript and run in
  a sandbox, drawing a panel on your dashboard or running a job on the hub. Install verified
  ones from the catalogue, or from a GitHub repo or a zip.
  docs/plugins.md has the API, and CONTRIBUTING.md covers
  getting one listed.

• Each catalogue plugin has a page: an icon, screenshots or GIFs and its README, rendered the
  way GitHub renders it, with the permissions it will ask for and the author's reason for each.
  Everything is read from the plugin's repository at the pinned commit, so nothing new is
  installed or executed by looking. Installed plugins sit in the same list behind an
  Installed filter, a search box covers it all, every plugin's page opens from its card,
  and a plugin installed from a zip carries its page inside the zip.

• Four come as standard. Picture in picture floats a camera above your other windows, alert
  sounds plays a horn when a defect is caught, progress reports sends a tally of a print through
  your alert channels, and Spotify puts the current cover behind the dashboard.

• A five-page walkthrough on first load, covering what PrintGuard does, cameras and printers,
  monitors, and when inference runs and when it stands down. Each page carries a shot of the part
  of the dashboard it describes, as does the guide behind the ? in the header. It opens once in
  every browser that has not seen it.

• A Glass theme, alongside System, Light and Dark. The panels frost over whatever is behind
  them, which is what the Spotify plugin's cover shows through. It opens dark and as clear as
  the text can carry, and two sliders adjust how solid the panels are and how light or dark,
  with text taking whichever colour holds 4.5:1 over what the glass lets through.

• Plugins install switched off. Enable lists every permission with the author's reason for it,
  and it is all or nothing. An update that asks for more waits until you accept it.

• What you gave a plugin carries across updates from the repository it came from. A bundle that
  shares only its id starts with nothing.

• Enabling one shows what its code does against what it asks for. The catalogue is held to the
  same check, so a listed plugin is one whose code and claims agree.

• Plugins can reach the network on match patterns like https://*.example.com/*, hold a
  WebSocket open, and read what they fetch. Reaching your own network is a separate permission.

• Plugins can add printers, cameras and monitors, change settings and mint API tokens, each
  behind its own permission.

• Plugins can hold credentials they can never read back, and PrintGuard runs OAuth sign-ins on
  their behalf.

• Plugins can take camera stills and read risk history, each behind its own permission.

• A plugin can ship a panel.html and draw its own panel, with video and larger images. Panels
  drag, pin and hide with your monitors.

• Plugins can call each other on channels both sides declared.

• PRINTGUARD_PLUGINS=off starts the hub with every plugin switched off.

Fixed

• The walkthrough and guide screenshots show whole panels, where several stopped mid-slider or
  mid-list. Dialogs and the walkthrough pages also move with a softer ease.
• state.json is written readable only by the account running the hub. It holds printer
  passwords, notifier keys and API token hashes, and was taking the system default.
• A plugin's credentials are scrubbed from bug reports.
• A plugin's own pages can no longer pull a live camera stream.
• A camera that keeps dropping out no longer alerts on every reconnect. A recovery is announced
  once the feed has held for a minute, and each one doubles what the next has to hold for, up to
  fifteen minutes. Outages are never delayed. Worth pulling if you run a camera on marginal
  wifi. Thanks to @subpanel0576 for the report.
• The latest-intel image now carries Intel's current GPU runtime, covering Arc, Battlemage
  and every iGPU from Tiger Lake on. Debian's driver predates Meteor Lake, so OpenVINO was
  handed no GPU and inference quietly stayed on the CPU. Gen8 to Gen11 iGPUs stay on the CPU
  path, since Intel publishes no current driver for them.
• The compute readout names the hardware, so intel openvino now reads intel gpu or
  intel cpu, and the log lists what the providers offered at start.
• The Getting Started progress bar is visible in dark and Glass, where its track was taking a
  colour that all but vanished into the panel behind it.
• A monitor whose printer reports a state PrintGuard cannot read now warns and says so on its
  panel. It keeps watching, which is the safe direction, but only an unreachable printer warned
  before, so a printer stuck in something like OctoPrint's "Connecting" ran inference at the
  camera's full frame rate with nothing explaining why. A printer that starts reporting again
  is announced as recovered even if it comes back idle.