sudacode/SubMiner

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

Files

History

sudacode 8874e2e1c6

docs: add stats dashboard feedback pass implementation plan

Task-by-task TDD plan for the seven items in the matching design
spec, organized as eleven commits in a single PR (365d backend,
server allow-list, frontend selector, vocabulary column,
Anki-deleted card filter, library episode delete, collapsible
library groups, session grouping helper, sessions tab rollup,
chart clarity pass, changelog fragment).

2026-04-09 00:28:41 -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

docs: add stats dashboard feedback pass implementation plan

2026-04-09 00:28:41 -07:00

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

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

README.md

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

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

RELEASING.md

fix(release): make AUR publish best-effort

2026-03-29 16:51:22 -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.