mirror of
https://github.com/ksyasuda/SubMiner.git
synced 2026-03-20 12:11:28 -07:00
sudacode
2f17859b7b
- 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`
69 lines
3.0 KiB
Markdown
69 lines
3.0 KiB
Markdown
---
|
|
id: TASK-164
|
|
title: Run maintained test gate and fix failing regressions
|
|
status: Done
|
|
assignee:
|
|
- Codex
|
|
created_date: '2026-03-11 08:52'
|
|
updated_date: '2026-03-11 08:54'
|
|
labels:
|
|
- maintenance
|
|
- testing
|
|
dependencies: []
|
|
references:
|
|
- /home/sudacode/projects/japanese/SubMiner/package.json
|
|
- /home/sudacode/projects/japanese/SubMiner/docs-site/development.md
|
|
- /home/sudacode/projects/japanese/SubMiner/docs-site/architecture.md
|
|
---
|
|
|
|
## Description
|
|
|
|
<!-- SECTION:DESCRIPTION:BEGIN -->
|
|
Execute the repo's maintained test verification flow, fix any regressions surfaced by those commands, and leave the requested test gate passing without disturbing unrelated in-progress work.
|
|
<!-- SECTION:DESCRIPTION:END -->
|
|
|
|
## Acceptance Criteria
|
|
<!-- AC:BEGIN -->
|
|
- [x] #1 The maintained test commands chosen for this pass are recorded in the task plan.
|
|
- [x] #2 Any test failures encountered in that gate are fixed in-scope with appropriate regression coverage when needed.
|
|
- [x] #3 The same maintained test gate passes after the fixes.
|
|
- [x] #4 Verification results, skips, and remaining risks are documented before handoff.
|
|
<!-- AC:END -->
|
|
|
|
## Implementation Plan
|
|
|
|
<!-- SECTION:PLAN:BEGIN -->
|
|
1. Run the maintained verification gate documented for local handoff: `bun run test:fast`, `bun run test:env`, `bun run build`, and `bun run test:smoke:dist`.
|
|
2. Stop at the first failing command, inspect the exact failure, and use a red/green loop with the smallest targeted failing test before writing any production-code fix.
|
|
3. Re-run the targeted failing test, then the original failing command, and continue through the remaining gate.
|
|
4. Record results, any skips, and residual risks before handoff.
|
|
<!-- SECTION:PLAN:END -->
|
|
|
|
## Implementation Notes
|
|
|
|
<!-- SECTION:NOTES:BEGIN -->
|
|
Using the docs-site recommended local gate as the maintained test/build verification flow for this request.
|
|
|
|
Ran `bun run test:fast` at 2026-03-11 01:52 PDT: passed.
|
|
|
|
Ran `bun run test:env` at 2026-03-11 01:53 PDT: passed.
|
|
|
|
Ran `bun run build` at 2026-03-11 01:53 PDT: passed.
|
|
|
|
Ran `bun run test:smoke:dist` at 2026-03-11 01:53 PDT: passed.
|
|
|
|
No failing tests surfaced in the maintained gate, so no production-code or test changes were required in this pass.
|
|
|
|
Working tree still includes unrelated user edits plus the previously-applied formatting change in `src/release-workflow.test.ts`; this task did not add new source changes.
|
|
<!-- SECTION:NOTES:END -->
|
|
|
|
## Final Summary
|
|
|
|
<!-- SECTION:FINAL_SUMMARY:BEGIN -->
|
|
Executed the repo's maintained local verification gate from the development docs: `bun run test:fast`, `bun run test:env`, `bun run build`, and `bun run test:smoke:dist`.
|
|
|
|
Result: every command passed. No failing tests surfaced, so no additional fixes or new regression tests were required for this task.
|
|
|
|
Working tree note: existing unrelated user changes remain in place, along with the prior formatting-only change to `src/release-workflow.test.ts` from TASK-163. This task introduced no new code changes.
|
|
<!-- SECTION:FINAL_SUMMARY:END -->
|