runner hook resolves target via Ticket.most_recent — breaks with concurrent pipelines #357

New issue

Open

opened 2026-08-14 14:14:32 +00:00 by jared · 1 comment

jared commented

2026-08-14 14:14:32 +00:00

Owner

Context

Target wiring (2026-08-14) persists the intake target on the ticket row; hooks/post_tool_use.rb reads it back via Ticket.most_recent because the hook re-entry carries no CLI/env context. With two pipelines in flight in one repo, the hook would read the newer ticket's target for both. Fine under today's single-run assumption; needs a real ticket-attribution mechanism (e.g. correlate the Agent tool call to its ticket) before parallel runs are supported.

## Context Target wiring (2026-08-14) persists the intake target on the ticket row; hooks/post_tool_use.rb reads it back via Ticket.most_recent because the hook re-entry carries no CLI/env context. With two pipelines in flight in one repo, the hook would read the newer ticket's target for both. Fine under today's single-run assumption; needs a real ticket-attribution mechanism (e.g. correlate the Agent tool call to its ticket) before parallel runs are supported.

jared added the

plugin/os-sdlc

labels

2026-08-14 14:14:32 +00:00

jared referenced this issue

2026-08-14 14:14:40 +00:00

os-sdlc: temporary temp-implement skill — orchestrator-driven harness until the runner is ready #355

jared referenced this issue from a commit

2026-08-14 19:06:24 +00:00

feat(os-sdlc): target selection wiring + implement lifecycle

jared added the

frozen