Document AUR install flow and add backlog planning artifacts

- Add Arch Linux `subminer-bin` install instructions to README and docs-site installation guide
- Add Hyprland troubleshooting guidance for transparency and global shortcut passthrough
- Add TASK-159..164 backlog records and skill design plans; include changelog fragment
- Apply formatting-only update to `src/release-workflow.test.ts`

docs/plans/2026-03-10-subminer-change-verification-design.md

@@ -0,0 +1,105 @@
+# SubMiner Change Verification Skill Design
+
+**Date:** 2026-03-10
+**Status:** Approved
+
+## Goal
+
+Create a SubMiner-specific skill that agents can use to verify code changes with automated checks. The skill must support both targeted regression testing during debugging and pre-handoff verification before final response.
+
+## Skill Contract
+
+- **Name:** `subminer-change-verification`
+- **Trigger:** Use when working in the SubMiner repo and you need to verify code changes actually work, especially for launcher, mpv, plugin, overlay, runtime, Electron, or env-sensitive behavior.
+- **Default posture:** cheap-first; prefer repo-native tests and narrow lanes before broader or GUI-dependent verification.
+- **Outputs:**
+  - verification summary
+  - exact commands run
+  - artifact paths for logs, captured summaries, and preserved temp state on failures
+  - skipped lanes and blockers
+- **Non-goals:**
+  - replacing the repo's native tests
+  - launching real GUI apps for every change
+  - default visual regression or pixel-diff workflows
+
+## Lane Selection
+
+The skill chooses lanes from the diff or explicit file list.
+
+- **`docs`**
+  - For `docs-site/`, `docs/`, and similar documentation-only changes.
+  - Prefer `bun run docs:test` and `bun run docs:build`.
+- **`config`**
+  - For `src/config/`, config example generation/verification paths, and config-template-sensitive changes.
+  - Prefer `bun run test:config`.
+- **`core`**
+  - For general source-level changes where type safety and the fast maintained lane are the best cheap signal.
+  - Prefer `bun run typecheck` and `bun run test:fast`.
+- **`launcher-plugin`**
+  - For `launcher/`, `plugin/subminer/`, plugin gating scripts, and wrapper/mpv routing work.
+  - Prefer `bun run test:launcher:smoke:src` and `bun run test:plugin:src`.
+- **`runtime-compat`**
+  - For runtime/composition/bundled behavior where dist-sensitive validation matters.
+  - Prefer `bun run build`, `bun run test:runtime:compat`, and `bun run test:smoke:dist`.
+- **`real-gui`**
+  - Reserved for cases where actual Electron/mpv/window behavior must be validated.
+  - Not part of the default lane set; the classifier marks these changes as candidates so the agent can escalate deliberately.
+
+## Escalation Rules
+
+1. Start with the narrowest lane that credibly exercises the changed behavior.
+2. If a narrow lane fails in a way that suggests broader fallout, expand once.
+3. If a change touches launcher/mpv/plugin/runtime/overlay/window tracking paths, include the relevant specialized lanes before falling back to broad suites.
+4. Treat real GUI/mpv verification as opt-in escalation:
+   - use only when cheaper evidence is insufficient
+   - allow for platform/display/permission blockers
+   - report skipped/blocker states explicitly
+
+## Helper Script Design
+
+The skill uses two small shell helpers:
+
+- **`scripts/classify_subminer_diff.sh`**
+  - Accepts explicit paths or discovers local changes from git.
+  - Emits lane suggestions and flags in a simple line-oriented format.
+  - Marks real GUI-sensitive paths as `flag:real-gui-candidate` instead of forcing GUI execution.
+- **`scripts/verify_subminer_change.sh`**
+  - Creates an artifact directory under `.tmp/skill-verification/<timestamp>/`.
+  - Selects lanes from the classifier unless lanes are supplied explicitly.
+  - Runs repo-native commands in a stable order and captures stdout/stderr per step.
+  - Writes a compact `summary.json` and a human-readable `summary.txt`.
+  - Skips real GUI verification unless explicitly enabled.
+
+## Artifact Contract
+
+Each invocation should create:
+
+- `summary.json`
+- `summary.txt`
+- `classification.txt`
+- `env.txt`
+- `lanes.txt`
+- `steps.tsv`
+- `steps/<step>.stdout.log`
+- `steps/<step>.stderr.log`
+
+Failures should preserve the artifact directory and identify the exact failing command and log paths.
+
+## Agent Workflow
+
+1. Inspect changed files or requested area.
+2. Classify the change into verification lanes.
+3. Run the cheapest sufficient lane set.
+4. Escalate only if evidence is insufficient.
+5. Escalate to real GUI/mpv only for actual Electron/mpv/window behavior claims.
+6. Return a short report with:
+   - pass/fail/skipped per lane
+   - exact commands run
+   - artifact paths
+   - blockers/gaps
+
+## Initial Implementation Scope
+
+- Ship the skill entrypoint plus the classifier/verifier helpers.
+- Make real GUI verification an explicit future hook rather than a default workflow.
+- Verify the new skill locally with representative classifier output and artifact generation.

docs/plans/2026-03-10-subminer-scrum-master-design.md

@@ -0,0 +1,111 @@
+# SubMiner Scrum Master Skill Design
+
+**Date:** 2026-03-10
+**Status:** Approved
+
+## Goal
+
+Create a repo-local skill that can take incoming requests, bugs, or issues in the SubMiner repo, decide whether backlog tracking is warranted, create or update backlog work when appropriate, plan the implementation, dispatch one or more subagents, and ensure verification happens before handoff.
+
+## Skill Contract
+
+- **Name:** `subminer-scrum-master`
+- **Location:** `.agents/skills/subminer-scrum-master/`
+- **Use when:** the user gives a feature request, bug report, issue, refactor, or implementation ask in the SubMiner repo and the agent should own intake, planning, backlog hygiene, dispatch, and completion flow.
+- **Responsibilities:**
+  - assess whether backlog tracking is warranted
+  - if needed, search/update/create proper backlog structure
+  - write a plan before dispatching coding work
+  - choose sequential vs parallel execution
+  - assign explicit ownership to workers
+  - require verification before final handoff
+- **Limits:**
+  - not the default code implementer unless delegation would be wasteful
+  - no overlapping parallel write scopes
+  - no skipping planning before dispatch
+  - no skipping verification
+  - must pause for ambiguous, risky, or external side-effect work
+
+## Backlog Decision Rules
+
+Backlog use is conditional, not mandatory.
+
+- **Skip backlog when:**
+  - question only
+  - obvious mechanical edit
+  - tiny isolated change with no real planning
+- **Use backlog when:**
+  - implementation requires planning
+  - scope/approach needs decisions
+  - multiple phases or subsystems
+  - likely subagent dispatch
+  - work should remain traceable
+
+When backlog is used:
+- search first
+- update existing matching work when appropriate
+- otherwise create standalone task or parent task
+- use parent + subtasks for multi-part work
+- record the implementation plan before coding starts
+
+## Orchestration Policy
+
+The skill orchestrates; workers implement.
+
+- **No dispatch** for trivial/mechanical work
+- **Single worker** for focused single-scope work
+- **Parallel workers** only for clearly disjoint scopes
+- **Sequential flow** for shared files, runtime coupling, or unclear boundaries
+
+Every worker should receive:
+- owned files/modules
+- explicit reminder not to revert unrelated edits
+- requirement to report changed files, tests run, and blockers
+
+## Verification Policy
+
+Every nontrivial code task gets verification.
+
+- prefer `subminer-change-verification`
+- use cheap-first lanes
+- escalate only when needed
+- accept worker-run verification only if it is clearly relevant and sufficient
+- run a consolidating final verification pass when the scrum master needs stronger evidence
+
+## Representative Flows
+
+### Trivial fix, no backlog
+
+1. assess request as mechanical or narrowly reversible
+2. skip backlog
+3. keep a short internal plan
+4. implement directly or use one worker if helpful
+5. run targeted verification
+6. report concise summary
+
+### Single-task implementation
+
+1. search backlog
+2. create/update one task
+3. record plan
+4. dispatch one worker
+5. integrate result
+6. run verification
+7. update task and report outcome
+
+### Multi-part feature
+
+1. search backlog
+2. create/update parent task
+3. create subtasks for distinct deliverables/phases
+4. record sequencing in the plan
+5. dispatch workers only where write scopes do not overlap
+6. integrate
+7. run consolidated verification
+8. update task state and report outcome
+
+## V1 Scope
+
+- instruction-heavy `SKILL.md`
+- no helper scripts unless orchestration becomes too repetitive
+- strong coordination with existing Backlog workflow and `subminer-change-verification`