[jcelerier]

Part of a six-repo pass standardizing Suite SAT packaging on one convention. livepose is the reference implementation, so the changes here are small: the flag rename, and one latent bug.

The convention

• artifact uploads: <tool>-${{ matrix.artifact-name }} and <tool>-pro-${{ matrix.artifact-name }}
• release download pattern <tool>-*, which must match both editions
• app-name differs per edition ("<Tool>" / "<Tool> Pro"), because tools/create-app.sh:234 derives the output filename from it -- two editions sharing a name produce one filename and silently overwrite
• pro gated positively: environment leaves the flag commented out, environment-pro sets it

Flag rename

"Pro" means the same thing in every tool: basic is camera and file input, pro also has NDI / Spout / Syphon. A per-tool LIVEPOSE_ADVANCED_IO was redundant and made the four hosts look like four different policies. All four now read SAT_ADVANCED_IO. The variable is only ever set by the shipped environment-pro, so nothing external depends on the old name.

qmlcomponents/io/InputSourceSelector.qml is unchanged: its contract is that the host computes allowedBackends and the widget does the platform filtering, which is exactly what is wanted here.

Latent bug fixed

Both uploads read ${{ matrix.artifact-path || '<their own dir>' }}. A single matrix row adding an artifact-path override -- as the wasm rows in koaia and spm do -- would have pointed both uploads at the basic directory, publishing the basic package under the livepose-pro-* artifact name. livepose has no wasm row yet, so this was latent, but it is the same failure mode that shipped the wrong Domeport edition. The matrix now overrides only the file glob (artifact-file) and each upload keeps its own output directory.

Verification

	value
basic upload	livepose-${{ matrix.artifact-name }}
pro upload	livepose-pro-${{ matrix.artifact-name }}
release pattern	livepose-* -- matches both
filenames	LivePose-* / LivePose-Pro-*

build.yml passes yaml.safe_load. These workflows cannot be run locally, so CI is the verification path.

---

The set

One convention across the Suite SAT tools; review these together:

• livepose (reference) — Rename the pro I/O gate to SAT_ADVANCED_IO #83
• DomeportPro — Gate pro I/O positively on SAT_ADVANCED_IO, and name the editions symmetrically DomeportPro#93
• koaia — Add the pro-edition packaging, name artifacts after the tool, and build the score graph at runtime koaia#120
• scenic-native — Add a pro edition gated on SAT_ADVANCED_IO, align the artifact names, and fix the SCENIC_SCENARIO URL and camera release scenic-native#3
• spatial-protocol-mapper — Name packaging artifacts after the tool, not "app" spatial-protocol-mapper#28

speaker-setup-format-converter needs no change: it is not a score app and has no editions, and its speaker-layout-converter-* uploads already match its speaker-layout-converter-* release pattern.

qmlcomponents is unchanged. It is a git submodule in livepose, DomeportPro and spm, not a vendored copy, so there is one source of truth and no drift. InputSourceSelector is agnostic by contract — the host computes allowedBackends, the widget does the platform filtering — which is exactly what these PRs rely on.

[jcelerier]

Triaged: the Package Custom App - linux-x86_64 failure is not in livepose. appimagetool is itself an AppImage and the self-hosted host has no usable FUSE under rootless docker, so it dies with fusermount3: mount failed: Operation not permitted and exit 127 after ~22 min of building.

Fixed in ossia/actions#29, which sets APPIMAGE_EXTRACT_AND_RUN on the two steps that write an AppImage — custom-score-build's Build (score's own, where this job died) and package-custom-app's packaging step (the app's own, the next place it would have failed). Since this repo pins the action at @master, re-running this job will keep failing identically until that merges; after it merges, no change is needed here.

Verified by A/B on appimagetool with no fusermount on $PATH: unset → exit 127 with the same open dir error line and no output file; APPIMAGE_EXTRACT_AND_RUN=1 → exit 0 and the AppImage is written.