Files
SubMiner/backlog/tasks/task-76 - Tokenizer-remove-POS-exclusion-config-surface-and-keep-hardcoded-defaults.md
2026-03-01 02:36:51 -08:00

1.3 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-76 Tokenizer: remove POS exclusion config surface and keep hardcoded defaults Done
2026-03-01 02:45 2026-03-01 04:14
medium 5000

Description

Remove user-facing config keys for annotation POS exclusions. Keep N+1/frequency POS exclusion behavior as built-in defaults with no config required.

Scope: remove config parsing/registry/docs/example for annotationFilters.pos1Exclusions/pos2Exclusions while preserving runtime filtering behavior.

Acceptance Criteria

  • #1 No user-facing config option exists for annotation POS exclusions.
  • #2 Runtime N+1/frequency exclusion behavior remains active via built-in defaults.
  • #3 Config/docs/example/tests updated accordingly.

Final Summary

Removed user-facing subtitleStyle.annotationFilters POS exclusion configuration (schema/resolver/options/docs/example). POS-based N+1/frequency filtering now always uses built-in defaults in runtime. Preserved robust exclusion behavior including merged-token overlap POS handling and N+1-only MeCab enrichment path.