Files
SubMiner/docs/workflow
sudacode 90fc7cf940 refactor(main): fold remaining main-deps builders into their handlers (#308)
* refactor(main): drop remaining pass-through main-deps builders

Jellyfin client-info/setup-window/remote, overlay shortcuts/visibility/
layout/window-factory, config hot-reload, and startup bootstrap factory
builders only forwarded deps. Callers now pass deps to the handlers
directly; createWatchConfigPathHandler moves into config-hot-reload-handlers.

* refactor(main): fold small-logic main-deps builders into their handlers

Tray click, mpv client factory, startup bootstrap exit callbacks, overlay
runtime options, and dictionary roots/runtime builders move their logic
into the owning handler or call site. The two duplicated dictionary-root
builders become one createBuildDictionaryRootsHandler(vendorDirName).

* refactor(main): fold cli command context builders into the factory

createCliCommandContextFactory now adapts appState and main services to
the CLI command context deps directly (socket-path change notification,
texthooker port/websocket URL, browser-open default). The pass-through
cli-command-context-main-deps and cli-command-context-deps layers are
removed; their behavioural tests now run against the factory's context.

* refactor(main): fold subtitle tokenization builder into the mpv composer

The tokenizer deps builder's logic (known-word lookup recording and the
character-dictionary gate on name matching) becomes
buildTokenizerRuntimeOptions in mpv-runtime-composer, tested through the
composer. The MeCab check and dictionary prewarm handlers move to
subtitle-tokenization-warmup.ts, and the unused BuiltMainDeps type is
removed from composer contracts.

* refactor(main): drop redundant tokenizer deps keys and cast

* refactor(main): end the main-deps builder pattern

mpv-main-event-main-deps becomes mpv-main-event-binding-deps
(createMpvMainEventBindingDeps), returning the binding deps directly
instead of a thunk; it owns the subtitle-recording state. The will-quit
cleanup adapter likewise returns its deps directly, and the pass-through
app-lifecycle activate builders are removed.

* docs: drop references to main-deps builders
2026-10-31 14:07:07 -07:00
..

Workflow

Status: active
Last verified: 2026-08-13 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
  • Testing - what a good test looks like and what not to write
  • Agent Skills - repo-local workflow skill ownership
  • 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.