mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-06 14:00:09 +02:00
* feat(issues): unify run-enqueue decision behind WillEnqueueRun + preview endpoint Collapse the issue update/batch enqueue copies into one service predicate service.IssueService.WillEnqueueRun, shared verbatim with a new dry-run endpoint POST /api/issues/preview-trigger so the four entry points stop drifting (squad/self-loop/batch omissions, MUL-3375). The private-agent gate stays at the HTTP boundary: write paths inject allow-all, preview injects the real gate so it never leaks a private agent's readiness. Add suppress_run to issue update/batch: the change applies but no run starts. Remove the now-dead handler mirrors shouldEnqueueSquadLeaderOnAssign / isSquadLeaderReady. service.Create and the comment trigger chain are untouched. Tests: preview behavior, preview<->write-path match, batch aggregation, member no-trigger, suppress_run skip, malformed-body 400. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai> * feat(issues): inject handoff note into assigned runs via first-class task field Add an optional handoff_note carried by issue assign/promote into the run's opening prompt and issue_context.md, via a dedicated agent_task_queue column (migration 122) and a daemon assignment-handoff render branch — never a fabricated comment, never trigger_comment_id (MUL-3375 §6.1). Thread the note through enqueueIssueTask/enqueueMentionTask + WithHandoff public variants and dispatchIssueRun; suppress_run or a parked write drops it (no run = nothing to inject). Soft version gate: MinHandoffCLIVersion + HandoffSupported, surfaced per-trigger as handoff_supported in the preview so the UI can gray the note box on old daemons; the assignment never hard-fails. Tests: daemon prompt + issue_context render via the assignment branch (not quick-create/comment), version helper matrix, note persists on the task, suppressed assign enqueues nothing. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai> * feat(issues): leave a display-only handoff record on the timeline When an assign/promote with a handoff note starts a run, write one type='handoff' timeline record via TaskService.RecordHandoff — a direct Queries.CreateComment + timeline event that bypasses Handler.CreateComment, so it never reaches triggerTasksForComment and cannot start a second run (MUL-3375 §6.2, the must-not-retrigger invariant). Author is the actor who handed off; body is the note. Migration 123 admits the 'handoff' comment type. Recorded only on a real run start: suppress_run or a parked write writes nothing. enqueueSquadLeaderTask now reports whether it enqueued so the trace is gated on an actual dispatch. Test: exactly one handoff record on assign-with-note, exactly one task (no re-trigger), and no record when suppressed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai> * feat(issues): frontend plumbing for issue-trigger preview + handoff (core) Add api.previewIssueTrigger + IssueTriggerPreviewSchema (zod parseWithFallback), the use-issue-trigger-preview hook, issueKeys.issueTriggerPreview(+All) with WS queue-state invalidation, suppress_run/handoff_note on UpdateIssueRequest, the 'handoff' CommentType, and stripping of the control fields from optimistic update/batch cache patches (MUL-3375 §9). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai> * fix(issues): exclude handoff records from new-comment counting type='handoff' is a display-only timeline record, not conversation. Exclude it from CountNewCommentsSince so a handoff note never inflates the count of "new comments to catch up on" fed to a claiming agent (MUL-3375 §12). Analytics already excludes it (RecordHandoff is a direct write that emits no analytics event), and the comment-trigger path is already bypassed. Test: a handoff record does not bump the new-comment count; a real comment does. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai> * feat(issues): pre-trigger preview UI, handoff note, timeline card (web/desktop) Wire the §9 frontend onto the preview endpoint + handoff fields: - Delete the backlog blocking dialog (backlog-agent-hint*) and its modal type; the over-eager nag is gone. Backlog awareness is now a passive label. - RunConfirmModal: single assign + batch assign/status route here. Shows the backend predicate's verdict ("将启动 @X" / "将启动 N 个" / parked), an optional handoff note (assign only, soft-gated by handoff_supported), and 暂不启动 — then applies via update/batch. No frontend guessing. - create modal: passive CreateRunHint ("将启动 @X" / backlog parked). - single status change stays a direct apply (unchanged). - timeline: render type='handoff' as a distinct, non-interactive handoff card. - i18n run_confirm + handoff_card across en/ja/ko/zh-Hans; drop backlog action keys; locale parity green. Tests: use-issue-actions (assign → run-confirm modal, member → direct), create-issue + comment-card suites updated/green; views typecheck + lint clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai> * test(issues): use a valid anchor in the handoff count-exclusion test CountNewCommentsSince filters id <> @anchor_id; SQL id <> NULL is NULL and excludes every row, so an empty anchor made the control assertion read 0. The production caller always passes a real anchor — mirror that with a non-matching sentinel uuid. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai> * test(issues): RunConfirmModal apply logic (start/suppress/note-gate/batch) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai> * test(core): preview schema malformed/missing/null fallback coverage Cover IssueTriggerPreviewSchema via parseWithFallback (MUL-3375): well-formed parse, top-level + item default fills (empty/older backend), and fallback to { triggers: [], total_count: 0 } for malformed shapes, a dropped required issue_id, a wrong-typed total_count, and null/non-object bodies — so the four entry points degrade to "nothing will start" instead of throwing. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai> * refactor(issues): remove display-only handoff timeline record (留痕) The handoff "留痕" timeline record (type='handoff' comment written on run start) was judged superfluous and dropped per product call. This removes only the display-only trace; the handoff NOTE injection into the run's opening prompt + issue_context.md is untouched. - backend: drop RecordHandoff + its call in dispatchIssueRun - db: drop the `type <> 'handoff'` exclusion in CountNewCommentsSince and migration 123 (comment_type_check reverts to the 4-type set from 001); no production data exists for this unreleased feature - frontend: drop the "handoff" CommentType, HandoffCard, and handoff_card i18n (all locales) - tests: drop handoff_count_test.go and the record-write assertions in issue_trigger_preview_test.go (note-injection tests retained) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai> * feat(issues): dismissable run-confirm modal + team-handoff copy Two fixes to the pre-trigger confirm modal (MUL-3375). 1. Dismissable: switch RunConfirmModal from AlertDialog to the standard shadcn Dialog so it has the close (X) button + Esc + click-outside. Previously the only choices were "start" / "don't start now" with no way to abort the action entirely; dismissing now cancels with no write. 2. Copy: rework the action-surface wording away from the backend term "run" toward team-handoff voice — 指派 / 开始 / 交接 (run stays only on record surfaces). Unifies the note's three names to "交接说明", and parallels the rewrite across en/ja/ko. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai> * chore(agent): bump handoff note min CLI version to 0.3.28 The daemon release that renders handoff notes ships in 0.3.28 (0.3.27 was the prior tag), so move the soft-gate threshold up. Below this the note is silently dropped and the frontend grays the note box — assignment is never blocked. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(issues): skip run-confirm when batch-moving issues to backlog A move into backlog never starts a run (service/issue_trigger.go), so the pre-trigger confirm modal degenerated to an empty "won't start" box with a single Apply button — pure friction. Apply directly instead, matching the single-issue status path. Other target statuses still route through the modal. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(issues): refine pre-trigger preview hint and copy - Move the create-issue run hint to a reveal band (grid 0fr→1fr) above the property toolbar. It was sharing the footer button row and, lacking a width constraint, reflowed the submit buttons whenever it appeared. Restyle to a borderless, comment-style avatar+caption that is purely a caption (non-interactive avatar). - Distinguish squad from agent in the pre-trigger copy: a squad's leader evaluates and delegates rather than "starting work" itself. Add will_start_named_squad / will_start_squad / create_will_start_squad across en/zh/ja/ko (reusing the squad_leader_* evaluate→arrange vocabulary) and branch run-confirm + the create hint on squad assignees. - Bold the assignee name in the run-confirm headline via a language-safe sentinel split (no per-language prefix/suffix keys). - Align zh "开始处理" → "开始工作" on the single-assign copy. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * test(issues): stub ActorAvatar in create-issue suite CreateRunHint now renders an ActorAvatar for agent/squad assignees, which pulls in getActorInitials/getActorAvatarUrl + the workspace/presence/navigation hook tree. This form-focused suite only stubbed getActorName, so the squad-forwarding test crashed with "getActorInitials is not a function". Stub the avatar inert — its own behavior is covered elsewhere. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Walt <walt@multica.ai> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai>
174 lines
6.1 KiB
Go
174 lines
6.1 KiB
Go
package service
|
|
|
|
import (
|
|
"context"
|
|
|
|
"github.com/jackc/pgx/v5/pgtype"
|
|
db "github.com/multica-ai/multica/server/pkg/db/generated"
|
|
)
|
|
|
|
// RunEnqueueSource identifies which kind of issue write would start an agent
|
|
// run. It is surfaced in preview responses so the UI can explain each trigger.
|
|
type RunEnqueueSource string
|
|
|
|
const (
|
|
// RunSourceAssign covers issue creation and assignee changes — the issue
|
|
// is being handed to an agent/squad. Parks silently on backlog.
|
|
RunSourceAssign RunEnqueueSource = "assign"
|
|
// RunSourceStatus covers promoting an already-assigned issue out of
|
|
// backlog into an active status.
|
|
RunSourceStatus RunEnqueueSource = "status"
|
|
)
|
|
|
|
// IssueTriggerProbe carries the request-scoped checks WillEnqueueRun cannot
|
|
// resolve from issue state alone.
|
|
//
|
|
// CanAccessAgent is the private-agent gate. The write paths enforce it at the
|
|
// HTTP boundary (validateAssigneePair on assign, canEnqueueSquadLeader inside
|
|
// the squad enqueue helper) and therefore pass an allow-all probe so the gate
|
|
// is never duplicated or sunk into the service layer. Preview passes the real
|
|
// gate so it never leaks a private agent's readiness to a member who cannot
|
|
// see it. A nil func is treated as allow-all.
|
|
//
|
|
// IsSelfLoop reports whether promoting this issue out of backlog would be the
|
|
// calling agent re-triggering its own running task. Only the status source
|
|
// consults it; create and assign never do. A nil func means "not a self-loop".
|
|
type IssueTriggerProbe struct {
|
|
CanAccessAgent func(agent db.Agent) bool
|
|
IsSelfLoop func() bool
|
|
}
|
|
|
|
// IssueTriggerInput describes one prospective issue write in its post-write
|
|
// shape. AssigneeChanged / StatusChanged mark which fields the write touches;
|
|
// IsCreate marks a brand-new issue (no prior task to cancel, no self-loop).
|
|
type IssueTriggerInput struct {
|
|
Issue db.Issue
|
|
PrevStatus string
|
|
IsCreate bool
|
|
AssigneeChanged bool
|
|
StatusChanged bool
|
|
}
|
|
|
|
// IssueRunTrigger is the resolved decision shared by preview and the write
|
|
// paths. AgentID is the agent that will actually run — the assignee for an
|
|
// agent issue, the squad leader for a squad issue.
|
|
type IssueRunTrigger struct {
|
|
IssueID pgtype.UUID
|
|
AgentID pgtype.UUID
|
|
AssigneeType string
|
|
Source RunEnqueueSource
|
|
}
|
|
|
|
func allowAllAgents(db.Agent) bool { return true }
|
|
|
|
// WillEnqueueRun is the single predicate answering "will this issue write
|
|
// start an agent run, and for whom". It is the one source of truth shared by
|
|
// the issue update / batch-update write paths and the preview endpoint,
|
|
// replacing the per-site copies that drifted (squad omitted, self-loop
|
|
// omitted, four entry points inconsistent — see MUL-3375).
|
|
//
|
|
// It is intentionally a distinct predicate from the comment trigger
|
|
// (shouldEnqueueOnComment): issue writes park on backlog while comments fire
|
|
// in any status. The two only share leaf readiness checks (AgentReadiness,
|
|
// the pending-task dedup), not the top-level decision.
|
|
//
|
|
// The decision must equal the real enqueue conditions so preview never claims
|
|
// a run that the write path then drops. In particular:
|
|
// - assign source (create / assignee change) cancels existing tasks before
|
|
// enqueuing, so a pre-existing pending task is moot — not checked here.
|
|
// - status source (backlog → active) enqueues without cancelling, so a live
|
|
// pending task would be blocked by the (issue_id, agent_id) unique index;
|
|
// reflected by the pending check below.
|
|
func (s *IssueService) WillEnqueueRun(ctx context.Context, in IssueTriggerInput, probe IssueTriggerProbe) (IssueRunTrigger, bool) {
|
|
issue := in.Issue
|
|
if !issue.AssigneeType.Valid || !issue.AssigneeID.Valid {
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
canAccess := probe.CanAccessAgent
|
|
if canAccess == nil {
|
|
canAccess = allowAllAgents
|
|
}
|
|
|
|
var source RunEnqueueSource
|
|
switch {
|
|
case in.IsCreate || in.AssigneeChanged:
|
|
// Backlog is the parking lot: assigning into backlog never starts a run.
|
|
if issue.Status == "backlog" {
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
source = RunSourceAssign
|
|
case in.StatusChanged && in.PrevStatus == "backlog" &&
|
|
issue.Status != "done" && issue.Status != "cancelled":
|
|
if probe.IsSelfLoop != nil && probe.IsSelfLoop() {
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
source = RunSourceStatus
|
|
default:
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
|
|
switch issue.AssigneeType.String {
|
|
case "agent":
|
|
agent, err := s.Queries.GetAgent(ctx, issue.AssigneeID)
|
|
if err != nil || !agent.RuntimeID.Valid || agent.ArchivedAt.Valid {
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
if !canAccess(agent) {
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
if source == RunSourceStatus && s.hasPendingRun(ctx, issue.ID, issue.AssigneeID) {
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
return IssueRunTrigger{
|
|
IssueID: issue.ID,
|
|
AgentID: issue.AssigneeID,
|
|
AssigneeType: "agent",
|
|
Source: source,
|
|
}, true
|
|
|
|
case "squad":
|
|
squad, err := s.Queries.GetSquadInWorkspace(ctx, db.GetSquadInWorkspaceParams{
|
|
ID: issue.AssigneeID,
|
|
WorkspaceID: issue.WorkspaceID,
|
|
})
|
|
if err != nil {
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
leader, err := s.Queries.GetAgent(ctx, squad.LeaderID)
|
|
if err != nil {
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
ready, _, err := AgentReadiness(ctx, s.Queries, leader)
|
|
if err != nil || !ready {
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
if !canAccess(leader) {
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
if source == RunSourceStatus && s.hasPendingRun(ctx, issue.ID, squad.LeaderID) {
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
return IssueRunTrigger{
|
|
IssueID: issue.ID,
|
|
AgentID: squad.LeaderID,
|
|
AssigneeType: "squad",
|
|
Source: source,
|
|
}, true
|
|
}
|
|
return IssueRunTrigger{}, false
|
|
}
|
|
|
|
// hasPendingRun reports whether the agent already holds a queued or dispatched
|
|
// task for the issue (the (issue_id, agent_id) unique-index slot). Errors fail
|
|
// closed to "pending" so preview never over-promises a run.
|
|
func (s *IssueService) hasPendingRun(ctx context.Context, issueID, agentID pgtype.UUID) bool {
|
|
pending, err := s.Queries.HasPendingTaskForIssueAndAgent(ctx, db.HasPendingTaskForIssueAndAgentParams{
|
|
IssueID: issueID,
|
|
AgentID: agentID,
|
|
})
|
|
if err != nil {
|
|
return true
|
|
}
|
|
return pending
|
|
}
|