Commands › Clash Manager / Manager › Clash Manager Mark Result Resolved
Clash Manager Mark Result Resolved
Coming soon
Before you run this
clash id resolvable; current state permits transition to resolved.
After it runs
Delegates to ClashManagerUpdateResultStatusCommand.
When to use this
- Most frequent state transition — closing a reviewed clash.
Don't use this when
Non-resolved transitions — use UpdateResultStatusCommand.
Inputs
| Name | Kind | Type | Required | Default | Description |
|---|---|---|---|---|---|
PresetKind |
config | string |
no | "clash_tolerances" | Deterministic config preset |
Decision flow
1) clash id required. 2) Build audit comment "Resolved by {user} at {utc}." + optional justification. 3) Delegate to UpdateResultStatusCommand with to_state=resolved. 4) Emit result.
What you'll see in the chat
on start
Marking clash resolved…
thinking
Delegating to ClashManagerUpdateResultStatusCommand…
on success
Clash marked resolved.
on failure
Mark resolved 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_mark_result_resolved- Request body schema (from
[RestApiParam]) - Response schema (from
[RestApiResponse]) - curl / JS / Python code examples
Keywords & intent patterns
clashmanagermarkresultresolved · mark clash resolved · qa done shortcut
Related
| Pillar | Clash Manager / Manager |
|---|