sudacode/SubMiner
1
0
Fork 0
mirror of https://github.com/ksyasuda/SubMiner.git synced 2026-03-01 06:22:44 -08:00
Code Issues Packages Projects Releases Wiki Activity

chore(workflow): sync backlog state and subagent coordination

Browse Source 
Capture backlog task lifecycle updates, archive TASK-34, and add planning artifacts for recent config work. Update docs sweep scripts and AGENTS guidance to use sharded docs/subagents coordination metadata.
This commit is contained in:
Kyle Yasuda
2026-02-19 00:49:23 -08:00
parent 9e6d039a32
commit 9384d67b8e
14 changed files with 466 additions and 157 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
backlog/tasks/task-84 - Gate-feature-dependent-keybindings-behind-config-flags.md Normal file
View File

@@ -0,0 +1,25 @@
---
id: TASK-84
title: Gate feature-dependent keybindings behind config flags
status: To Do
assignee: []
created_date: '2026-02-19 08:41'
labels: []
dependencies: []
priority: medium
---
## Description
<!-- SECTION:DESCRIPTION:BEGIN -->
Ensure feature-specific keybindings only work when their related feature is enabled in configuration, so users do not trigger unavailable behavior and the app avoids loading integrations that are disabled (for example Jellyfin).
<!-- SECTION:DESCRIPTION:END -->
## Acceptance Criteria
<!-- AC:BEGIN -->
- [ ] #1 Feature-dependent keybindings are effectively disabled when their corresponding feature flag/config is off, with no user-facing error dialogs.
- [ ] #2 When a feature is disabled in config, its related integration code is not loaded or initialized during startup (including Jellyfin as a concrete case).
- [ ] #3 When a feature is enabled, existing keybinding behavior continues to work as expected.
- [ ] #4 Automated tests cover enabled and disabled paths for keybinding gating and disabled-integration loading behavior.
- [ ] #5 User-facing docs/config guidance explain that feature keybindings require the corresponding feature to be enabled.
<!-- AC:END -->