Files
SubMiner/backlog/tasks/task-100 - Add-configurable-texthooker-startup-launch.md
sudacode 5d96f9d535 Add annotation websocket and texthooker startup config
- Add `texthooker.launchAtStartup` (default `true`) and wire startup behavior
- Add dedicated `annotationWebsocket` config/service path (default port `6678`) for texthooker annotations
- Regenerate config example/tests and update Yomitan patching/vendor assets
2026-03-07 01:41:08 -08:00

1.5 KiB

id, title, status, assignee, created_date, updated_date, labels, dependencies, priority, ordinal
id title status assignee created_date updated_date labels dependencies priority ordinal
TASK-100 Add configurable texthooker startup launch Done
2026-03-06 23:30 2026-03-07 01:59
medium 10000

Description

Add a config option under texthooker to launch the built-in texthooker server automatically when SubMiner starts.

Scope:

  • Add texthooker.launchAtStartup.
  • Default to true.
  • Start the existing texthooker server during normal app startup when enabled.
  • Keep texthooker.openBrowser as separate behavior.
  • Add regression coverage and update generated config docs/example.

Acceptance Criteria

  • #1 Default config enables automatic texthooker startup.
  • #2 Config parser accepts valid boolean values and warns on invalid values.
  • #3 App-ready startup launches texthooker when enabled.
  • #4 Generated config template/example documents the new option.

Final Summary

Added texthooker.launchAtStartup with a default of true, wired it through config defaults/validation/template generation, and started the existing texthooker server during app-ready startup without coupling it to browser auto-open behavior.

Also added regression coverage for config parsing/template output and app-ready dependency wiring, then regenerated the checked-in config example artifacts.