sudacode/SubMiner

mirror of https://github.com/ksyasuda/SubMiner.git synced 2026-07-27 04:49:49 -07:00

Files

T

History

sudacode 83fffe533a

refactor: split anki-connect and stats-server resolvers into modules

- Break src/config/resolve/anki-connect.ts into focused resolvers under anki-connect/ (initialize, known-words, legacy, modern, shared)
- Break src/core/services/stats-server.ts into route groups under stats-server/ (analytics, integration, library, mining, static, shared support)
- Add route-group and resolver isolation tests
- Update docs/architecture/domains.md to reflect new module layout

2026-07-15 22:58:55 -07:00

..

refactor: split anki-connect and stats-server resolvers into modules

2026-07-15 22:58:55 -07:00

fix(overlay): Linux X11/XWayland stacking, stale pause state, multi-copy selector (#101 )

2026-05-31 20:59:18 -07:00

feat(stats): dashboard updates (#50 )

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

remove redundant isVerbNonIndependent and consolidate test lanes

2026-07-14 19:57:50 -07:00

README.md

docs: audit and refresh user-facing and internal docs

2026-05-23 21:21:16 -07:00

RELEASING.md

ci: reuse quality gate across CI and release workflows (#167 )

2026-07-13 23:14:19 -07:00

README.md

SubMiner Internal Docs

Status: active
Last verified: 2026-05-23
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

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.