Repository navigation
Conversation
…iewer (AGT-4055) The Discord /pair flow calls runWorker/runReviewer directly and never built a coordinationContext, so the AGT-4054 inbox nudge, guidance prompt and coordination tools were inert there. - PairSession carries the Linear issue UUID when the session is backed by a real issue (!pair start, and !pair run when the lookup resolves). - pairCoordinationContext() derives the board identity with the pipeline's own coordinationContextFor, keyed by the issue UUID like the daemon, so a Discord run and a daemon run on one issue are the same participants. - Sessions with no issue behind them get no coordination tools rather than a synthetic id nobody would address. - coordinationContextFor now takes a narrower CoordinationSubject (task ids, projectPath, runMetadata); PipelineContext still satisfies it. - v1 visibility is board-only: publishes are not echoed into the thread.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
무엇
PairSession/CreatePairSessionOptions에linearIssueId(Linear 이슈 UUID)를 추가했다.!pair start와, Linear 조회에 성공한!pair run에서 채운다.discordPair.ts에pairCoordinationContext(session, role)을 추가하고runWorker/runReviewer호출에coordinationContext로 넘긴다.coordinationContextFor의 인자 타입을CoordinationSubject(task id 3종, projectPath, runMetadata)로 좁혔다.PipelineContext는 그대로 만족하므로 pairPipeline 쪽 호출은 바뀌지 않는다.설계 결정 (DoD 1·2)
coordination_publish를 스레드로 에코하지 않는다. 스레드 에코는 필요하면 후속으로 한다.왜
AGT-4054(#445)의 inbox nudge·가이드 프롬프트·coordination 도구가 Discord
/pair흐름에서는 동작하지 않았다. 이 흐름은pairPipeline을 거치지 않고 worker/reviewer를 직접 부르기 때문이다.검증
src/discord/discordPair.coordination.test.ts5건: 이슈 없음 → undefined, UUID 키·identifier 라벨, 역할별 handle 안정성,!pair run에서 worker/reviewer 양쪽 전달, 조회 실패 시 미전달tsc --noEmit -p tsconfig.check.json통과, oxlint 0src/discord src/agents src/coordination109 files / 1504 tests 통과