M6.1: Remove APC USB identity and LED note restrictions. Note mute bindings with an output use their original channel and note with on=127/off=0. Alternate note/CC protocols and values remain explicit feedback configuration. Document the default and overrides.
Tests: generic controller regression failed before implementation; cargo test -p fader-config --test editor (23 tests) and cargo test -p fader_master --lib feedback (2 tests) pass. Formatting, workspace all-target/all-feature check, strict Clippy, doctests and release build pass. Full workspace all-target/all-feature tests with --no-fail-fast exercise all targets: same four pre-existing Arch-profile fixture failures; all remaining tests pass. No hardware LED test performed.
M6.1: Resolve missing feedback from the original APC Mini USB identity and supported note LED map, allowing the first learned mute binding to send confirmed feedback. Preserve explicit mappings and exclude unknown/outputless devices, unsupported controls, and MK2. Resolve defaults without rewriting user profiles.
Tests: fresh-profile planner regression failed with zero messages before the fix and passes after it. Added device/control exclusion and override coverage. cargo fmt --all -- --check, cargo check --workspace --all-targets --all-features, cargo clippy --workspace --all-targets --all-features -- -D warnings, cargo test --workspace --doc --all-features, cargo build --workspace --release --all-features pass. cargo test --workspace --all-targets --all-features --no-fail-fast --quiet exercises all targets: four existing Arch-profile fixture failures (schema ID and three MIDI device/routing assertions); remaining tests pass. Physical LED verification not performed.
MadGobblins/fader_master/pipeline/head This commit looks goodDetails
M9.3: Save advances the public revision offset, but MIDI passed the reducer revision into public validation. Subsequent volume/mute input failed deterministically and escaped the server loop. Move validation to the IPC request boundary; preserve stale-client rejection and execute server-owned MIDI against current state.
Regression reproduced StaleRevision { actual: 1, current: 2 } before the fix; repeated reconfiguration with MIDI volume/mute and correlated readbacks now passes. cargo test -p fader_master --lib live::reconfigure_tests: 4 passed. Full workspace all-target/all-feature tests with --no-fail-fast: all targets exercised, four fixture failures from the pre-existing edited arch-pipewire profile (schema ID and three MIDI routing/device assertions); all 12 live mixer and 47 TUI tests pass. cargo fmt --all -- --check, cargo check --workspace --all-targets --all-features, cargo clippy --workspace --all-targets --all-features -- -D warnings, cargo test --workspace --doc --all-features, and cargo build --workspace --release --all-features all pass.
Expose the server-owned active profile path through IPC and render it in the Config tab. Keep the displayed path current when switching profiles and document the diagnostic.
Tests: cargo fmt --all -- --check; cargo check --workspace --all-targets --all-features; cargo test -p tui; cargo test -p fader_master profile_switch_prepares_before_commit_and_invalid_candidate_keeps_old_profile; cargo clippy --workspace --all-targets --all-features -- -D warnings; cargo test --workspace --doc --all-features; cargo build --workspace --release --all-features. Full workspace tests reach the pre-existing user-edited arch-pipewire fixture failure: expected surface id apc-mini, got apc-mini-apc-mini-midi-1.
Keep the horizontal fader meter height stable by always reserving its pickup-status row at normal strip heights. Unassigned and hidden indicators render that row empty instead of expanding the meter.
Tests: cargo fmt --all -- --check; cargo check --workspace --all-targets --all-features; cargo test -p tui; cargo clippy --workspace --all-targets --all-features -- -D warnings; cargo test --workspace --doc --all-features; cargo build --workspace --release --all-features. Full workspace tests stop at the pre-existing edited examples/profiles/arch-pipewire.toml fixture mismatch.
Show the existing Left/Right mixer-orientation control in the Config quick-help footer and document the interaction.\n\nTests: cargo fmt --all -- --check\nTests: cargo test -p tui --all-features\nTests: cargo check --workspace --all-targets --all-features\nTests: cargo clippy -p tui --all-targets --all-features -- -D warnings
MadGobblins/fader_master/pipeline/head This commit looks goodDetails
Lead quick start with cargo-binstall for the published RC, manual downloads, runtime requirements and first-run setup. Retain source builds as an alternative.
Validation: cargo-binstall --git with exact RC version and crate-meta-data strategy passed in dry-run mode, resolving all three published executables without installing. Local documentation links and git diff --check passed. No release or tag changes.
Record v0.1.0-rc.1 publication, upstream publisher fix and digest-pinned Cross image override. Tagged source and user profile edits remain untouched.
Validation: documentation paths and git diff --check passed; authenticated dry run, compile-only packaging, SHA256SUMS, archive contents, ELF dependency inspection, three CLI help smoke tests, public asset downloads/checksums and isolated cargo-binstall verification passed. Gitea API confirms prerelease=true, draft=false and all five assets. Hardware and stable-release qualification remain pending.
Add token-file wrapper, Cargo-resolved version handling, GNU/Linux Cross configuration, binstall metadata, offline tests and release contract/audit. Preserve user profile edits; do not tag or publish.
Validation: 8 wrapper tests, sh -n, CI script tests, git diff --check, cargo fmt, workspace all-target/all-feature check and tests, doc tests, strict Clippy, release build, default/no-default builds, portable build and independent MIDI/Pulse checks passed. Two real-audio tests remain opt-in. ShellCheck unavailable.
Real publisher dry run confirms metadata/assets/destination but fails: installed rust_realease 0.1.3 rejects Cross pre-build and v0.1.0 tag is absent. Compile-only is blocked by pre-build support. No real token supplied; authenticated preview and artifact qualification remain pending. Public release API returned 404; no local/remote tag or assets exist.
Adopt a sole MIDI input when creating a managed profile, publish other unclaimed inputs to Config, and let the user add them as durable surfaces. Legacy empty profiles can add a safe Master fader, then Save and use the existing MIDI Learn flow without editing TOML.
Tests: cargo test --workspace --all-targets --all-features; cargo test --workspace --doc --all-features; cargo clippy --workspace --all-targets --all-features -- -D warnings; cargo build --workspace --release --all-features; default/no-default/midir/pulse cargo checks
Give newly initialized managed profiles a safe pickup-enabled default-output fader so the mixer and MIDI Learn have a usable target before application discovery.
Tests: cargo test -p fader_master managed_startup_initializes_missing_active_selection_and_profile --all-features; cargo test -p fader-config --test schema mixer_layout_defaults_to_declared_faders_and_validates_explicit_entries
Apply queued audio snapshot events before MIDI intents collected in the same server turn so pickup can evaluate the controller's first sweep against live state.
Tests: cargo test --workspace --all-targets --all-features; cargo test --workspace --doc --all-features; cargo clippy --workspace --all-targets --all-features -- -D warnings; cargo build --workspace --release --all-features; feature-matrix cargo checks
Add a persisted Bordered slim size between Slim and Standard. It renders as a three-row bordered vertical card and a compact horizontal strip, and round-trips through config, IPC, the editor, and TUI.
Tests: cargo test -p fader-config -p tui --all-targets --all-features --locked
Tests: cargo clippy --workspace --all-targets --all-features --locked -- -D warnings
Tests: cargo fmt --all -- --check
Keep queued mixer-layout moves visible and replay them over confirmed snapshots so rapid Shift+J/K or Shift+arrow input advances through each destination instead of repeatedly targeting stale order.
Tests: cargo test -p tui --all-targets --all-features --locked
Tests: cargo clippy -p tui --all-targets --all-features --locked -- -D warnings
Create a valid empty default profile and active pointer on first managed launch, or recreate only the missing profile named by an existing valid pointer. Preserve explicit-path failures and existing malformed files.
Tests: cargo test -p fader_master managed_startup_; cargo test -p fader-config --test schema --test persistence; cargo fmt --all -- --check