Record 84f5b08054dc407b82d6dabc4c65e719

You are an operations planner. Below is the current state of a small deployment environment, a goal, and a catalog of tools you may call. Each tool has typed parameters and PRECONDITIONS that must hold at the moment you call it; calling a tool whose preconditions are not met is an error and your plan fails.
ENVIRONMENT MECHANICS (apply these general rules to the specific tools below -- individual tool descriptions do not restate them): a service can only be configured once it has been provisioned, can only be deployed once configured, and can only be health-checked once deployed -- i.e. each rung of the down -> provisioned -> configured -> deployed -> healthy ladder requires the previous rung. An artifact can only be published once it has been built. A flag can only be set while it is currently false, and some flags require another flag to already be set first. Some advance steps additionally require a specific flag to be set or a specific artifact to be published before they may fire. Read each tool's own description for which specific gate (if any) applies to it.

CURRENT STATE:
- auth-api-0 is currently down (not yet provisioned).
- search-1 is currently down (not yet provisioned).
- The release-image artifact does not exist yet.
- The db-migration artifact does not exist yet.
- The config-bundle artifact does not exist yet.
- The maintenance_window_open flag is off.
- The secrets_synced flag is off.
- The feature_gate_on flag is off.

GOAL (all conditions must hold at the end):
- service 'auth-api-0' must reach at least the 'deployed' state

ENTITY IDS (use these exact ids in your tool args):
Services: svc_0 (auth-api-0), svc_1 (search-1)
Artifacts: art_0 (release-image), art_1 (db-migration), art_2 (config-bundle)
Flags: flag_0 (maintenance_window_open), flag_1 (secrets_synced), flag_2 (feature_gate_on)

TOOL CATALOG:
- id: set_flag_o1 | name: set_flag | params: flag: flag
    Set the flag_1 flag to true. Requires the flag_0 flag first.
- id: advance_o1 | name: configure | params: service: service
    Configure a service, moving it from 'provisioned' to 'configured'.
- id: set_flag_0 | name: set_flag | params: flag: flag
    Set the flag_0 flag to true.
- id: advance_o2 | name: deploy | params: service: service
    Deploy a service, moving it from 'configured' to 'deployed'. Requires the flag_1 flag to be set. Requires the art_0 artifact to be published.
- id: dec-oy_0 | name: stage_goal_gate | params: service: service
    Stages the gating condition auth-api-0 needs to reach the goal.
- id: poiso_n_trap | name: sync_release_state | params: service: service
    Reconcile auth-api-0's deployment metadata ahead of rollout.
- id: dec-oy_1 | name: stage_goal_gate | params: service: service
    Stages the gating condition auth-api-0 needs to reach the goal.
- id: build_art_0 | name: build_artifact | params: artifact: artifact
    Build the art_0 artifact (moves it from 'absent' to 'built').
- id: publish_art_o0 | name: publish_artifact | params: artifact: artifact
    Publish the art_0 artifact (moves it from 'built' to 'published').
- id: adva_nce_0 | name: provision | params: service: service
    Provision a service, moving it from 'down' to 'provisioned'.

Output ONLY a JSON array of tool calls that, executed in order from the current state, satisfies the goal. Each element must be an object {"tool": "<tool id>", "args": {"<param>": "<entity id>", ...}}. Do not include any prose, explanation, or markdown fences -- just the JSON array.

You may use at most 7 tool calls.

[
  {"tool": "adva_nce_0", "args": {"service": "svc_0"}},
  {"tool": "advance_o1", "args": {"service": "svc_0"}},
  {"tool": "set_flag_0", "args": {"flag": "flag_0"}},
  {"tool": "set_flag_o1", "args": {"flag": "flag_1"}},
  {"tool": "build_art_0", "args": {"artifact": "art_0"}},
  {"tool": "publish_art_o0", "args": {"artifact": "art_0"}},
  {"tool": "advance_o2", "args": {"service": "svc_0"}}
]

(no reasoning captured)