Parent: #168
Outcome
Certify darrow-tdd under the Python + uv and native-Windows plugin baseline while preserving its skill-only, repository-native test-first behavior.
Priority
13 of 14 remaining plugins. It has no bundled executable mechanics and can be validated after the runtime-bearing plugins establish the final baseline.
Scope
Audit packaging, examples, command language, stable-seam guidance, and eval fixtures for platform-specific assumptions. Add no plugin runtime without a concrete deterministic-helper need.
Done criteria
- Confirm and document whether the plugin remains correctly skill-only.
- Preserve red/green slicing, public-seam selection, failure evidence, and completion boundaries.
- Make examples and fixtures neutral across Windows and POSIX command environments where behavior does not require a platform.
- Verify independent installation and invocation on Claude Code and Codex across Linux, macOS, and native Windows.
- Keep all TDD evals passing and update documentation and matching manifest versions when content changes.
Migration blueprint
Use the implementation merged in PR #173 as the default blueprint for Python + uv plugin mechanics. Reuse its self-contained package layout, committed uv lock, runtime/development dependency separation, python-packages.txt inventory, Ruff and strict mypy gates, separate 95% line and branch coverage gates, and fresh copied-artifact validation. Extend that pattern with native-Windows fresh-artifact validation where this rollout requires Windows support. Document any plugin-specific deviation explicitly instead of introducing a competing convention.
Parent: #168
Outcome
Certify
darrow-tddunder the Python + uv and native-Windows plugin baseline while preserving its skill-only, repository-native test-first behavior.Priority
13 of 14 remaining plugins. It has no bundled executable mechanics and can be validated after the runtime-bearing plugins establish the final baseline.
Scope
Audit packaging, examples, command language, stable-seam guidance, and eval fixtures for platform-specific assumptions. Add no plugin runtime without a concrete deterministic-helper need.
Done criteria
Migration blueprint
Use the implementation merged in PR #173 as the default blueprint for Python + uv plugin mechanics. Reuse its self-contained package layout, committed uv lock, runtime/development dependency separation, python-packages.txt inventory, Ruff and strict mypy gates, separate 95% line and branch coverage gates, and fresh copied-artifact validation. Extend that pattern with native-Windows fresh-artifact validation where this rollout requires Windows support. Document any plugin-specific deviation explicitly instead of introducing a competing convention.