List the Korral stores this deployment is authorized to query, each with local time and closing time. Call this first to learn which store_id(s) are available — every other tool rejects a store_id not in this list. If exactly one store is authorized, store_id is optional on every other tool and defaults to it.

Assess whether a SKU at a store will run out before closing today, and whether a replenishment order would arrive in time. Combines current on-hand, recent sales velocity, and supplier lead time into one deterministic projection with an explicit confidence level and any data-quality caveats — the evidence used is included so the projection can be checked without another call. Use korral_list_recent_sales if you need the individual transactions behind the velocity figure (e.g. to check whether a single bulk sale skewed it).

List individual POS transactions for a SKU at a store, most recent first. Use this to see whether a sales velocity figure from korral_check_stock_risk was driven by many small baskets or a single large one (e.g. a catering order), or as the audit trail when a projection needs to be double-checked against what actually sold.

Look up the status of a replenishment order previously raised with korral_raise_replenishment_order, by its order_id. Use this to follow up on an order from an earlier session, or to check upstream state after a write call returned WRITE_OUTCOME_UNKNOWN before deciding whether to resubmit.

Raise a replenishment order for a SKU at a store. Defaults to a dry run: the response is a preview containing the exact order plus the on-hand, sales velocity, and stockout projection that justify it, a duplicate-order warning, and a quantity-sanity check — enough for a human to approve or reject without another tool call. Set confirm=true to execute, which also requires the deployment to have ALLOW_WRITES enabled. confirm=true reflects this agent's own judgment, not a recorded human approval — treat it accordingly.