Files
SubMiner/docs/workflow
sudacode a4927a3bbd refactor(tests): centralize lane definitions and add per-file isolation
- extract test lane config to scripts/test-lanes.ts (single source of truth)
- run-test-lane.mjs: per-file bun process isolation with wall timeout; --jobs N, --single-process flags
- drop hand-listed test file lists from package.json; lanes now discovered by directory
- add test:stats (stats/src) and test:scripts (scripts/**) lanes; wire both into CI
- test:fast now: test:src + launcher-unit + test:scripts + test:runtime:compat
- remove obsolete test:full, test:core, test:core:dist, test:config:dist scripts
2026-07-07 00:17:43 -07:00
..

Workflow

Status: active
Last verified: 2026-05-23
Owner: Kyle Yasuda
Read when: planning or executing nontrivial work in this repo

This section is the internal workflow map for contributors and agents.

  • Planning - when to write a lightweight plan vs a full execution plan
  • Verification - maintained test/build lanes and handoff gate
  • Agent Plugins - repo-local plugin ownership for agent workflow skills
  • Release Guide - tagged release workflow

Default Flow

  1. Read the smallest relevant docs from docs/.
  2. Decide whether the work needs a written plan.
  3. Implement in small, reviewable edits.
  4. Run the cheapest sufficient verification lane.
  5. Escalate to the full maintained gate before handoff when the change is substantial.

Boundaries

  • Internal process lives in docs/.
  • Public/product docs live in docs-site/.
  • Generated artifacts are never edited by hand.