Twenty-one prompts against the live assistant found one fabricated success,
a model that believed it was 2025, and a describe_garden that was ~450 plop
entries per turn. This is the set of fixes, each traceable to a finding:

- The gardener's LOCAL day travels with the turn (`today` on POST /agent/chat,
  sent by the UI like plantedAt) into the system prompt and every dated tool
  default. Left to guess, the model dated journal entries a year back; left to
  the server, a 9 pm fill landed on UTC's tomorrow.
- describe_garden groups plops by plant — count, where, planted date, days to
  maturity — and lists ids only for groups of ≤ 8; list_plantings spells a big
  group out on demand and remove_plantings acts on one plant in a bed ("take
  the beets out, leave the garlic"), which used to mean 116 single removals.
- New tools: move_planting (keeps the planting date; across beds via the new
  MovePlanting, which is why the store's UPDATE now writes object_id),
  update_plant, read_history, copy_garden (the "<garden> — <year>" plan
  convention). fill_region takes an explicit local rectangle and a seedLotId;
  place_planting's radius defaults to one plant (spacing/2) instead of a guess.
- The system prompt states the date and the gardener's units, forbids claiming
  a change no tool made, says it cannot undo and points at the Undo button,
  asks before clearing beds on an ambiguous sentence, and stops narrating its
  own plantings into the journal.
- A mutation aimed at ANOTHER garden inside a turn is recorded under that
  garden as its own change set, not filed into the open scope.
- UI: the thread scrolls inside the Assistant panel so the composer stays
  put; every tool has a step label; wide tables stay inside the bubble.

Co-Authored-By: Claude Fable 5 <[email protected]>

@@ -228,0 +261,4 @@
+- fill_region in grid mode lays out individual plants at true spacing, which is what "so I can
+  plant from it" means; clump mode is a quick sketch. For an area no compass name describes (a
+  middle third, a strip along one edge) give fill_region a rectangle instead of placing plops by hand.
+- A garden named "%s — <year>" is this garden's plan for that year; copy_garden with that name

@@ -44,0 +72,4 @@
+		llm.DefineTool("remove_planting",
+			"Remove ONE plop from a bed, leaving the rest — the single-plant answer to clear_object's "+
+				"all-or-nothing. Soft-removes it (kept for planting history, undoable), like clearing a "+
+				"bed does. Needs the plop's id and version from describe_garden. Use for \"pull the "+

@@ -169,0 +256,4 @@
+	given := 0
+	for _, v := range rect {
+		if v != nil {
+			given++

@@ -169,0 +261,4 @@
+	}
+	switch {
+	case given == 4 && strings.TrimSpace(args.Region) == "":
+		spec.Region = service.Region{MinX: *args.X0CM, MinY: *args.Y0CM, MaxX: *args.X1CM, MaxY: *args.Y1CM}

@@ -216,1 +350,4 @@
 
+func (a *adapter) removePlantings(ctx context.Context, args struct {
+	ObjectID int64 `json:"objectId" description:"object to remove the plant from"`
+	PlantID  int64 `json:"plantId" description:"the plant to remove every plop of (from describe_garden)"`

@@ -239,0 +393,4 @@
+	Changes string `json:"changes"`
+	Undone  bool   `json:"undone,omitempty"`
+	// Undo is set when this entry is itself an undo of an earlier one.
+	Undo *int64 `json:"undoOf,omitempty"`