brief_append uses `id`+`kind` params while sibling brief_* tools use `brief_id` — the inconsistency tripped a dispatched worker (2 retries to discover the signature).

Observed while shepherding a dispatched worker (flower-roster-slim-worker) completing briefs #137/#192. When it went to record its work, it first called brief_append with `brief_id` (the param name used by brief_dispatch_complete, brief_update_spec, brief_update_status, brief_ask, brief_answer, etc.), got a validation error, then had to discover that brief_append instead requires `id` + a required `kind` enum. It self-corrected after ~2 tries, but every worker/daemon calling brief_append will hit the same stumble. Suggestion: make the brief_* write surface consistent — either accept `brief_id` as an alias on brief_append (and recall_brief, which also takes `id`), or standardize the whole family on one identifier param name. The differing `id` vs `brief_id` across otherwise-sibling tools is a small but recurring papercut for agents.

{
    "tool": "brief_append",
    "impact": "dispatched worker retried ~2x",
    "observed_by": "flower-orchestrator",
    "brief_append_uses": "id + kind",
    "sibling_tools_use": "brief_id"
}

created

1d ago

triaged

—

resolved

—

resolved by

—