sudacode/SubMiner

0 Fork 0

mirror of https://github.com/ksyasuda/SubMiner.git synced 2026-10-27 23:35:17 -07:00

Files

T

History

sudacode 15f32b10c7

feat(plugins): add episode-tags and auto-jimaku example plugins

- episode-tags: tag mined cards with show/episode parsed from the file name or stream title
- auto-jimaku: open Jimaku search when a file starts without a Japanese subtitle track
- Hold card-mined for notes merged into a note still waiting on queued YouTube media
- Route YouTube media settle reports through reportCardsReady
- Document both plugins in docs-site and changelog fragment

2026-10-27 22:31:34 -07:00

..

feat(plugins): add episode-tags and auto-jimaku example plugins

2026-10-27 22:31:34 -07:00

test: cut low-value tests, rewrite the rest around behavior, parallelize lanes (#285 )

2026-10-05 00:07:44 -07:00

feat(plugins): add JavaScript plugin system with overlay panel

2026-10-26 21:38:51 -07:00

README.md

docs: audit and refresh user-facing and internal docs

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

RELEASING.md

chore(build): consolidate packaging inputs and build output layout (#299 )

2026-10-24 23:28:38 -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.