sudacode/SubMiner

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

Files

T

History

sudacode f7230db90c

chore(release): prepare v0.20.0

- Build v0.20.0 changelog and release notes from changes/ fragments
- Remove package-size JSON reports and previous-release size comparisons from CI
- Download AUR release assets via curl with retries and skip publish on failure
- Update release docs, verification lanes, and workflow tests to match

2026-09-24 00:01:03 -07:00

..

fix(dictionary): pin Hachidori extension ID with a static manifest key

2026-09-23 09:15:33 -07:00

chore(workflow): add release skill

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

chore(release): prepare v0.20.0

2026-09-24 00:01:03 -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.