Upgrade darrow-ticket-to-pr for the migrated plugin stack #184

Parent: #168

Outcome

Upgrade darrow-ticket-to-pr to compose the migrated ticket, Git, review, verification, and adaptive-delivery plugins portably without adding its own workflow runtime.

Priority

10 of 14 remaining plugins. This composition recipe should move only after the capabilities it delegates to have stable migrated interfaces.

Scope

Audit and update its composition fixtures, installation assumptions, and host invocation seams. Add Python only if substantial deterministic mechanics remain after dependency migration; otherwise keep the plugin skill-only.

Done criteria

• Preserve the one-ticket/one-PR contract, exact token propagation, same-PR review evidence, continuation behavior, and explicit orchestration trigger.
• Remove POSIX-only fixture assumptions where native host APIs or portable test helpers can express the same boundary.
• Demonstrate composition against the final public interfaces of the migrated dependency plugins.
• Keep the plugin independently installable and avoid copying provider or orchestration mechanics.
• If Python is introduced, register and lock it and satisfy every Establish and enforce repository-wide Python quality standards #172 gate; otherwise document why no runtime was added.
• Run composition tests and evals on Linux, macOS, and native Windows.
• Update docs and matching manifest versions.

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.