fix(giellie): say what "applied" means on a dry run

On a dry run nothing is written, so a row the engine reports as
applied only means it would be applied. The tool description said
none of that, and a reader of the description alone still got the
old ambiguity.
This commit is contained in:
Dave 2026-11-06 00:52:35 +02:00
parent 0db696c898
commit 9813732e5f

View file

@ -2211,7 +2211,7 @@ const tools = [
'Use mode "set" when the number is the new quantity on hand (the stocktake case), and mode "add" when it is a change to add to the current quantity. ' +
"Each line is resolved by exact SKU first, then by a description match (flagged as such). A line that cannot be resolved is reported, never guessed. " +
"Quantities are truncated to whole units. One SKU may appear only once in a batch — a repeated SKU rejects the whole batch, so split the paste. " +
"Pass dry_run true first to preview the before/after plan. Quantities may be negative — the till oversells on purpose and the stocktake corrects it. " +
"Pass dry_run true first to preview the before/after plan; on a dry run a row reported as applied only means would be applied, because nothing is written. Quantities may be negative — the till oversells on purpose and the stocktake corrects it. " +
"Writes a stock_ledger row against the acting user and mirrors the new quantity onto the price-list catalogue.",
inputSchema: {
type: "object",