sudacode/SubMiner

Fork 0

mirror of https://github.com/ksyasuda/SubMiner.git synced 2026-06-11 03:13:32 -07:00

Files

T

History

sudacode b3b45521b6

fix(release): preserve attribution placement; default update notifs to o

- Move What's Changed/New Contributors before Installation in release notes
- Preserve committed attribution when regenerating via writeReleaseNotesForVersion
- Change notificationType default from 'both' to 'overlay' for new installs

2026-06-10 23:53:31 -07:00

architecture

feat(notifications): add overlay notifications with position config (#110 )

2026-06-10 22:46:52 -07:00

knowledge-base

fix(overlay): Linux X11/XWayland stacking, stale pause state, multi-copy selector (#101 )

2026-05-31 20:59:18 -07:00

plans

feat(notifications): add overlay notifications with position config (#110 )

2026-06-10 22:46:52 -07:00

superpowers

feat(stats): dashboard updates (#50 )

2026-04-10 02:46:50 -07:00

workflow

docs: audit and refresh user-facing and internal docs

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

README.md

docs: audit and refresh user-facing and internal docs

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

RELEASING.md

fix(release): preserve attribution placement; default update notifs to o

2026-06-10 23:53:31 -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.