Skip to content

Visual workflows, public-release work, and the remaining roadmap gaps - #6

Merged
vman26 merged 26 commits into
developfrom
claude/workflows-release
Nov 15, 2026
Merged

vman26 merged 26 commits into
developfrom
claude/workflows-release

Conversation

@vman26

@vman26 vman26 commented Nov 13, 2026 •

Copy link
Copy Markdown
Owner

This adds a visual workflow editor, the public-release pieces, most of the remaining roadmap gaps, support for generic USB devices with a device creator, firmware updates in the device plugin API, and running DeckHost plugins in their own process. It is stacked on #5 (Elgato and Web Deck), which is stacked on #4.

Visual workflows (roadmap phase 4)

  • What a control does, as nodes linked on a canvas. Drop Workflow on a control, or use Turn into a workflow… in its editor, then Open workflow editor.
  • Node types:
    • When: pressed, released, tapped, double pressed, held, turned or swiped. A workflow can have several.
    • Action, Wait, Toggle, Repeat, Stop.
    • If: checks a variable, the app in front, or the time of day.
    • Set variable.
  • Engine (Core/Workflows/WorkflowEngine):
    • Runs on the host worker, with a work queue per run.
    • Waits are scheduled, so the device never blocks.
    • An output with several links runs them side by side.
    • A step limit guards against runaway runs.
  • While a run is going, a second input can start another run, be ignored, restart the run, or stop it.
  • Live trace: the editor lights up each step as it runs and keeps a run log.
  • Editor: canvas, inspector, undo/redo, Arrange, Fit, Run, Stop. Links that would form a loop are refused.
  • Conversion: Multi Action, Multi Action Switch, Key Logic and plain actions convert into a workflow that does the same.

DeckHost plugins in their own process (default on)

  • How a plugin runs: DeckHost starts itself with --plugin-host <port> <token> <folder> (no window) for each installed DeckHost plugin.
    • The process loads the package and connects back over loopback TCP, proving itself with a one-time token.
    • It then describes its actions. Messages are JSON lines (Core/Plugins/Isolation).
  • Stand-ins inside DeckHost (IsolatedApplicationPlugin, IsolatedDeckAction), so neither the rest of DeckHost nor the plugins change:
    • Execute, OnAppear and OnDisappear are sent without waiting.
    • Render replays the action's last drawing, recorded in the plugin process as a display list. It asks for a new one when what the action draws from changes (settings, size, the control's variables), when the plugin calls RequestRender, and at the action's refresh interval. When the new drawing arrives the device is redrawn.
    • Published variables (strings, numbers, booleans, times) and IActionHost calls are forwarded to DeckHost.
  • Crashes and hangs:
    • Pings every 5 s detect a hung process.
    • A process that ends or stops answering is restarted after 1, 3 and 10 s, and told again what's on the devices.
    • After that the plugin stays stopped, with a message on the Plugins page.
  • Opt-out per plugin: Plugins page → Run in its own process (on by default).
    • Turning it off shows a warning first: inside DeckHost, a crash or hang takes DeckHost and the devices with it.
    • The choice is kept in plugins/state.json.
    • System plugins stay inside DeckHost; Stream Deck plugins were always separate.
  • Stream Deck / OpenAction plugins (always their own program) now get the same restarts (StreamDeckRuntime):
    • When the program ends unexpectedly, it's restarted after 1, 3 and 10 s.
    • Messages meant for the dead process are dropped, and on reconnect the plugin is sent willAppear again for everything visible, so its keys come back.
    • After three restarts in a row it stays stopped with a message. A process that ran for 5 minutes starts the count again.
    • The Plugins page shows each plugin's process and status.
    • Their protocol has no ping, so a hung Stream Deck plugin isn't detected; it only stops updating its own keys.
  • ADR 0007 is rewritten for this. Developer notes are in docs/maintainers/plugins.md.

Generic USB devices and the device creator

  • DeckHost.Device.Hid turns a device description into a deck. A description is a JSON file in devices/hid/<id>.json holding:
    • The vendor and product id, and optionally the HID interface (by usage page).
    • Each key or knob's place on the layout.
    • Where each control shows up in the input reports: a bit, a value, steps or a position. A knob can also have a push.
  • Plugin behavior:
    • Devices are listed while unplugged and opened when plugged in.
    • Keys get long-press.
    • Input only: these devices have no screens or lights DeckHost can drive.
  • Device creator (☰ → Add a USB device):
    • Lists the HID interfaces on the computer and shows the reports of the picked one.
    • Add key, Add knob and Learn push work out each control from pressing or turning it (HidLearner, which ignores bits that change by themselves).
    • A key that was already added is recognized. Controls light up live as they are pressed.
    • Controls are dragged into place, or placed in rows with Arrange. They are numbered by position, so LayoutMapper can copy profiles between devices.
    • Save, Edit and Remove. On Linux the page shows the device rule to install.
  • Limits are in the docs and ADR 0008:
    • Windows doesn't let any program read keyboard or mouse interfaces; many macro pads have a vendor-defined interface that works.
    • A device that types keys keeps typing them.

Firmware updates in the device plugin API

  • IDeviceFirmware (an optional interface in Contracts) lets a device plugin:
    • Report the version.
    • Check the maker's server for a newer release (FirmwareRelease, carrying its SHA-256).
    • Install an image, with progress.
    • The check and install methods are default members, so a plugin can implement only the version.
  • Core/Firmware/FirmwareService gives every plugin the same safety:
    • Only connected devices, and one update at a time.
    • HTTPS downloads only, and they must match their SHA-256. A release without a checksum is refused.
    • The device is paused in the host while the plugin writes: no images, lights or input reach it (IDeviceHostService.SetDevicePaused).
    • Afterwards the device is redrawn.
  • Device settings → Firmware: shows the version; when the plugin can install, offers check, install from a release or a file, a confirmation and progress.
  • Today's plugins only report versions:
    • MiraBox: the SDK reads it but has no way to write firmware.
    • Elgato: the version is now read through a feature report; the update protocol isn't public.
    • Generic USB devices: their USB release number.
  • See ADR 0009.

Public release

  • Welcome tour on the first start.
  • Opt-in crash reports: saved locally, and offered as a pre-filled GitHub issue on the next start. Nothing is sent by itself.
  • Help and support:
    • Documentation link.
    • Report a problem.
    • Support bundle.
    • A per-device Devices card: inputs received, images sent, failures and the last error.
  • Documentation site (MkDocs, docs.yml), published to the releases repo's GitHub Pages.

Signing

  • Windows, either path (both optional; without them, packages build unsigned as before):
    • Azure Artifact Signing via azure/artifact-signing-action@v2. scripts/setup-azure-signing.sh sets up the account, certificate profile and a signing-only app, and stores the variables and secrets.
    • A .pfx certificate.
  • macOS: Developer ID plus notarization.
  • Build provenance attestations for public source repositories.
  • Options and eligibility are described in docs/maintainers/releasing.md.

Problem reports between the public and private repositories

  • sync-issues.yml and scripts/sync-issues.py:
    • New issues in the public releases repo get a copy here, labeled public-report, and comments follow.
    • A /public <text> comment here is posted there.
    • Closing the copy as completed closes the public issue with a thank-you.
  • Issue forms for the releases repo are in packaging/releases-repo/.

Remaining gaps

  • Architecture tests:
    • The dependency rule is checked on the built assemblies.
    • A plugin API baseline (ContractsApi.txt): removals, changes and interface members without a body fail unless CurrentHostApiVersion is bumped.
  • Decision records: nine ADRs, plus an architecture page with third-party packages and licenses.
  • Profile migrations:
    • Versioned steps on the JSON tree, with a backup before migrating.
    • A file written by a newer DeckHost is backed up before this version saves over it.
  • Stream Deck first edition and Mini: BMP key images, the older report layout, and key numbering from the right on the first edition.
  • Plugins:
    • permissions in plugin.json, shown when installing and on the Plugins page.
    • PluginDiagnostics, also as DeckHost --check-plugin <zip|folder>.
    • Updates keep the previous version, with Back to v… to roll back.
  • Undo/redo in the main editor:
    • Drops, moves and swaps, removes, editor edits and workflows.
    • Quick edits merge into one step.
    • Header arrows and Ctrl+Z / Ctrl+Y.
  • Themes: Dark, Light, or Same as the system.
  • Copy a profile to another device (LayoutMapper):
    • Keys keep their row and column where they fit; the rest go onto added pages.
    • Importing a profile made for another device uses the same mapping.

Not done:

  • A real sandbox (lower rights per plugin process). Permissions are still declarations.
  • Publisher verification and package signing.
  • Plugin dependencies.
  • An own store backend.

Tests

  • All 600 tests pass on Linux.
  • Plugin process tests run the real OBS plugin through the protocol, with the plugin process simulated in the test process:
    • Its actions are described.
    • The first render asks for a drawing, and the device is redrawn when it arrives.
    • A press publishes the plugin's connection error, which reaches DeckHost's variables, and the next drawing shows it.
    • A killed process is restarted and draws again.
    • Moving a plugin inside DeckHost and back is remembered.
  • Stream Deck plugin tests with real Node.js plugin processes:
    • A killed plugin is restarted and draws its key again, showing the new process id.
    • A plugin that exits right away is stopped after three restarts, with a message; disabling and enabling it starts it fresh.
  • Checked with real processes, using the built DeckHost.App as the plugin host:
    • Install took 0.7 s, including a trial process.
    • The first drawing came back in 27 ms.
    • A killed process was restarted after 1 s.
    • Moving the plugin inside DeckHost left no processes behind.
  • Checked headless:
    • The workflow editor and the welcome tour.
    • Undo/redo.
    • Light and dark themes.
    • Copying a profile from an N4 Pro to a Mini.
    • --check-plugin on the OBS package.
    • The device creator.
    • A saved USB device in the main editor.
    • The Firmware card.
    • The Plugins page with the process setting and its warning.
  • sync-issues.py was tested against a fake GitHub API.
  • Untested:
    • Signing: no certificates or Azure account here.
    • Docs publishing.
    • The issue sync against real repos.
    • On hardware: the first-edition Stream Deck and the Mini, generic USB devices, and the Stream Deck firmware version read.
    • Plugin processes on Windows and macOS: only Linux here.
  • CI: earlier PRs' Actions jobs failed without a runner (billing/minutes), so CI may not run here until that's fixed.

🤖 Generated with Claude Code

https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi

@vman26 vman26 changed the title Visual workflows, welcome tour, crash reports, signing and docs Visual workflows, public-release work, and the remaining roadmap gaps Nov 13, 2026
@vman26
vman26 added this pull request to stack #3 November 15, 2026 11:51
@vman26
vman26 force-pushed the claude/workflows-release branch from 62d812f to de8fe8a Compare November 15, 2026 11:55
Base automatically changed from claude/elgato-hardware to develop November 15, 2026 11:56
A control can now run a workflow: nodes linked on a canvas. What starts it
(pressed, released, tapped, double pressed, held, turned or swiped), actions,
waits, If (a variable, the app in front, the time of day), toggles, repeats,
variables and Stop. Runs never block the device, can be ignored, restarted
or stopped while they wait, and light up node by node in the editor with a
run log. Multi Action, Multi Action Switch, Key Logic and plain actions turn
into a workflow that does the same. The editor has undo/redo, arrange, fit,
run and stop; a Show Variable action shows a workflow variable on a key.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
The knob's name and action are in its tooltip and the editor below.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
- First start opens a welcome tour: the devices found (with what to do when
  none is), a starter layout for empty controls, start at sign-in, update
  checks and crash-report offers, and how the editor works. The menu opens
  it again.
- A crash writes a report on this computer (home folder and user name
  replaced). The next start opens Help and support, which offers to report
  it as a pre-filled GitHub issue the user reads and submits. Nothing is sent
  by itself; the offer can be turned off.
- Help and support: the documentation, Report a problem, a support bundle
  (recent logs, crash reports, settings, plugin list, a summary; profiles
  only when asked, since actions keep passwords there), and the log folder.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
- release.yml signs when certificates are added as secrets: Windows with
  signtool (DeckHost's exe and libraries before packaging, the setup after),
  macOS with a Developer ID for the hardened runtime, then notarized and
  stapled. Without the secrets nothing changes.
- docs/ is the user documentation (getting started, devices, the editor,
  profiles, Multi Action and Key Logic, workflows, lights, plugins, updates,
  troubleshooting, privacy) plus maintainer pages (releasing and signing,
  writing plugins), built with MkDocs. The docs workflow checks it on pull
  requests and publishes it to the releases repository's GitHub Pages, where
  DeckHost's Help links.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
…, and build provenance

The release workflow signs with Azure Artifact Signing when its variables and
secrets are set (Microsoft issues and renews the certificates), next to the
certificate-file path. scripts/setup-azure-signing.sh creates the account,
certificate profile and a signing-only app and stores the settings in the
repository. Public source repositories also get build provenance attestations.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
The sync issues workflow copies new issues and comments from the public
releases repository into this one, posts /public comments back and closes a
report when its copy is closed as completed. Issue forms and a README for the
releases repository are in packaging/releases-repo.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
…ile migrations

ArchitectureTests check the dependency rule on the built assemblies and compare
the public Contracts surface with ContractsApi.txt: removals, changes and
interface members without a body fail unless the host API version is bumped.
docs/maintainers has an architecture page with the third-party packages and
seven decision records.

Profiles carry a format version: ProfileMigrations upgrades older files step by
step on the JSON tree (with a backup first), and a file from a newer DeckHost
is copied to the backups before this version saves over it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
Both use the older protocol: BMP key images (turned 180° on the first edition,
mirrored on the diagonal on the Mini) in padded reports, keys numbered from the
right on the first edition, other brightness and reset reports, and one input
byte per key. Written from the protocol; not tested on hardware yet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
plugin.json can declare what a plugin does (network, starting programs, files,
input, system settings, clipboard); the Plugins page and the install message
show it. PluginDiagnostics checks a package without loading it, shows warnings
for installed plugins and backs DeckHost --check-plugin, which also trial-loads
the plugin for its author. An update keeps the previous version, and Back to v...
on the Plugins page swaps them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
Every change to what a control does (drops, moves and swaps, removes, the
editor below the device, workflows) is recorded with the binding before and
after. Quick edits of one control merge into one step, a move or swap is one
step. Header arrows and Ctrl+Z / Ctrl+Y (Cmd on macOS) outside text boxes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
The views' colors are theme resources (Themes/Colors.axaml, a dark and a light
value per color), so DeckHost settings -> Look switches between dark, light and
the system's choice at once. Disabled header buttons are dimmed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
LayoutMapper moves a profile onto another device's controls: keys keep their
row and column where they fit, the rest go onto added pages, dials and touch
zones the device lacks are left out. Profiles -> Copy to uses it, and so does
importing a profile made for another device.

The host counts per device the inputs it received, images sent, failures and
the last error. Help and support shows them (Devices) and the support bundle
includes them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
DeckHost.Device.Hid turns user-written device descriptions into decks: vendor
and product id, the HID interface, each key or knob's place on the layout and
where it shows up in the input reports (a bit, a value, steps or a position).
Devices are listed while unplugged and opened when plugged in; input only.

The device creator (menu: Add a USB device) lists the HID interfaces, shows
what the picked one sends, learns each key, knob and knob push from pressing
and turning it (bytes that change by themselves are ignored), lights controls
up live, lets them be dragged into place, numbers them by position and saves
the device. On Linux it shows the device rule to install.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
Device plugins can implement IDeviceFirmware: report the version, check the
maker's server for a newer release and write an image. FirmwareService does
the rest the same way for every plugin: connected devices only, one update at
a time, HTTPS downloads that must match the release's SHA-256, and the device
paused in the host (no images, lights or input) while the plugin writes, then
redrawn. Device settings gets a Firmware card with the version, update check,
install from a release or a file, a confirmation and progress.

The N4 Pro, Stream Decks (now read through their feature report) and generic
USB devices report their version only: none of them has an update protocol
DeckHost can use.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
DeckHost starts itself with --plugin-host for each installed DeckHost plugin;
the process loads the package, connects back over a loopback socket with a
one-time token and describes its actions. DeckHost uses stand-ins for the
plugin and its actions, so nothing else changes and plugins need no changes:
calls are sent without waiting, Render replays the action's last drawing
(recorded as a display list in the plugin process) and asks for a new one when
what it draws from changed, published variables and host calls come back. A
process that ends or stops answering is restarted (1, 3, 10 s) and told what's
on the devices; after that the plugin stays stopped with a message.

The Plugins page has Run in its own process per plugin, on by default; turning
it off shows a warning first. The choice is kept in plugins/state.json.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
When a Stream Deck / OpenAction plugin's program ends without DeckHost
stopping it, the runtime drops the messages meant for it, starts it again
after 1, 3 and 10 seconds and, once it registers, sends willAppear for
everything it had on the devices, so its keys come back. After three restarts
in a row it stays stopped with a message; a process that ran five minutes
starts the count again. The Plugins page shows each plugin's process and
status.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
…lugin safety

The first step mentions devices taught through the device creator and opens
it; the preferences have the theme; the tips cover undo/redo, copying a
profile to another device, plugins running in their own process, and Device
settings / Help and support.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
DeckHost is now GPL-3.0-or-later. DeckHost.Contracts and the plugin template
stay MIT, and NOTICE.md adds a section 7 permission for plugins and platform
libraries (WebView2, OS and vendor SDKs), so plugins can use any license,
free or paid.

The store reads the official DeckHost catalog (the deckhost-plugins
repository's GitHub Pages) before the user's own sources; while it doesn't
exist it's simply empty. Catalog entries can carry a sha256 (a download that
doesn't match is refused), the plugin's permissions (shown in the store) and,
for paid plugins, a purchase_url and price (Buy opens the page).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
…s, references, catalog repo

- README: what DeckHost is now, how it's made (with an AI coding assistant,
  reviewed and tested by its developer), contributing, GPL license; badges
  point at this repository.
- CONTRIBUTING (incl. AI-assisted contributions), SECURITY, CODE_OF_CONDUCT,
  issue forms, PR template, FUNDING (Buy me a coffee).
- Docs: a full plugin guide, a device plugin guide, generated references for
  the built-in actions and the plugin API (ReferenceDocsTests keeps them in
  sync), the plugin catalog guide, a going-public checklist with an
  announcement draft, ADR 0010 on the license; releasing assumes one public
  repository with the private route as an option.
- packaging/plugins-repo: everything for vman26/deckhost-plugins (README for
  authors, the OBS entry, a checker that validates entries and packages and
  builds catalog.json, PR checks with DeckHost --check-plugin, Pages publish).
- The release publishes deckhost.plugin.obs.zip for the catalog.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
…1 always shown

- The Web Deck page opens without a code and asks for the pairing code (and the PIN when set),
  remembers them on the device, takes ?code= from a link and removes it from the address bar,
  and asks again when the code or PIN changes in DeckHost.
- Pairing codes are short (XXXX-XXXX, no look-alike characters); case, spaces and dashes don't matter.
- Optional PIN; five wrong tries from one address within a minute make it wait.
- Device plugins can add buttons to Device settings (IDeviceSettingActions, with an optional
  confirmation); the Web Deck uses it for New pairing code, which disconnects every phone.
- The page bar always shows page 1 next to +.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
The window reused an open device settings page whatever device it belonged
to, so opening the Web Deck's settings could show the N4 Pro's page (with
its MiraBox firmware note). Now the open page is shown again only for the
same device; another device's page is closed and the right one opened.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
Each installed and system plugin gets the same 44 px picture the store
shows: its own icon (Stream Deck manifest or plugin.json), DeckHost's icon
for system plugins, else its first action's icon, else its initials. The
store's Sources note no longer says there is no official catalog.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
The restart test read the process status live and then checked the Changed
count once; the events can arrive a moment after the status, so the check
failed now and then.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
The Device settings page had no template for secret and hotkey settings, so
the Web Deck's new PIN field showed "Not found: SecretSettingField". It now
has a password box with Show, and a test checks that every page that lists
settings has a template for every kind of field.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
…eb Deck

The device cards showed the MiraBox note ("the StreamDock SDK ... has no
update function") under every device, the Web Deck too. Each card now shows
what the device's own plugin reports (the version and its note, or that
Settings… → Firmware can update it) and nothing for devices without
firmware. The Settings… tooltip no longer lists N4 Pro settings.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EBcvHpHJnyUyHcb3dfxyi
@vman26
vman26 force-pushed the claude/workflows-release branch from de8fe8a to 3e5a3fa Compare November 15, 2026 11:56
@vman26
vman26 marked this pull request as ready for review November 15, 2026 11:56
@vman26
vman26 merged commit 11553ba into develop Nov 15, 2026
3 of 10 checks passed
@vman26
vman26 deleted the claude/workflows-release branch November 15, 2026 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants