sudacode/SubMiner

0 Fork 0

mirror of https://github.com/ksyasuda/SubMiner.git synced 2026-10-21 05:01:26 -07:00

Files

T

History

sudacode 4d1adebf11

refactor(hachidori): drop the Docker management upload for character dictionaries

Every supported host now takes dictionary ZIPs over the link, so remove
the port 8780 upload, its hachidori.externalHostManagementUrl override and
the hachidori config section. A linked host without linked-import-v1 now
reports the update or manual-import fix.

2026-10-05 09:50:52 -07:00

..

refactor(hachidori): drop the Docker management upload for character dictionaries

2026-10-05 09:50:52 -07:00

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

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

Merge remote-tracking branch 'origin/main' into add-hachidori-backend

2026-10-05 09:01:11 -07:00

README.md

docs: audit and refresh user-facing and internal docs

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

RELEASING.md

chore(release): remove package size reports

2026-09-23 21:50: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.