Commands  ›  Clash Manager / Manager  ›  Clash Manager Update Result Status

Clash Manager Update Result Status

Clash Manager / Manager writes to model Public API · not yet exposed

Coming soon

Before you run this

clash id resolvable; to state is a valid transition.

After it runs

Single SQLite UPDATE via repo.TransitionState.

When to use this

Don't use this when

fix_status transitions — separate command.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) clash id + to state required; validate to_state ∈ {new, active, reviewed, resolved, ignored}.
2) Load row; compare from_state to enforce a valid transition path (ValidTransitions table).
3) repo.TransitionState(id, to_state, comment?).
4) Emit ok + from/to.

What you'll see in the chat

on start
Transitioning clash state…
thinking
Validating transition against allowed set…
Writing via ClashesRepository…
on success
State {from_state} → {to_state}.
on failure
State update failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/clash_manager_update_result_status
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashmanagerupdateresultstatus · update clash state · qa state transition

PillarClash Manager / Manager