mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-05 21:39:54 +02:00
b17f975a17
* docs(cli): clarify `issue rerun` semantics The CLI table described `multica issue rerun <id>` as "Rerun the most recent agent task", which led users to expect it would re-run whichever agent ran last. The actual behavior is to enqueue a fresh task for the issue's **current** agent assignee, regardless of who ran most recently — see `TaskService.RerunIssue` in `server/internal/service/task.go`. Also fix a stale claim in `tasks.mdx`: the "Manual rerun" section described session inheritance as "Yes", but commitb1345685made manual rerun pass `force_fresh_session=true` precisely to avoid replaying a poisoned session. Only **automatic retry** still inherits the session. Updates EN + ZH mirrors of `cli.mdx` and `tasks.mdx`. Co-authored-by: multica-agent <github@multica.ai> * docs(tasks): tighten rerun trigger surface; clean stale Go comments Apply review feedback on PR #2304: - `tasks.mdx` / `tasks.zh.mdx`: rerun is triggered via CLI or the `/api/issues/{id}/rerun` endpoint, not "UI or CLI" — there's no rerun affordance in web/desktop today. - `tasks.mdx` / `tasks.zh.mdx`: comparison table — manual rerun applies to "Issues with an agent assignee", not "All sources". The handler rejects with `issue is not assigned to an agent` for anything else, and there's no rerun path for chat or autopilot tasks. - `task_lifecycle.go`: `RerunIssue` doc comment claimed the new task "carries the most recent session_id/work_dir so the agent can resume". That has been false sinceb1345685— rewrite to reflect the actual `force_fresh_session=true` contract. - `agent.sql` (regenerated `agent.sql.go`): `GetLastTaskSession` doc said it serves "auto-retry / manual rerun"; manual rerun is now routed around it via `force_fresh_session=true`. Note both the auto-retry path it does serve and the rerun escape hatch. No logic change. Co-authored-by: multica-agent <github@multica.ai> --------- Co-authored-by: multica-agent <github@multica.ai>