Certify darrow-readiness-gate for the Python + uv plugin baseline #186

Parent: #168

Outcome

Certify darrow-readiness-gate under the Python + uv and native-Windows plugin baseline while keeping it skill-only unless substantial deterministic mechanics are justified.

Priority

12 of 14 remaining plugins. It currently has no bundled runtime scripts and therefore needs certification after script-bearing capabilities are migrated.

Scope

Audit packaging, installation, JSON/human-output examples, resource references, and eval fixtures for cross-platform assumptions.

Done criteria

• Confirm whether any substantial helper is warranted; do not introduce Python for prose-only behavior.
• Preserve readiness criteria, verdict semantics, evidence handling, and v1 JSON output exactly.
• Verify independent installation and invocation across Linux, macOS, and native Windows for Claude Code and Codex.
• Remove POSIX-only path or fixture assumptions without weakening the gate.
• Keep all readiness 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.