From fdd5e82dfd446495d145fb767aa779d22b4e42ce Mon Sep 17 00:00:00 2001 From: Naiyuan Qing <145280634+NevilleQingNY@users.noreply.github.com> Date: Wed, 3 Jun 2026 17:05:58 +0800 Subject: [PATCH] feat(runtime): add source-authority escape hatch to the brief The brief already tells agents to run `--help` for command discovery, but nothing stated the trust precedence when a skill, the brief, or a doc seems to contradict actual behavior. Add one line to the Available Commands escape-hatch note: trust the live CLI (`--help`/`--output json`) and the checked-out source over source-traced prose that can lag the code, and verify on any conflict or confusion. Kept in the always-on brief (universal, needed before any skill loads) rather than duplicated into each skill; per-skill source-map pointers remain the specific layer. Co-Authored-By: Claude Opus 4.8 Co-authored-by: multica-agent --- server/internal/daemon/execenv/runtime_config.go | 1 + 1 file changed, 1 insertion(+) diff --git a/server/internal/daemon/execenv/runtime_config.go b/server/internal/daemon/execenv/runtime_config.go index 8b8959d03..65203d02b 100644 --- a/server/internal/daemon/execenv/runtime_config.go +++ b/server/internal/daemon/execenv/runtime_config.go @@ -425,6 +425,7 @@ func buildMetaSkillContent(provider string, ctx TaskContextForEnv) string { b.WriteString("## Available Commands\n\n") b.WriteString("**Use `--output json` for structured data.** Human table output now prints routable issue keys (for example `MUL-123`) and short UUID prefixes for workspace resources; use `--full-id` on list commands when you need canonical UUIDs.\n\n") b.WriteString("The default brief includes the commands needed for the core agent loop and common issue create/update tasks. For everything else, run `multica --help`, `multica --help`, or `multica --help`; prefer `--output json` when the command supports it.\n\n") + b.WriteString("When a skill, this brief, or a doc seems to disagree with what a command actually does — or you are unsure — trust the live CLI: `--help` and `--output json` reflect current behavior, and the checked-out source is the deeper authority when a repo is present. Skill and doc text is source-traced but can lag the code, so verify against the CLI or source on any conflict or confusion rather than trusting stale prose.\n\n") b.WriteString("### Core\n") b.WriteString("- `multica issue get --output json` — Get full issue details.\n") b.WriteString("- `multica issue comment list [--thread [--tail N] | --recent N] [--before --before-id ] [--since ] --output json` — List comments on an issue. Default returns the full flat timeline (server cap 2000). On busy issues prefer the thread-aware reads: `--thread ` returns one conversation (root + every reply); `--thread --tail N` caps replies to the N most recent (root is always included, even at `--tail 0`); `--recent N` returns the N most recently active threads. `--before` / `--before-id` walks older replies under `--thread --tail` (stderr label: `Next reply cursor`) or older threads under `--recent` (stderr label: `Next thread cursor`). `--since` is for incremental polling and may combine with `--thread` (with or without `--tail`) or `--recent`.\n")