sudacode/SubMiner

Fork 0

mirror of https://github.com/ksyasuda/SubMiner.git synced 2026-09-22 05:16:22 -07:00

Files

T

History

sudacode d9fdc7ef6d

feat(dictionary): add Hachidori backend support

- Add backend selection, setup gating, Anki integration, and external host support
- Add launcher flags, documentation, packaging, and focused tests
- Open on-demand overlay modals on the first attempt

2026-09-22 00:21:19 -07:00

architecture

feat(dictionary): add Hachidori backend support

2026-09-22 00:21:19 -07:00

knowledge-base

chore(workflow): add release skill

2026-08-23 01:14:03 -07:00

workflow

feat(dictionary): add Hachidori backend support

2026-09-22 00:21:19 -07:00

README.md

docs: audit and refresh user-facing and internal docs

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

RELEASING.md

feat(stats): add TMDB metadata for live-action dramas in the Library (#252 )

2026-09-21 00:10:00 -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.