From bd603184d51d435890f2f990e8b9f6c0b677776e Mon Sep 17 00:00:00 2001 From: Byron Gamatos Date: Tue, 16 Jun 2026 18:48:12 +0200 Subject: [PATCH] Clean release snapshot --- .build-config.json | 52 + .claude/skills/speckit-analyze/SKILL.md | 260 + .claude/skills/speckit-checklist/SKILL.md | 372 ++ .claude/skills/speckit-clarify/SKILL.md | 254 + .claude/skills/speckit-constitution/SKILL.md | 157 + .claude/skills/speckit-implement/SKILL.md | 210 + .claude/skills/speckit-plan/SKILL.md | 152 + .claude/skills/speckit-specify/SKILL.md | 330 ++ .claude/skills/speckit-tasks/SKILL.md | 202 + .claude/skills/speckit-taskstoissues/SKILL.md | 106 + .devcontainer/Dockerfile | 64 + .devcontainer/README.md | 171 + .devcontainer/devcontainer.json | 37 + .github/FUNDING.yml | 4 + .github/workflows/addon-ci.yml | 128 + .github/workflows/build.yml | 563 ++ .github/workflows/ci.yml | 48 + .github/workflows/nightly.yml | 197 + .github/workflows/release.yml | 292 ++ .github/workflows/sandbox.yml | 158 + .github/workflows/ship-ci.yml | 22 + .gitignore | 56 + .gitmodules | 20 + .packages/README.md | 70 + .packages/apt.txt | 53 + .packages/brew.txt | 39 + .packages/choco.txt | 12 + .packages/python.txt | 19 + .specify/init-options.json | 10 + .specify/integration.json | 15 + .specify/integrations/claude.manifest.json | 16 + .specify/integrations/speckit.manifest.json | 17 + .specify/memory/constitution.md | 118 + .specify/scripts/bash/check-prerequisites.sh | 190 + .specify/scripts/bash/common.sh | 645 +++ .specify/scripts/bash/create-new-feature.sh | 413 ++ .specify/scripts/bash/setup-plan.sh | 75 + .specify/scripts/bash/setup-tasks.sh | 96 + .specify/templates/checklist-template.md | 40 + .specify/templates/constitution-template.md | 50 + .specify/templates/plan-template.md | 104 + .specify/templates/spec-template.md | 128 + .specify/templates/tasks-template.md | 251 + .specify/workflows/speckit/workflow.yml | 63 + .specify/workflows/workflow-registry.json | 13 + CMakeLists.txt | 64 + CONTRIBUTORS.md | 15 + JUCE | 1 + LICENSE | 661 +++ README.md | 22 + THIRD_PARTY_LICENSES.md | 175 + WINDOWS_BUILD_REQUIREMENTS.md | 69 + cmake/onnxruntime.cmake | 202 + docs/BUILD_ARCHITECTURE.md | 203 + docs/CAPABILITY-MIGRATION.md | 108 + docs/SANDBOX-DESIGN.md | 446 ++ docs/VST-SANDBOX-DIAG.md | 120 + package.json | 151 + resources/default-irs/.gitkeep | 0 resources/default-irs/1x12_Open_Fender.wav | Bin 0 -> 8236 bytes .../default-irs/2x12_Closed_Marshall.wav | Bin 0 -> 8236 bytes resources/default-irs/4x12_Closed_V30.wav | Bin 0 -> 8236 bytes resources/default-irs/4x12_Modern_Metal.wav | Bin 0 -> 8236 bytes resources/default-irs/guitar_amp.wav | Bin 0 -> 90246 bytes resources/default-irs/mesa_cab.wav | 1459 ++++++ resources/entitlements.mac.plist | 16 + resources/icons/.gitkeep | 0 resources/icons/128x128.png | Bin 0 -> 4913 bytes resources/icons/16x16.png | Bin 0 -> 411 bytes resources/icons/256x256.png | Bin 0 -> 9833 bytes resources/icons/32x32.png | Bin 0 -> 981 bytes resources/icons/48x48.png | Bin 0 -> 1650 bytes resources/icons/512x512.png | Bin 0 -> 21152 bytes resources/icons/64x64.png | Bin 0 -> 2321 bytes resources/icons/icon.icns | Bin 0 -> 119237 bytes resources/icons/icon.ico | Bin 0 -> 370070 bytes resources/icons/icon.svg | 1 + resources/models/README.md | 19 + resources/models/basic_pitch.onnx | Bin 0 -> 230444 bytes resources/soundfonts/LICENSE | 43 + scripts/BUILD_SCRIPTS.md | 186 + scripts/VST_TRACE_README.md | 69 + scripts/build-audio.sh | 149 + scripts/build-common.sh | 590 +++ scripts/build-linux-docker.sh | 102 + scripts/build-linux-ubuntu.sh | 67 + scripts/build-macos.sh | 419 ++ scripts/build-release.sh | 100 + scripts/build-windows.sh | 276 + scripts/bundle-binaries.sh | 191 + scripts/bundle-python.sh | 89 + scripts/bundle-slopsmith.sh | 189 + scripts/bundle-soundfont.sh | 35 + scripts/bundle.sh | 35 + scripts/bundled-lib-skiplist.sh | 22 + scripts/dev/load-gr6.js | 129 + scripts/fix-onnxruntime-install-names.sh | 78 + scripts/parse-build-config.py | 50 + scripts/setup-dev.sh | 158 + scripts/sign-macos-binaries.sh | 98 + src/audio/AudioEngine.cpp | 2589 +++++++++ src/audio/AudioEngine.h | 598 +++ src/audio/AudioSanitize.h | 53 + src/audio/CMakeLists.txt | 285 + src/audio/ChordScorer.cpp | 470 ++ src/audio/ChordScorer.h | 170 + src/audio/IRLoader.cpp | 106 + src/audio/IRLoader.h | 64 + src/audio/InputRingReader.h | 29 + src/audio/MlNoteDetector.cpp | 571 ++ src/audio/MlNoteDetector.h | 88 + src/audio/NAMProcessor.cpp | 142 + src/audio/NAMProcessor.h | 71 + src/audio/NodeAddon.cpp | 3149 +++++++++++ src/audio/NoiseGate.cpp | 97 + src/audio/NoiseGate.h | 59 + src/audio/NoteVerifier.cpp | 416 ++ src/audio/NoteVerifier.h | 205 + src/audio/OnsetDetector.cpp | 226 + src/audio/OnsetDetector.h | 105 + src/audio/PitchDetector.cpp | 316 ++ src/audio/PitchDetector.h | 121 + src/audio/Sandbox/AudioChannel.h | 126 + src/audio/Sandbox/AudioChannelImpl.h | 80 + src/audio/Sandbox/AudioChannel_posix.cpp | 471 ++ src/audio/Sandbox/AudioChannel_shared.cpp | 503 ++ src/audio/Sandbox/AudioChannel_win.cpp | 294 ++ src/audio/Sandbox/ControlChannel.h | 163 + src/audio/Sandbox/ControlChannelImpl.h | 51 + src/audio/Sandbox/ControlChannel_posix.cpp | 400 ++ src/audio/Sandbox/ControlChannel_shared.cpp | 248 + src/audio/Sandbox/ControlChannel_win.cpp | 373 ++ src/audio/Sandbox/Protocol.cpp | 84 + src/audio/Sandbox/Protocol.h | 285 + src/audio/Sandbox/SandboxFactory_posix.cpp | 48 + src/audio/Sandbox/SandboxFactory_shared.cpp | 146 + src/audio/Sandbox/SandboxFactory_win.cpp | 77 + src/audio/Sandbox/SandboxedProcessor.cpp | 582 +++ src/audio/Sandbox/SandboxedProcessor.h | 241 + src/audio/Sandbox/SubprocessHandle.h | 75 + src/audio/Sandbox/SubprocessHandleImpl.h | 26 + src/audio/Sandbox/SubprocessHandle_posix.cpp | 229 + src/audio/Sandbox/SubprocessHandle_win.cpp | 178 + src/audio/SignalChain.cpp | 325 ++ src/audio/SignalChain.h | 91 + src/audio/SourceChain.cpp | 544 ++ src/audio/SourceChain.h | 215 + src/audio/TonePolish.cpp | 116 + src/audio/TonePolish.h | 73 + src/audio/VSTHost.cpp | 609 +++ src/audio/VSTHost.h | 91 + src/audio/VSTTrace.h | 163 + src/audio/third_party/.gitkeep | 0 src/audio/third_party/NAM | 1 + src/audio/third_party/RTNeural | 1 + src/audio/third_party/signalsmith-linear | 1 + src/audio/third_party/signalsmith-stretch | 1 + src/main/audio-bridge.ts | 1183 +++++ src/main/audio-effects-executor.ts | 713 +++ src/main/debug-log.ts | 75 + src/main/images/1.webp | Bin 0 -> 4292 bytes src/main/images/10.webp | Bin 0 -> 3858 bytes src/main/images/11.webp | Bin 0 -> 4004 bytes src/main/images/12.webp | Bin 0 -> 3934 bytes src/main/images/13.webp | Bin 0 -> 4158 bytes src/main/images/14.webp | Bin 0 -> 4132 bytes src/main/images/15.webp | Bin 0 -> 4200 bytes src/main/images/16.webp | Bin 0 -> 4214 bytes src/main/images/17.webp | Bin 0 -> 4212 bytes src/main/images/18.webp | Bin 0 -> 4234 bytes src/main/images/19.webp | Bin 0 -> 4054 bytes src/main/images/2.webp | Bin 0 -> 4284 bytes src/main/images/20.webp | Bin 0 -> 4122 bytes src/main/images/21.webp | Bin 0 -> 3914 bytes src/main/images/22.webp | Bin 0 -> 3858 bytes src/main/images/23.webp | Bin 0 -> 3886 bytes src/main/images/24.webp | Bin 0 -> 3852 bytes src/main/images/25.webp | Bin 0 -> 3914 bytes src/main/images/26.webp | Bin 0 -> 3824 bytes src/main/images/27.webp | Bin 0 -> 3926 bytes src/main/images/28.webp | Bin 0 -> 4028 bytes src/main/images/29.webp | Bin 0 -> 4166 bytes src/main/images/3.webp | Bin 0 -> 4188 bytes src/main/images/30.webp | Bin 0 -> 4188 bytes src/main/images/31.webp | Bin 0 -> 4054 bytes src/main/images/32.webp | Bin 0 -> 4236 bytes src/main/images/33.webp | Bin 0 -> 4134 bytes src/main/images/34.webp | Bin 0 -> 4150 bytes src/main/images/35.webp | Bin 0 -> 3984 bytes src/main/images/36.webp | Bin 0 -> 3910 bytes src/main/images/37.webp | Bin 0 -> 3858 bytes src/main/images/38.webp | Bin 0 -> 3850 bytes src/main/images/39.webp | Bin 0 -> 3822 bytes src/main/images/4.webp | Bin 0 -> 4164 bytes src/main/images/40.webp | Bin 0 -> 3870 bytes src/main/images/41.webp | Bin 0 -> 3956 bytes src/main/images/42.webp | Bin 0 -> 4008 bytes src/main/images/43.webp | Bin 0 -> 4178 bytes src/main/images/44.webp | Bin 0 -> 4196 bytes src/main/images/45.webp | Bin 0 -> 4154 bytes src/main/images/46.webp | Bin 0 -> 4164 bytes src/main/images/47.webp | Bin 0 -> 3930 bytes src/main/images/48.webp | Bin 0 -> 4020 bytes src/main/images/49.webp | Bin 0 -> 3814 bytes src/main/images/5.webp | Bin 0 -> 4052 bytes src/main/images/50.webp | Bin 0 -> 3834 bytes src/main/images/51.webp | Bin 0 -> 3950 bytes src/main/images/52.webp | Bin 0 -> 4086 bytes src/main/images/53.webp | Bin 0 -> 4154 bytes src/main/images/54.webp | Bin 0 -> 4128 bytes src/main/images/55.webp | Bin 0 -> 4230 bytes src/main/images/56.webp | Bin 0 -> 4188 bytes src/main/images/57.webp | Bin 0 -> 4104 bytes src/main/images/58.webp | Bin 0 -> 4022 bytes src/main/images/59.webp | Bin 0 -> 3994 bytes src/main/images/6.webp | Bin 0 -> 3942 bytes src/main/images/60.webp | Bin 0 -> 3740 bytes src/main/images/61.webp | Bin 0 -> 3824 bytes src/main/images/62.webp | Bin 0 -> 3640 bytes src/main/images/63.webp | Bin 0 -> 3638 bytes src/main/images/64.webp | Bin 0 -> 3556 bytes src/main/images/65.webp | Bin 0 -> 3816 bytes src/main/images/66.webp | Bin 0 -> 3828 bytes src/main/images/67.webp | Bin 0 -> 3920 bytes src/main/images/68.webp | Bin 0 -> 3810 bytes src/main/images/69.webp | Bin 0 -> 3858 bytes src/main/images/7.webp | Bin 0 -> 3882 bytes src/main/images/70.webp | Bin 0 -> 4008 bytes src/main/images/71.webp | Bin 0 -> 3954 bytes src/main/images/72.webp | Bin 0 -> 4072 bytes src/main/images/73.webp | Bin 0 -> 4188 bytes src/main/images/74.webp | Bin 0 -> 4228 bytes src/main/images/75.webp | Bin 0 -> 4162 bytes src/main/images/76.webp | Bin 0 -> 4160 bytes src/main/images/8.webp | Bin 0 -> 3820 bytes src/main/images/9.webp | Bin 0 -> 3840 bytes src/main/ipc-channels.ts | 26 + src/main/main.ts | 1174 +++++ src/main/nsis-migration.ts | 273 + src/main/plugin-manager.ts | 222 + src/main/preload.ts | 506 ++ src/main/python.ts | 914 ++++ src/main/soundfont-manager.ts | 257 + src/main/spinner.json | 1 + src/main/splash-preload.ts | 17 + src/main/splash.html | 60 + src/main/update-manager.ts | 435 ++ src/main/vst-crash-guard.ts | 128 + src/renderer/plugin-manager/plugin.json | 13 + src/renderer/plugin-manager/screen.html | 44 + src/renderer/plugin-manager/screen.js | 172 + src/renderer/plugin.json | 64 + src/renderer/screen.html | 232 + src/renderer/screen.js | 4642 +++++++++++++++++ src/renderer/settings.html | 110 + src/vst-host/CMakeLists.txt | 137 + src/vst-host/VSTScan.cpp | 47 + src/vst-host/main.cpp | 1921 +++++++ tests/CMakeLists.txt | 20 + tests/audio-effects-executor.test.js | 392 ++ tests/audio_sanitize/CMakeLists.txt | 6 + tests/audio_sanitize/test.cpp | 65 + tests/chordscorer/.gitignore | 5 + tests/chordscorer/CMakeLists.txt | 35 + tests/chordscorer/bench.cpp | 395 ++ tests/chordscorer/calibration/chart.txt | 58 + .../calibration/make_calibration.py | 153 + tests/chordscorer/calibration/notes.csv | 59 + tests/chordscorer/calibration/score.md | 95 + .../chordscorer/calibration/wrong_position.md | 41 + tests/ml-note-detection.test.js | 121 + tests/mlnotedetector/CMakeLists.txt | 74 + tests/mlnotedetector/bench.cpp | 314 ++ tests/mlnotedetector/test.cpp | 147 + tests/multi-source.test.js | 125 + tests/renderer-capability-migration.test.js | 126 + tests/sandbox/CMakeLists.txt | 117 + tests/sandbox/audio_channel_midi_test.cpp | 413 ++ tests/sandbox/control_channel_test.cpp | 218 + tests/sandbox/e2e/CMakeLists.txt | 110 + tests/sandbox/e2e/e2e_test.cpp | 156 + tests/sandbox/e2e/leak_test.sh | 55 + tests/sandbox/e2e/passthrough.cpp | 49 + tests/sandbox/spawn_smoke_child.cpp | 79 + tests/sandbox/spawn_smoke_test.cpp | 192 + tests/sandbox/standalone/CMakeLists.txt | 30 + tests/spike/CMakeLists.txt | 28 + tests/spike/README.md | 63 + tests/spike/main.cpp | 252 + tests/spike/test_guitar.wav | Bin 0 -> 528044 bytes tsconfig.json | 19 + 291 files changed, 47318 insertions(+) create mode 100644 .build-config.json create mode 100644 .claude/skills/speckit-analyze/SKILL.md create mode 100644 .claude/skills/speckit-checklist/SKILL.md create mode 100644 .claude/skills/speckit-clarify/SKILL.md create mode 100644 .claude/skills/speckit-constitution/SKILL.md create mode 100644 .claude/skills/speckit-implement/SKILL.md create mode 100644 .claude/skills/speckit-plan/SKILL.md create mode 100644 .claude/skills/speckit-specify/SKILL.md create mode 100644 .claude/skills/speckit-tasks/SKILL.md create mode 100644 .claude/skills/speckit-taskstoissues/SKILL.md create mode 100644 .devcontainer/Dockerfile create mode 100644 .devcontainer/README.md create mode 100644 .devcontainer/devcontainer.json create mode 100644 .github/FUNDING.yml create mode 100644 .github/workflows/addon-ci.yml create mode 100644 .github/workflows/build.yml create mode 100644 .github/workflows/ci.yml create mode 100644 .github/workflows/nightly.yml create mode 100644 .github/workflows/release.yml create mode 100644 .github/workflows/sandbox.yml create mode 100644 .github/workflows/ship-ci.yml create mode 100644 .gitignore create mode 100644 .gitmodules create mode 100644 .packages/README.md create mode 100644 .packages/apt.txt create mode 100644 .packages/brew.txt create mode 100644 .packages/choco.txt create mode 100644 .packages/python.txt create mode 100644 .specify/init-options.json create mode 100644 .specify/integration.json create mode 100644 .specify/integrations/claude.manifest.json create mode 100644 .specify/integrations/speckit.manifest.json create mode 100644 .specify/memory/constitution.md create mode 100755 .specify/scripts/bash/check-prerequisites.sh create mode 100755 .specify/scripts/bash/common.sh create mode 100755 .specify/scripts/bash/create-new-feature.sh create mode 100755 .specify/scripts/bash/setup-plan.sh create mode 100755 .specify/scripts/bash/setup-tasks.sh create mode 100644 .specify/templates/checklist-template.md create mode 100644 .specify/templates/constitution-template.md create mode 100644 .specify/templates/plan-template.md create mode 100644 .specify/templates/spec-template.md create mode 100644 .specify/templates/tasks-template.md create mode 100644 .specify/workflows/speckit/workflow.yml create mode 100644 .specify/workflows/workflow-registry.json create mode 100644 CMakeLists.txt create mode 100644 CONTRIBUTORS.md create mode 160000 JUCE create mode 100644 LICENSE create mode 100644 README.md create mode 100644 THIRD_PARTY_LICENSES.md create mode 100644 WINDOWS_BUILD_REQUIREMENTS.md create mode 100644 cmake/onnxruntime.cmake create mode 100644 docs/BUILD_ARCHITECTURE.md create mode 100644 docs/CAPABILITY-MIGRATION.md create mode 100644 docs/SANDBOX-DESIGN.md create mode 100644 docs/VST-SANDBOX-DIAG.md create mode 100644 package.json create mode 100644 resources/default-irs/.gitkeep create mode 100644 resources/default-irs/1x12_Open_Fender.wav create mode 100644 resources/default-irs/2x12_Closed_Marshall.wav create mode 100644 resources/default-irs/4x12_Closed_V30.wav create mode 100644 resources/default-irs/4x12_Modern_Metal.wav create mode 100644 resources/default-irs/guitar_amp.wav create mode 100644 resources/default-irs/mesa_cab.wav create mode 100644 resources/entitlements.mac.plist create mode 100644 resources/icons/.gitkeep create mode 100644 resources/icons/128x128.png create mode 100644 resources/icons/16x16.png create mode 100644 resources/icons/256x256.png create mode 100644 resources/icons/32x32.png create mode 100644 resources/icons/48x48.png create mode 100644 resources/icons/512x512.png create mode 100644 resources/icons/64x64.png create mode 100644 resources/icons/icon.icns create mode 100644 resources/icons/icon.ico create mode 100644 resources/icons/icon.svg create mode 100644 resources/models/README.md create mode 100644 resources/models/basic_pitch.onnx create mode 100644 resources/soundfonts/LICENSE create mode 100644 scripts/BUILD_SCRIPTS.md create mode 100644 scripts/VST_TRACE_README.md create mode 100755 scripts/build-audio.sh create mode 100644 scripts/build-common.sh create mode 100755 scripts/build-linux-docker.sh create mode 100755 scripts/build-linux-ubuntu.sh create mode 100755 scripts/build-macos.sh create mode 100755 scripts/build-release.sh create mode 100755 scripts/build-windows.sh create mode 100755 scripts/bundle-binaries.sh create mode 100755 scripts/bundle-python.sh create mode 100755 scripts/bundle-slopsmith.sh create mode 100755 scripts/bundle-soundfont.sh create mode 100755 scripts/bundle.sh create mode 100644 scripts/bundled-lib-skiplist.sh create mode 100644 scripts/dev/load-gr6.js create mode 100755 scripts/fix-onnxruntime-install-names.sh create mode 100755 scripts/parse-build-config.py create mode 100755 scripts/setup-dev.sh create mode 100755 scripts/sign-macos-binaries.sh create mode 100644 src/audio/AudioEngine.cpp create mode 100644 src/audio/AudioEngine.h create mode 100644 src/audio/AudioSanitize.h create mode 100644 src/audio/CMakeLists.txt create mode 100644 src/audio/ChordScorer.cpp create mode 100644 src/audio/ChordScorer.h create mode 100644 src/audio/IRLoader.cpp create mode 100644 src/audio/IRLoader.h create mode 100644 src/audio/InputRingReader.h create mode 100644 src/audio/MlNoteDetector.cpp create mode 100644 src/audio/MlNoteDetector.h create mode 100644 src/audio/NAMProcessor.cpp create mode 100644 src/audio/NAMProcessor.h create mode 100644 src/audio/NodeAddon.cpp create mode 100644 src/audio/NoiseGate.cpp create mode 100644 src/audio/NoiseGate.h create mode 100644 src/audio/NoteVerifier.cpp create mode 100644 src/audio/NoteVerifier.h create mode 100644 src/audio/OnsetDetector.cpp create mode 100644 src/audio/OnsetDetector.h create mode 100644 src/audio/PitchDetector.cpp create mode 100644 src/audio/PitchDetector.h create mode 100644 src/audio/Sandbox/AudioChannel.h create mode 100644 src/audio/Sandbox/AudioChannelImpl.h create mode 100644 src/audio/Sandbox/AudioChannel_posix.cpp create mode 100644 src/audio/Sandbox/AudioChannel_shared.cpp create mode 100644 src/audio/Sandbox/AudioChannel_win.cpp create mode 100644 src/audio/Sandbox/ControlChannel.h create mode 100644 src/audio/Sandbox/ControlChannelImpl.h create mode 100644 src/audio/Sandbox/ControlChannel_posix.cpp create mode 100644 src/audio/Sandbox/ControlChannel_shared.cpp create mode 100644 src/audio/Sandbox/ControlChannel_win.cpp create mode 100644 src/audio/Sandbox/Protocol.cpp create mode 100644 src/audio/Sandbox/Protocol.h create mode 100644 src/audio/Sandbox/SandboxFactory_posix.cpp create mode 100644 src/audio/Sandbox/SandboxFactory_shared.cpp create mode 100644 src/audio/Sandbox/SandboxFactory_win.cpp create mode 100644 src/audio/Sandbox/SandboxedProcessor.cpp create mode 100644 src/audio/Sandbox/SandboxedProcessor.h create mode 100644 src/audio/Sandbox/SubprocessHandle.h create mode 100644 src/audio/Sandbox/SubprocessHandleImpl.h create mode 100644 src/audio/Sandbox/SubprocessHandle_posix.cpp create mode 100644 src/audio/Sandbox/SubprocessHandle_win.cpp create mode 100644 src/audio/SignalChain.cpp create mode 100644 src/audio/SignalChain.h create mode 100644 src/audio/SourceChain.cpp create mode 100644 src/audio/SourceChain.h create mode 100644 src/audio/TonePolish.cpp create mode 100644 src/audio/TonePolish.h create mode 100644 src/audio/VSTHost.cpp create mode 100644 src/audio/VSTHost.h create mode 100644 src/audio/VSTTrace.h create mode 100644 src/audio/third_party/.gitkeep create mode 160000 src/audio/third_party/NAM create mode 160000 src/audio/third_party/RTNeural create mode 160000 src/audio/third_party/signalsmith-linear create mode 160000 src/audio/third_party/signalsmith-stretch create mode 100644 src/main/audio-bridge.ts create mode 100644 src/main/audio-effects-executor.ts create mode 100644 src/main/debug-log.ts create mode 100644 src/main/images/1.webp create mode 100644 src/main/images/10.webp create mode 100644 src/main/images/11.webp create mode 100644 src/main/images/12.webp create mode 100644 src/main/images/13.webp create mode 100644 src/main/images/14.webp create mode 100644 src/main/images/15.webp create mode 100644 src/main/images/16.webp create mode 100644 src/main/images/17.webp create mode 100644 src/main/images/18.webp create mode 100644 src/main/images/19.webp create mode 100644 src/main/images/2.webp create mode 100644 src/main/images/20.webp create mode 100644 src/main/images/21.webp create mode 100644 src/main/images/22.webp create mode 100644 src/main/images/23.webp create mode 100644 src/main/images/24.webp create mode 100644 src/main/images/25.webp create mode 100644 src/main/images/26.webp create mode 100644 src/main/images/27.webp create mode 100644 src/main/images/28.webp create mode 100644 src/main/images/29.webp create mode 100644 src/main/images/3.webp create mode 100644 src/main/images/30.webp create mode 100644 src/main/images/31.webp create mode 100644 src/main/images/32.webp create mode 100644 src/main/images/33.webp create mode 100644 src/main/images/34.webp create mode 100644 src/main/images/35.webp create mode 100644 src/main/images/36.webp create mode 100644 src/main/images/37.webp create mode 100644 src/main/images/38.webp create mode 100644 src/main/images/39.webp create mode 100644 src/main/images/4.webp create mode 100644 src/main/images/40.webp create mode 100644 src/main/images/41.webp create mode 100644 src/main/images/42.webp create mode 100644 src/main/images/43.webp create mode 100644 src/main/images/44.webp create mode 100644 src/main/images/45.webp create mode 100644 src/main/images/46.webp create mode 100644 src/main/images/47.webp create mode 100644 src/main/images/48.webp create mode 100644 src/main/images/49.webp create mode 100644 src/main/images/5.webp create mode 100644 src/main/images/50.webp create mode 100644 src/main/images/51.webp create mode 100644 src/main/images/52.webp create mode 100644 src/main/images/53.webp create mode 100644 src/main/images/54.webp create mode 100644 src/main/images/55.webp create mode 100644 src/main/images/56.webp create mode 100644 src/main/images/57.webp create mode 100644 src/main/images/58.webp create mode 100644 src/main/images/59.webp create mode 100644 src/main/images/6.webp create mode 100644 src/main/images/60.webp create mode 100644 src/main/images/61.webp create mode 100644 src/main/images/62.webp create mode 100644 src/main/images/63.webp create mode 100644 src/main/images/64.webp create mode 100644 src/main/images/65.webp create mode 100644 src/main/images/66.webp create mode 100644 src/main/images/67.webp create mode 100644 src/main/images/68.webp create mode 100644 src/main/images/69.webp create mode 100644 src/main/images/7.webp create mode 100644 src/main/images/70.webp create mode 100644 src/main/images/71.webp create mode 100644 src/main/images/72.webp create mode 100644 src/main/images/73.webp create mode 100644 src/main/images/74.webp create mode 100644 src/main/images/75.webp create mode 100644 src/main/images/76.webp create mode 100644 src/main/images/8.webp create mode 100644 src/main/images/9.webp create mode 100644 src/main/ipc-channels.ts create mode 100644 src/main/main.ts create mode 100644 src/main/nsis-migration.ts create mode 100644 src/main/plugin-manager.ts create mode 100644 src/main/preload.ts create mode 100644 src/main/python.ts create mode 100644 src/main/soundfont-manager.ts create mode 100644 src/main/spinner.json create mode 100644 src/main/splash-preload.ts create mode 100644 src/main/splash.html create mode 100644 src/main/update-manager.ts create mode 100644 src/main/vst-crash-guard.ts create mode 100644 src/renderer/plugin-manager/plugin.json create mode 100644 src/renderer/plugin-manager/screen.html create mode 100644 src/renderer/plugin-manager/screen.js create mode 100644 src/renderer/plugin.json create mode 100644 src/renderer/screen.html create mode 100644 src/renderer/screen.js create mode 100644 src/renderer/settings.html create mode 100644 src/vst-host/CMakeLists.txt create mode 100644 src/vst-host/VSTScan.cpp create mode 100644 src/vst-host/main.cpp create mode 100644 tests/CMakeLists.txt create mode 100644 tests/audio-effects-executor.test.js create mode 100644 tests/audio_sanitize/CMakeLists.txt create mode 100644 tests/audio_sanitize/test.cpp create mode 100644 tests/chordscorer/.gitignore create mode 100644 tests/chordscorer/CMakeLists.txt create mode 100644 tests/chordscorer/bench.cpp create mode 100644 tests/chordscorer/calibration/chart.txt create mode 100644 tests/chordscorer/calibration/make_calibration.py create mode 100644 tests/chordscorer/calibration/notes.csv create mode 100644 tests/chordscorer/calibration/score.md create mode 100644 tests/chordscorer/calibration/wrong_position.md create mode 100644 tests/ml-note-detection.test.js create mode 100644 tests/mlnotedetector/CMakeLists.txt create mode 100644 tests/mlnotedetector/bench.cpp create mode 100644 tests/mlnotedetector/test.cpp create mode 100644 tests/multi-source.test.js create mode 100644 tests/renderer-capability-migration.test.js create mode 100644 tests/sandbox/CMakeLists.txt create mode 100644 tests/sandbox/audio_channel_midi_test.cpp create mode 100644 tests/sandbox/control_channel_test.cpp create mode 100644 tests/sandbox/e2e/CMakeLists.txt create mode 100644 tests/sandbox/e2e/e2e_test.cpp create mode 100755 tests/sandbox/e2e/leak_test.sh create mode 100644 tests/sandbox/e2e/passthrough.cpp create mode 100644 tests/sandbox/spawn_smoke_child.cpp create mode 100644 tests/sandbox/spawn_smoke_test.cpp create mode 100644 tests/sandbox/standalone/CMakeLists.txt create mode 100644 tests/spike/CMakeLists.txt create mode 100644 tests/spike/README.md create mode 100644 tests/spike/main.cpp create mode 100644 tests/spike/test_guitar.wav create mode 100644 tsconfig.json diff --git a/.build-config.json b/.build-config.json new file mode 100644 index 0000000..1a5efcd --- /dev/null +++ b/.build-config.json @@ -0,0 +1,52 @@ +{ + "versions": { + "node": "22", + "python": "3.12.9", + "electron": "35.0.0", + "cmake": "3.22", + "ubuntu": "22.04" + }, + "external": { + "fluidsynth_windows": { + "version": "v2.5.4", + "url": "https://github.com/FluidSynth/fluidsynth/releases/download/v2.5.4/fluidsynth-v2.5.4-win10-x64-cpp11.zip" + }, + "soundfont_general_user": { + "url": "https://github.com/slopsmith/slopsmith-desktop/releases/download/soundfonts-v1/GeneralUser-GS.sf2", + "sha256": "9575028c7a1f589f5770fccc8cff2734566af40cd26ed836944e9a5152688cfe" + }, + "python_standalone_macos_arm64": { + "url": "https://github.com/astral-sh/python-build-standalone/releases/download/20250317/cpython-3.12.9+20250317-aarch64-apple-darwin-install_only_stripped.tar.gz", + "sha256": "0a4647b7df3c8eca11071d6cea68a14a4b102bd6fc6afae314e9852510654b7d" + }, + "python_standalone_macos_x64": { + "url": "https://github.com/astral-sh/python-build-standalone/releases/download/20250317/cpython-3.12.9+20250317-x86_64-apple-darwin-install_only_stripped.tar.gz", + "sha256": "1a414bf392a7afe08c742502a82edd41893a1144ccbceb184dc5ee6ee9c069c0" + }, + "python_standalone_linux_x64": { + "url": "https://github.com/astral-sh/python-build-standalone/releases/download/20250317/cpython-3.12.9+20250317-x86_64-unknown-linux-gnu-install_only_stripped.tar.gz", + "sha256": "a36bc60c38fe146e908e2e71fc21266c8558b24a9407226b1d887212839437ef" + }, + "ffmpeg_macos_arm64": { + "url": "https://www.osxexperts.net/ffmpeg81arm.zip", + "sha256": "ebb82529562b71170807bbc6b0e7eb4f0b13af8cbb0e085bb9e8f6fe709598ad" + }, + "ffprobe_macos_arm64": { + "url": "https://www.osxexperts.net/ffprobe81arm.zip", + "sha256": "a6640a77d38a6f0527c5b597e599cb36a3427a6931444ed80bc62542421950a1" + }, + "ffmpeg_macos_x64": { + "url": "https://evermeet.cx/ffmpeg/ffmpeg-8.1.1.zip", + "sha256": "4610988e2f54c243c50da73a09e4e2c36d9bb77546f9aa6c84cb328dcb1a98c1" + }, + "ffprobe_macos_x64": { + "url": "https://evermeet.cx/ffmpeg/ffprobe-8.1.1.zip", + "sha256": "aeade29dee3c3844e9bcc974f4ae4b29cc4f87994177d77003a8589fa531009e" + }, + "ffmpeg_macos_rubberband": { + "_comment": "Intel ffmpeg with --enable-librubberband, bundled as resources/bin/ffmpeg-rubberband on Apple Silicon ONLY (runs via Rosetta 2). The native arm64 static builds (osxexperts/martin-riedl) omit librubberband, so Retune's pitch-shift step has no rubberband filter there. Used solely by lib/retune.py; all other ffmpeg use stays on the native arm64 binary. Same evermeet build as ffmpeg_macos_x64.", + "url": "https://evermeet.cx/ffmpeg/ffmpeg-8.1.1.zip", + "sha256": "4610988e2f54c243c50da73a09e4e2c36d9bb77546f9aa6c84cb328dcb1a98c1" + } + } +} diff --git a/.claude/skills/speckit-analyze/SKILL.md b/.claude/skills/speckit-analyze/SKILL.md new file mode 100644 index 0000000..58f2348 --- /dev/null +++ b/.claude/skills/speckit-analyze/SKILL.md @@ -0,0 +1,260 @@ +--- +name: "speckit-analyze" +description: "Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation." +argument-hint: "Optional focus areas for analysis" +compatibility: "Requires spec-kit project structure with .specify/ directory" +metadata: + author: "github-spec-kit" + source: "templates/commands/analyze.md" +user-invocable: true +disable-model-invocation: false +--- + + +## User Input + +```text +$ARGUMENTS +``` + +You **MUST** consider the user input before proceeding (if not empty). + +## Pre-Execution Checks + +**Check for extension hooks (before analysis)**: +- Check if `.specify/extensions.yml` exists in the project root. +- If it exists, read it and look for entries under the `hooks.before_analyze` key +- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally +- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default. +- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions: + - If the hook has no `condition` field, or it is null/empty, treat the hook as executable + - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation +- When constructing slash commands from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`. +- For each executable hook, output the following based on its `optional` flag: + - **Optional hook** (`optional: true`): + ``` + ## Extension Hooks + + **Optional Pre-Hook**: {extension} + Command: `/{command}` + Description: {description} + + Prompt: {prompt} + To execute: `/{command}` + ``` + - **Mandatory hook** (`optional: false`): + ``` + ## Extension Hooks + + **Automatic Pre-Hook**: {extension} + Executing: `/{command}` + EXECUTE_COMMAND: {command} + + Wait for the result of the hook command before proceeding to the Goal. + ``` +- If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently + +## Goal + +Identify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (`spec.md`, `plan.md`, `tasks.md`) before implementation. This command MUST run only after `/speckit-tasks` has successfully produced a complete `tasks.md`. + +## Operating Constraints + +**STRICTLY READ-ONLY**: Do **not** modify any files. Output a structured analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually). + +**Constitution Authority**: The project constitution (`.specify/memory/constitution.md`) is **non-negotiable** within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjustment of the spec, plan, or tasks—not dilution, reinterpretation, or silent ignoring of the principle. If a principle itself needs to change, that must occur in a separate, explicit constitution update outside `/speckit-analyze`. + +## Execution Steps + +### 1. Initialize Analysis Context + +Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths: + +- SPEC = FEATURE_DIR/spec.md +- PLAN = FEATURE_DIR/plan.md +- TASKS = FEATURE_DIR/tasks.md + +Abort with an error message if any required file is missing (instruct the user to run missing prerequisite command). +For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot"). + +### 2. Load Artifacts (Progressive Disclosure) + +Load only the minimal necessary context from each artifact: + +**From spec.md:** + +- Overview/Context +- Functional Requirements +- Success Criteria (measurable outcomes — e.g., performance, security, availability, user success, business impact) +- User Stories +- Edge Cases (if present) + +**From plan.md:** + +- Architecture/stack choices +- Data Model references +- Phases +- Technical constraints + +**From tasks.md:** + +- Task IDs +- Descriptions +- Phase grouping +- Parallel markers [P] +- Referenced file paths + +**From constitution:** + +- Load `.specify/memory/constitution.md` for principle validation + +### 3. Build Semantic Models + +Create internal representations (do not include raw artifacts in output): + +- **Requirements inventory**: For each Functional Requirement (FR-###) and Success Criterion (SC-###), record a stable key. Use the explicit FR-/SC- identifier as the primary key when present, and optionally also derive an imperative-phrase slug for readability (e.g., "User can upload file" → `user-can-upload-file`). Include only Success Criteria items that require buildable work (e.g., load-testing infrastructure, security audit tooling), and exclude post-launch outcome metrics and business KPIs (e.g., "Reduce support tickets by 50%"). +- **User story/action inventory**: Discrete user actions with acceptance criteria +- **Task coverage mapping**: Map each task to one or more requirements or stories (inference by keyword / explicit reference patterns like IDs or key phrases) +- **Constitution rule set**: Extract principle names and MUST/SHOULD normative statements + +### 4. Detection Passes (Token-Efficient Analysis) + +Focus on high-signal findings. Limit to 50 findings total; aggregate remainder in overflow summary. + +#### A. Duplication Detection + +- Identify near-duplicate requirements +- Mark lower-quality phrasing for consolidation + +#### B. Ambiguity Detection + +- Flag vague adjectives (fast, scalable, secure, intuitive, robust) lacking measurable criteria +- Flag unresolved placeholders (TODO, TKTK, ???, ``, etc.) + +#### C. Underspecification + +- Requirements with verbs but missing object or measurable outcome +- User stories missing acceptance criteria alignment +- Tasks referencing files or components not defined in spec/plan + +#### D. Constitution Alignment + +- Any requirement or plan element conflicting with a MUST principle +- Missing mandated sections or quality gates from constitution + +#### E. Coverage Gaps + +- Requirements with zero associated tasks +- Tasks with no mapped requirement/story +- Success Criteria requiring buildable work (performance, security, availability) not reflected in tasks + +#### F. Inconsistency + +- Terminology drift (same concept named differently across files) +- Data entities referenced in plan but absent in spec (or vice versa) +- Task ordering contradictions (e.g., integration tasks before foundational setup tasks without dependency note) +- Conflicting requirements (e.g., one requires Next.js while other specifies Vue) + +### 5. Severity Assignment + +Use this heuristic to prioritize findings: + +- **CRITICAL**: Violates constitution MUST, missing core spec artifact, or requirement with zero coverage that blocks baseline functionality +- **HIGH**: Duplicate or conflicting requirement, ambiguous security/performance attribute, untestable acceptance criterion +- **MEDIUM**: Terminology drift, missing non-functional task coverage, underspecified edge case +- **LOW**: Style/wording improvements, minor redundancy not affecting execution order + +### 6. Produce Compact Analysis Report + +Output a Markdown report (no file writes) with the following structure: + +## Specification Analysis Report + +| ID | Category | Severity | Location(s) | Summary | Recommendation | +|----|----------|----------|-------------|---------|----------------| +| A1 | Duplication | HIGH | spec.md:L120-134 | Two similar requirements ... | Merge phrasing; keep clearer version | + +(Add one row per finding; generate stable IDs prefixed by category initial.) + +**Coverage Summary Table:** + +| Requirement Key | Has Task? | Task IDs | Notes | +|-----------------|-----------|----------|-------| + +**Constitution Alignment Issues:** (if any) + +**Unmapped Tasks:** (if any) + +**Metrics:** + +- Total Requirements +- Total Tasks +- Coverage % (requirements with >=1 task) +- Ambiguity Count +- Duplication Count +- Critical Issues Count + +### 7. Provide Next Actions + +At end of report, output a concise Next Actions block: + +- If CRITICAL issues exist: Recommend resolving before `/speckit-implement` +- If only LOW/MEDIUM: User may proceed, but provide improvement suggestions +- Provide explicit command suggestions: e.g., "Run /speckit-specify with refinement", "Run /speckit-plan to adjust architecture", "Manually edit tasks.md to add coverage for 'performance-metrics'" + +### 8. Offer Remediation + +Ask the user: "Would you like me to suggest concrete remediation edits for the top N issues?" (Do NOT apply them automatically.) + +### 9. Check for extension hooks + +After reporting, check if `.specify/extensions.yml` exists in the project root. +- If it exists, read it and look for entries under the `hooks.after_analyze` key +- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally +- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default. +- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions: + - If the hook has no `condition` field, or it is null/empty, treat the hook as executable + - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation +- When constructing slash commands from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`. +- For each executable hook, output the following based on its `optional` flag: + - **Optional hook** (`optional: true`): + ``` + ## Extension Hooks + + **Optional Hook**: {extension} + Command: `/{command}` + Description: {description} + + Prompt: {prompt} + To execute: `/{command}` + ``` + - **Mandatory hook** (`optional: false`): + ``` + ## Extension Hooks + + **Automatic Hook**: {extension} + Executing: `/{command}` + EXECUTE_COMMAND: {command} + ``` +- If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently + +## Operating Principles + +### Context Efficiency + +- **Minimal high-signal tokens**: Focus on actionable findings, not exhaustive documentation +- **Progressive disclosure**: Load artifacts incrementally; don't dump all content into analysis +- **Token-efficient output**: Limit findings table to 50 rows; summarize overflow +- **Deterministic results**: Rerunning without changes should produce consistent IDs and counts + +### Analysis Guidelines + +- **NEVER modify files** (this is read-only analysis) +- **NEVER hallucinate missing sections** (if absent, report them accurately) +- **Prioritize constitution violations** (these are always CRITICAL) +- **Use examples over exhaustive rules** (cite specific instances, not generic patterns) +- **Report zero issues gracefully** (emit success report with coverage statistics) + +## Context + +$ARGUMENTS diff --git a/.claude/skills/speckit-checklist/SKILL.md b/.claude/skills/speckit-checklist/SKILL.md new file mode 100644 index 0000000..4b45697 --- /dev/null +++ b/.claude/skills/speckit-checklist/SKILL.md @@ -0,0 +1,372 @@ +--- +name: "speckit-checklist" +description: "Generate a custom checklist for the current feature based on user requirements." +argument-hint: "Domain or focus area for the checklist" +compatibility: "Requires spec-kit project structure with .specify/ directory" +metadata: + author: "github-spec-kit" + source: "templates/commands/checklist.md" +user-invocable: true +disable-model-invocation: false +--- + + +## Checklist Purpose: "Unit Tests for English" + +**CRITICAL CONCEPT**: Checklists are **UNIT TESTS FOR REQUIREMENTS WRITING** - they validate the quality, clarity, and completeness of requirements in a given domain. + +**NOT for verification/testing**: + +- ❌ NOT "Verify the button clicks correctly" +- ❌ NOT "Test error handling works" +- ❌ NOT "Confirm the API returns 200" +- ❌ NOT checking if code/implementation matches the spec + +**FOR requirements quality validation**: + +- ✅ "Are visual hierarchy requirements defined for all card types?" (completeness) +- ✅ "Is 'prominent display' quantified with specific sizing/positioning?" (clarity) +- ✅ "Are hover state requirements consistent across all interactive elements?" (consistency) +- ✅ "Are accessibility requirements defined for keyboard navigation?" (coverage) +- ✅ "Does the spec define what happens when logo image fails to load?" (edge cases) + +**Metaphor**: If your spec is code written in English, the checklist is its unit test suite. You're testing whether the requirements are well-written, complete, unambiguous, and ready for implementation - NOT whether the implementation works. + +## User Input + +```text +$ARGUMENTS +``` + +You **MUST** consider the user input before proceeding (if not empty). + +## Pre-Execution Checks + +**Check for extension hooks (before checklist generation)**: +- Check if `.specify/extensions.yml` exists in the project root. +- If it exists, read it and look for entries under the `hooks.before_checklist` key +- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally +- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default. +- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions: + - If the hook has no `condition` field, or it is null/empty, treat the hook as executable + - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation +- When constructing slash commands from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`. +- For each executable hook, output the following based on its `optional` flag: + - **Optional hook** (`optional: true`): + ``` + ## Extension Hooks + + **Optional Pre-Hook**: {extension} + Command: `/{command}` + Description: {description} + + Prompt: {prompt} + To execute: `/{command}` + ``` + - **Mandatory hook** (`optional: false`): + ``` + ## Extension Hooks + + **Automatic Pre-Hook**: {extension} + Executing: `/{command}` + EXECUTE_COMMAND: {command} + + Wait for the result of the hook command before proceeding to the Execution Steps. + ``` +- If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently + +## Execution Steps + +1. **Setup**: Run `.specify/scripts/bash/check-prerequisites.sh --json` from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS list. + - All file paths must be absolute. + - For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot"). + +2. **Clarify intent (dynamic)**: Derive up to THREE initial contextual clarifying questions (no pre-baked catalog). They MUST: + - Be generated from the user's phrasing + extracted signals from spec/plan/tasks + - Only ask about information that materially changes checklist content + - Be skipped individually if already unambiguous in `$ARGUMENTS` + - Prefer precision over breadth + + Generation algorithm: + 1. Extract signals: feature domain keywords (e.g., auth, latency, UX, API), risk indicators ("critical", "must", "compliance"), stakeholder hints ("QA", "review", "security team"), and explicit deliverables ("a11y", "rollback", "contracts"). + 2. Cluster signals into candidate focus areas (max 4) ranked by relevance. + 3. Identify probable audience & timing (author, reviewer, QA, release) if not explicit. + 4. Detect missing dimensions: scope breadth, depth/rigor, risk emphasis, exclusion boundaries, measurable acceptance criteria. + 5. Formulate questions chosen from these archetypes: + - Scope refinement (e.g., "Should this include integration touchpoints with X and Y or stay limited to local module correctness?") + - Risk prioritization (e.g., "Which of these potential risk areas should receive mandatory gating checks?") + - Depth calibration (e.g., "Is this a lightweight pre-commit sanity list or a formal release gate?") + - Audience framing (e.g., "Will this be used by the author only or peers during PR review?") + - Boundary exclusion (e.g., "Should we explicitly exclude performance tuning items this round?") + - Scenario class gap (e.g., "No recovery flows detected—are rollback / partial failure paths in scope?") + + Question formatting rules: + - If presenting options, generate a compact table with columns: Option | Candidate | Why It Matters + - Limit to A–E options maximum; omit table if a free-form answer is clearer + - Never ask the user to restate what they already said + - Avoid speculative categories (no hallucination). If uncertain, ask explicitly: "Confirm whether X belongs in scope." + + Defaults when interaction impossible: + - Depth: Standard + - Audience: Reviewer (PR) if code-related; Author otherwise + - Focus: Top 2 relevance clusters + + Output the questions (label Q1/Q2/Q3). After answers: if ≥2 scenario classes (Alternate / Exception / Recovery / Non-Functional domain) remain unclear, you MAY ask up to TWO more targeted follow‑ups (Q4/Q5) with a one-line justification each (e.g., "Unresolved recovery path risk"). Do not exceed five total questions. Skip escalation if user explicitly declines more. + +3. **Understand user request**: Combine `$ARGUMENTS` + clarifying answers: + - Derive checklist theme (e.g., security, review, deploy, ux) + - Consolidate explicit must-have items mentioned by user + - Map focus selections to category scaffolding + - Infer any missing context from spec/plan/tasks (do NOT hallucinate) + +4. **Load feature context**: Read from FEATURE_DIR: + - spec.md: Feature requirements and scope + - plan.md (if exists): Technical details, dependencies + - tasks.md (if exists): Implementation tasks + + **Context Loading Strategy**: + - Load only necessary portions relevant to active focus areas (avoid full-file dumping) + - Prefer summarizing long sections into concise scenario/requirement bullets + - Use progressive disclosure: add follow-on retrieval only if gaps detected + - If source docs are large, generate interim summary items instead of embedding raw text + +5. **Generate checklist** - Create "Unit Tests for Requirements": + - Create `FEATURE_DIR/checklists/` directory if it doesn't exist + - Generate unique checklist filename: + - Use short, descriptive name based on domain (e.g., `ux.md`, `api.md`, `security.md`) + - Format: `[domain].md` + - File handling behavior: + - If file does NOT exist: Create new file and number items starting from CHK001 + - If file exists: Append new items to existing file, continuing from the last CHK ID (e.g., if last item is CHK015, start new items at CHK016) + - Never delete or replace existing checklist content - always preserve and append + + **CORE PRINCIPLE - Test the Requirements, Not the Implementation**: + Every checklist item MUST evaluate the REQUIREMENTS THEMSELVES for: + - **Completeness**: Are all necessary requirements present? + - **Clarity**: Are requirements unambiguous and specific? + - **Consistency**: Do requirements align with each other? + - **Measurability**: Can requirements be objectively verified? + - **Coverage**: Are all scenarios/edge cases addressed? + + **Category Structure** - Group items by requirement quality dimensions: + - **Requirement Completeness** (Are all necessary requirements documented?) + - **Requirement Clarity** (Are requirements specific and unambiguous?) + - **Requirement Consistency** (Do requirements align without conflicts?) + - **Acceptance Criteria Quality** (Are success criteria measurable?) + - **Scenario Coverage** (Are all flows/cases addressed?) + - **Edge Case Coverage** (Are boundary conditions defined?) + - **Non-Functional Requirements** (Performance, Security, Accessibility, etc. - are they specified?) + - **Dependencies & Assumptions** (Are they documented and validated?) + - **Ambiguities & Conflicts** (What needs clarification?) + + **HOW TO WRITE CHECKLIST ITEMS - "Unit Tests for English"**: + + ❌ **WRONG** (Testing implementation): + - "Verify landing page displays 3 episode cards" + - "Test hover states work on desktop" + - "Confirm logo click navigates home" + + ✅ **CORRECT** (Testing requirements quality): + - "Are the exact number and layout of featured episodes specified?" [Completeness] + - "Is 'prominent display' quantified with specific sizing/positioning?" [Clarity] + - "Are hover state requirements consistent across all interactive elements?" [Consistency] + - "Are keyboard navigation requirements defined for all interactive UI?" [Coverage] + - "Is the fallback behavior specified when logo image fails to load?" [Edge Cases] + - "Are loading states defined for asynchronous episode data?" [Completeness] + - "Does the spec define visual hierarchy for competing UI elements?" [Clarity] + + **ITEM STRUCTURE**: + Each item should follow this pattern: + - Question format asking about requirement quality + - Focus on what's WRITTEN (or not written) in the spec/plan + - Include quality dimension in brackets [Completeness/Clarity/Consistency/etc.] + - Reference spec section `[Spec §X.Y]` when checking existing requirements + - Use `[Gap]` marker when checking for missing requirements + + **EXAMPLES BY QUALITY DIMENSION**: + + Completeness: + - "Are error handling requirements defined for all API failure modes? [Gap]" + - "Are accessibility requirements specified for all interactive elements? [Completeness]" + - "Are mobile breakpoint requirements defined for responsive layouts? [Gap]" + + Clarity: + - "Is 'fast loading' quantified with specific timing thresholds? [Clarity, Spec §NFR-2]" + - "Are 'related episodes' selection criteria explicitly defined? [Clarity, Spec §FR-5]" + - "Is 'prominent' defined with measurable visual properties? [Ambiguity, Spec §FR-4]" + + Consistency: + - "Do navigation requirements align across all pages? [Consistency, Spec §FR-10]" + - "Are card component requirements consistent between landing and detail pages? [Consistency]" + + Coverage: + - "Are requirements defined for zero-state scenarios (no episodes)? [Coverage, Edge Case]" + - "Are concurrent user interaction scenarios addressed? [Coverage, Gap]" + - "Are requirements specified for partial data loading failures? [Coverage, Exception Flow]" + + Measurability: + - "Are visual hierarchy requirements measurable/testable? [Acceptance Criteria, Spec §FR-1]" + - "Can 'balanced visual weight' be objectively verified? [Measurability, Spec §FR-2]" + + **Scenario Classification & Coverage** (Requirements Quality Focus): + - Check if requirements exist for: Primary, Alternate, Exception/Error, Recovery, Non-Functional scenarios + - For each scenario class, ask: "Are [scenario type] requirements complete, clear, and consistent?" + - If scenario class missing: "Are [scenario type] requirements intentionally excluded or missing? [Gap]" + - Include resilience/rollback when state mutation occurs: "Are rollback requirements defined for migration failures? [Gap]" + + **Traceability Requirements**: + - MINIMUM: ≥80% of items MUST include at least one traceability reference + - Each item should reference: spec section `[Spec §X.Y]`, or use markers: `[Gap]`, `[Ambiguity]`, `[Conflict]`, `[Assumption]` + - If no ID system exists: "Is a requirement & acceptance criteria ID scheme established? [Traceability]" + + **Surface & Resolve Issues** (Requirements Quality Problems): + Ask questions about the requirements themselves: + - Ambiguities: "Is the term 'fast' quantified with specific metrics? [Ambiguity, Spec §NFR-1]" + - Conflicts: "Do navigation requirements conflict between §FR-10 and §FR-10a? [Conflict]" + - Assumptions: "Is the assumption of 'always available podcast API' validated? [Assumption]" + - Dependencies: "Are external podcast API requirements documented? [Dependency, Gap]" + - Missing definitions: "Is 'visual hierarchy' defined with measurable criteria? [Gap]" + + **Content Consolidation**: + - Soft cap: If raw candidate items > 40, prioritize by risk/impact + - Merge near-duplicates checking the same requirement aspect + - If >5 low-impact edge cases, create one item: "Are edge cases X, Y, Z addressed in requirements? [Coverage]" + + **🚫 ABSOLUTELY PROHIBITED** - These make it an implementation test, not a requirements test: + - ❌ Any item starting with "Verify", "Test", "Confirm", "Check" + implementation behavior + - ❌ References to code execution, user actions, system behavior + - ❌ "Displays correctly", "works properly", "functions as expected" + - ❌ "Click", "navigate", "render", "load", "execute" + - ❌ Test cases, test plans, QA procedures + - ❌ Implementation details (frameworks, APIs, algorithms) + + **✅ REQUIRED PATTERNS** - These test requirements quality: + - ✅ "Are [requirement type] defined/specified/documented for [scenario]?" + - ✅ "Is [vague term] quantified/clarified with specific criteria?" + - ✅ "Are requirements consistent between [section A] and [section B]?" + - ✅ "Can [requirement] be objectively measured/verified?" + - ✅ "Are [edge cases/scenarios] addressed in requirements?" + - ✅ "Does the spec define [missing aspect]?" + +6. **Structure Reference**: Generate the checklist following the canonical template in `.specify/templates/checklist-template.md` for title, meta section, category headings, and ID formatting. If template is unavailable, use: H1 title, purpose/created meta lines, `##` category sections containing `- [ ] CHK### ` lines with globally incrementing IDs starting at CHK001. + +7. **Report**: Output full path to checklist file, item count, and summarize whether the run created a new file or appended to an existing one. Summarize: + - Focus areas selected + - Depth level + - Actor/timing + - Any explicit user-specified must-have items incorporated + +**Important**: Each `/speckit-checklist` command invocation uses a short, descriptive checklist filename and either creates a new file or appends to an existing one. This allows: + +- Multiple checklists of different types (e.g., `ux.md`, `test.md`, `security.md`) +- Simple, memorable filenames that indicate checklist purpose +- Easy identification and navigation in the `checklists/` folder + +To avoid clutter, use descriptive types and clean up obsolete checklists when done. + +## Example Checklist Types & Sample Items + +**UX Requirements Quality:** `ux.md` + +Sample items (testing the requirements, NOT the implementation): + +- "Are visual hierarchy requirements defined with measurable criteria? [Clarity, Spec §FR-1]" +- "Is the number and positioning of UI elements explicitly specified? [Completeness, Spec §FR-1]" +- "Are interaction state requirements (hover, focus, active) consistently defined? [Consistency]" +- "Are accessibility requirements specified for all interactive elements? [Coverage, Gap]" +- "Is fallback behavior defined when images fail to load? [Edge Case, Gap]" +- "Can 'prominent display' be objectively measured? [Measurability, Spec §FR-4]" + +**API Requirements Quality:** `api.md` + +Sample items: + +- "Are error response formats specified for all failure scenarios? [Completeness]" +- "Are rate limiting requirements quantified with specific thresholds? [Clarity]" +- "Are authentication requirements consistent across all endpoints? [Consistency]" +- "Are retry/timeout requirements defined for external dependencies? [Coverage, Gap]" +- "Is versioning strategy documented in requirements? [Gap]" + +**Performance Requirements Quality:** `performance.md` + +Sample items: + +- "Are performance requirements quantified with specific metrics? [Clarity]" +- "Are performance targets defined for all critical user journeys? [Coverage]" +- "Are performance requirements under different load conditions specified? [Completeness]" +- "Can performance requirements be objectively measured? [Measurability]" +- "Are degradation requirements defined for high-load scenarios? [Edge Case, Gap]" + +**Security Requirements Quality:** `security.md` + +Sample items: + +- "Are authentication requirements specified for all protected resources? [Coverage]" +- "Are data protection requirements defined for sensitive information? [Completeness]" +- "Is the threat model documented and requirements aligned to it? [Traceability]" +- "Are security requirements consistent with compliance obligations? [Consistency]" +- "Are security failure/breach response requirements defined? [Gap, Exception Flow]" + +## Anti-Examples: What NOT To Do + +**❌ WRONG - These test implementation, not requirements:** + +```markdown +- [ ] CHK001 - Verify landing page displays 3 episode cards [Spec §FR-001] +- [ ] CHK002 - Test hover states work correctly on desktop [Spec §FR-003] +- [ ] CHK003 - Confirm logo click navigates to home page [Spec §FR-010] +- [ ] CHK004 - Check that related episodes section shows 3-5 items [Spec §FR-005] +``` + +**✅ CORRECT - These test requirements quality:** + +```markdown +- [ ] CHK001 - Are the number and layout of featured episodes explicitly specified? [Completeness, Spec §FR-001] +- [ ] CHK002 - Are hover state requirements consistently defined for all interactive elements? [Consistency, Spec §FR-003] +- [ ] CHK003 - Are navigation requirements clear for all clickable brand elements? [Clarity, Spec §FR-010] +- [ ] CHK004 - Is the selection criteria for related episodes documented? [Gap, Spec §FR-005] +- [ ] CHK005 - Are loading state requirements defined for asynchronous episode data? [Gap] +- [ ] CHK006 - Can "visual hierarchy" requirements be objectively measured? [Measurability, Spec §FR-001] +``` + +**Key Differences:** + +- Wrong: Tests if the system works correctly +- Correct: Tests if the requirements are written correctly +- Wrong: Verification of behavior +- Correct: Validation of requirement quality +- Wrong: "Does it do X?" +- Correct: "Is X clearly specified?" + +## Post-Execution Checks + +**Check for extension hooks (after checklist generation)**: +Check if `.specify/extensions.yml` exists in the project root. +- If it exists, read it and look for entries under the `hooks.after_checklist` key +- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally +- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default. +- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions: + - If the hook has no `condition` field, or it is null/empty, treat the hook as executable + - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation +- When constructing slash commands from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`. +- For each executable hook, output the following based on its `optional` flag: + - **Optional hook** (`optional: true`): + ``` + ## Extension Hooks + + **Optional Hook**: {extension} + Command: `/{command}` + Description: {description} + + Prompt: {prompt} + To execute: `/{command}` + ``` + - **Mandatory hook** (`optional: false`): + ``` + ## Extension Hooks + + **Automatic Hook**: {extension} + Executing: `/{command}` + EXECUTE_COMMAND: {command} + ``` +- If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently diff --git a/.claude/skills/speckit-clarify/SKILL.md b/.claude/skills/speckit-clarify/SKILL.md new file mode 100644 index 0000000..cda85c6 --- /dev/null +++ b/.claude/skills/speckit-clarify/SKILL.md @@ -0,0 +1,254 @@ +--- +name: "speckit-clarify" +description: "Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec." +argument-hint: "Optional areas to clarify in the spec" +compatibility: "Requires spec-kit project structure with .specify/ directory" +metadata: + author: "github-spec-kit" + source: "templates/commands/clarify.md" +user-invocable: true +disable-model-invocation: false +--- + + +## User Input + +```text +$ARGUMENTS +``` + +You **MUST** consider the user input before proceeding (if not empty). + +## Pre-Execution Checks + +**Check for extension hooks (before clarification)**: +- Check if `.specify/extensions.yml` exists in the project root. +- If it exists, read it and look for entries under the `hooks.before_clarify` key +- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally +- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default. +- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions: + - If the hook has no `condition` field, or it is null/empty, treat the hook as executable + - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation +- When constructing slash commands from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`. +- For each executable hook, output the following based on its `optional` flag: + - **Optional hook** (`optional: true`): + ``` + ## Extension Hooks + + **Optional Pre-Hook**: {extension} + Command: `/{command}` + Description: {description} + + Prompt: {prompt} + To execute: `/{command}` + ``` + - **Mandatory hook** (`optional: false`): + ``` + ## Extension Hooks + + **Automatic Pre-Hook**: {extension} + Executing: `/{command}` + EXECUTE_COMMAND: {command} + + Wait for the result of the hook command before proceeding to the Outline. + ``` +- If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently + +## Outline + +Goal: Detect and reduce ambiguity or missing decision points in the active feature specification and record the clarifications directly in the spec file. + +Note: This clarification workflow is expected to run (and be completed) BEFORE invoking `/speckit-plan`. If the user explicitly states they are skipping clarification (e.g., exploratory spike), you may proceed, but must warn that downstream rework risk increases. + +Execution steps: + +1. Run `.specify/scripts/bash/check-prerequisites.sh --json --paths-only` from repo root **once** (combined `--json --paths-only` mode / `-Json -PathsOnly`). Parse minimal JSON payload fields: + - `FEATURE_DIR` + - `FEATURE_SPEC` + - (Optionally capture `IMPL_PLAN`, `TASKS` for future chained flows.) + - If JSON parsing fails, abort and instruct user to re-run `/speckit-specify` or verify feature branch environment. + - For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot"). + +2. Load the current spec file. Perform a structured ambiguity & coverage scan using this taxonomy. For each category, mark status: Clear / Partial / Missing. Produce an internal coverage map used for prioritization (do not output raw map unless no questions will be asked). + + Functional Scope & Behavior: + - Core user goals & success criteria + - Explicit out-of-scope declarations + - User roles / personas differentiation + + Domain & Data Model: + - Entities, attributes, relationships + - Identity & uniqueness rules + - Lifecycle/state transitions + - Data volume / scale assumptions + + Interaction & UX Flow: + - Critical user journeys / sequences + - Error/empty/loading states + - Accessibility or localization notes + + Non-Functional Quality Attributes: + - Performance (latency, throughput targets) + - Scalability (horizontal/vertical, limits) + - Reliability & availability (uptime, recovery expectations) + - Observability (logging, metrics, tracing signals) + - Security & privacy (authN/Z, data protection, threat assumptions) + - Compliance / regulatory constraints (if any) + + Integration & External Dependencies: + - External services/APIs and failure modes + - Data import/export formats + - Protocol/versioning assumptions + + Edge Cases & Failure Handling: + - Negative scenarios + - Rate limiting / throttling + - Conflict resolution (e.g., concurrent edits) + + Constraints & Tradeoffs: + - Technical constraints (language, storage, hosting) + - Explicit tradeoffs or rejected alternatives + + Terminology & Consistency: + - Canonical glossary terms + - Avoided synonyms / deprecated terms + + Completion Signals: + - Acceptance criteria testability + - Measurable Definition of Done style indicators + + Misc / Placeholders: + - TODO markers / unresolved decisions + - Ambiguous adjectives ("robust", "intuitive") lacking quantification + + For each category with Partial or Missing status, add a candidate question opportunity unless: + - Clarification would not materially change implementation or validation strategy + - Information is better deferred to planning phase (note internally) + +3. Generate (internally) a prioritized queue of candidate clarification questions (maximum 5). Do NOT output them all at once. Apply these constraints: + - Maximum of 5 total questions across the whole session. + - Each question must be answerable with EITHER: + - A short multiple‑choice selection (2–5 distinct, mutually exclusive options), OR + - A one-word / short‑phrase answer (explicitly constrain: "Answer in <=5 words"). + - Only include questions whose answers materially impact architecture, data modeling, task decomposition, test design, UX behavior, operational readiness, or compliance validation. + - Ensure category coverage balance: attempt to cover the highest impact unresolved categories first; avoid asking two low-impact questions when a single high-impact area (e.g., security posture) is unresolved. + - Exclude questions already answered, trivial stylistic preferences, or plan-level execution details (unless blocking correctness). + - Favor clarifications that reduce downstream rework risk or prevent misaligned acceptance tests. + - If more than 5 categories remain unresolved, select the top 5 by (Impact * Uncertainty) heuristic. + +4. Sequential questioning loop (interactive): + - Present EXACTLY ONE question at a time. + - For multiple‑choice questions: + - **Analyze all options** and determine the **most suitable option** based on: + - Best practices for the project type + - Common patterns in similar implementations + - Risk reduction (security, performance, maintainability) + - Alignment with any explicit project goals or constraints visible in the spec + - Present your **recommended option prominently** at the top with clear reasoning (1-2 sentences explaining why this is the best choice). + - Format as: `**Recommended:** Option [X] - ` + - Then render all options as a Markdown table: + + | Option | Description | + |--------|-------------| + | A |