mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-27 21:33:41 +02:00
40a984c997
* feat(quick-create): default assignee to picker agent when user didn't name one The quick-create prompt previously told the agent to OMIT --assignee when the user's input didn't name a person. That left almost every quick-created issue unassigned, which doesn't match user intent — the user opened quick-create with a specific agent picked, so that agent is the obvious owner. Both prompt surfaces (BuildPrompt for the dispatched message, plus the workflow block in injected CLAUDE.md / AGENTS.md) now instruct the agent: if the input doesn't name an assignee, pass `--assignee "<your name>"`. The picker agent's name is interpolated into the prompt at task-build time so the agent has a literal value to use rather than guessing its own name. The "explicitly named assignee → resolve via members" branch is unchanged. * refactor(execenv): drop duplicated quick-create field rules from CLAUDE.md/AGENTS.md The quick-create field rules (title / description / priority / assignee fallback / project / status) lived in two places — the per-turn user message built by BuildPrompt, and the workflow block injected into CLAUDE.md / AGENTS.md by buildMetaSkillContent. Same content, two sources, easy to update one and forget the other (the assignee-default change in this PR had to touch both). Quick-create is one-shot, so the per-turn user message is always present and is the natural single source of truth. The injected file's quick-create section now keeps only the hard guardrails: "do exactly one issue create, no issue get / status / comment add, exit on CLI error". Those guardrails stay in BOTH surfaces because they're the safety net for providers that don't propagate the user message into resumed-session context. renderQuickCreateContext (issue_context.md) was already guardrails-only — no change needed there.