multica

mirror of https://github.com/multica-ai/multica.git synced 2026-08-12 10:59:06 +02:00

Files

Jiang Bohan e02029337d fix(prompt): clarify --recent is paging, not a replacement (MUL-2387)

Address Elon's second-pass nit on #2816: the assignment-trigger workflow
in runtime_config.go used "you may switch to --recent 20", which reads as
a replacement for the mandatory full-history rule. Rephrase --recent as a
paging strategy ("read the full history page-by-page, not a shortcut that
replaces it") so it cannot conflict with the rule it lives next to.

The default per-turn prompt in prompt.go opened with "If you need comment
history" — that soft conditional contradicts the runtime workflow's
mandatory read. Move it to a neutral "For comment history, follow the
rule in your runtime workflow file" framing that defers to whatever the
workflow says (mandatory for assignment, optional elsewhere) instead of
encoding its own policy.

Keep the runtime/prompt dual-layer fallback intact — different runtimes
propagate the config file vs. the per-turn user prompt with varying
fidelity, so both surfaces need the guidance.

Tests pin the new phrasing against regression:

- TestBuildPromptDefaultMentionsRecent now also forbids "If you need
  comment history" from sneaking back in.
- TestInjectRuntimeConfigAssignmentTriggerMentionsRecent now also forbids
  "you may switch to" / "switch to `--recent" replacement phrasing.

Co-authored-by: multica-agent <github@multica.ai>

2026-05-19 14:31:46 +08:00

cmd

feat(comments): thread-aware list with composite cursor (MUL-2340) (#2787 )

2026-05-18 19:28:26 +08:00

internal

fix(prompt): clarify --recent is paging, not a replacement (MUL-2387)

2026-05-19 14:31:46 +08:00

migrations

feat(autopilots): webhook delivery layer + idempotency/signature/replay (MUL-2334) [PR1] (#2774 )

2026-05-18 14:59:40 +08:00

pkg

feat(comments): thread-aware list with composite cursor (MUL-2340) (#2787 )