sudacode/SubMiner

mirror of https://github.com/ksyasuda/SubMiner.git synced 2026-05-26 12:55:16 -07:00

Files

T

History

sudacode 48447c2f1a

fix: curl fetch for Linux updater, overlay restart restore, Yomitan late

- Use /usr/bin/curl on Linux for update checks to avoid Electron net-service crashes
- Restore visible overlay on manual restart even when auto-start visibility is disabled
- Reload overlay windows after Yomitan extension loads to fix popup race on startup

2026-05-20 01:45:14 -07:00

..

Refactor startup, queries, and workflow into focused modules (#36 )

2026-03-29 16:16:29 -07:00

feat(stats): add v1 immersion stats dashboard (#19 )

2026-03-20 02:43:28 -07:00

feat(macos): configuration window + curl-backed macOS updater (#71 )

2026-05-17 02:23:44 -07:00

feat(stats): dashboard updates (#50 )

2026-04-10 02:46:50 -07:00

chore: remove Backlog.md task system and backlog directory

2026-05-12 23:37:31 -07:00

README.md

Refactor startup, queries, and workflow into focused modules (#36 )

2026-03-29 16:16:29 -07:00

RELEASING.md

fix: curl fetch for Linux updater, overlay restart restore, Yomitan late

2026-05-20 01:45:14 -07:00

README.md

SubMiner Internal Docs

Status: active
Last verified: 2026-03-13
Owner: Kyle Yasuda
Read when: you need internal architecture, workflow, verification, or release guidance

docs/ is the internal system of record for agent and contributor knowledge. Start here, then drill into the smallest doc that fits the task.

Start Here

Architecture - runtime map, domains, layering rules
Workflow - planning, execution, verification expectations
Knowledge Base - how docs are structured, maintained, and audited
Release Guide - tagged release checklist
Plans - active design and implementation artifacts

Fast Paths

New feature or refactor: Workflow, then Architecture
Test/build/release work: Verification, then Release Guide
Coverage lane selection or LCOV artifact path: Verification
“What owns this behavior?”: Domains
“Can these modules depend on each other?”: Layering
“What doc should exist for this?”: Catalog

Rules

Treat docs/ as canonical for internal guidance.
Treat docs-site/ as user-facing/public docs.
Keep AGENTS.md short; deep detail belongs here.
Update docs when behavior, architecture, or workflow meaningfully changes.