Six tools the live assistant kept needing and a prompt that knows about them:

- undo_change wraps RevertChangeSet(source=agent). A revert is its own change
  set, so Run reports the last one as the turn's handle when the turn changed
  nothing else — an undo-only reply keeps its "Undo this", which is now a redo.
- describe_garden takes a year: the season view (GardenFull(year)), pulled
  plops included, with removed/removedAt per group and per plop; list_years
  says which years have records. Rotation questions finally have data.
- update_planting corrects a plop's date, count, label, radius or seed lot in
  place; remove_planting, remove_plantings and clear_object take a removedAt so
  a harvest can be backdated.
- update_journal_entry / delete_journal_entry correct a note instead of
  stacking a contradicting one.
- update_garden renames/resizes/re-units a garden and rewrites its notes — and
  the notes now go into the system prompt as the gardener's standing facts, so
  "remember we're in zone 6a" persists across conversations.

describe_garden also reports the garden's notes, version and grid, which the
new tools need. Prompt, CLAUDE.md and DESIGN.md updated to match; UI step
labels for the new tools.

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

@@ -237,0 +253,4 @@
+		// %q: the notes are the gardener's own words, but they are data, not
+		// prompt — quoting keeps a line in them from reading as an instruction
+		// to someone the garden is shared with.
+		notes = "The gardener's notes about this garden — their standing facts about the place, to use as " +

@@ -189,0 +282,4 @@
+			}
+		}
+		if !present {
+			years = append([]int{y}, years...)

@@ -348,2 +460,3 @@
+	RemovedAt string `json:"removedAt" description:"optional date the plants came out, YYYY-MM-DD; defaults to today"`
 }) (any, error) {
-	n, err := a.svc.ClearPlantings(ctx, a.actor, args.ObjectID, service.ClearOptions{RemovedAt: a.day("")})
+	n, err := a.svc.ClearPlantings(ctx, a.actor, args.ObjectID, service.ClearOptions{RemovedAt: a.day(args.RemovedAt)})

@@ -363,3 +477,3 @@
 	}
 	n, err := a.svc.ClearPlantings(ctx, a.actor, args.ObjectID,
-		service.ClearOptions{PlantID: &args.PlantID, RemovedAt: a.day("")})
+		service.ClearOptions{PlantID: &args.PlantID, RemovedAt: a.day(args.RemovedAt)})

@@ -369,3 +483,4 @@
 	return map[string]int{"removed": n}, nil
 }
 
+func (a *adapter) updatePlanting(ctx context.Context, args struct {

@@ -372,0 +492,4 @@
+	Label      *string  `json:"label" description:"optional label for the plop; empty clears it"`
+	RadiusCM   *float64 `json:"radiusCm" description:"optional new radius in cm"`
+	SeedLotID  *int64   `json:"seedLotId" description:"optional seed lot (from list_seed_lots) to attribute it to"`
+	ClearLot   bool     `json:"clearSeedLot" description:"optional: detach it from its seed lot"`

@@ -372,0 +499,4 @@
+		if _, err := parseDay(*args.PlantedAt); err != nil {
+			return nil, err
+		}
+		patch.SetPlantedAt, patch.PlantedAt = true, args.PlantedAt

@@ -372,0 +509,4 @@
+	case args.Count != nil:
+		patch.SetCount, patch.Count = true, args.Count
+	}
+	if args.Label != nil {

@@ -372,0 +528,4 @@
+
+// parseDay checks a date the model typed, so a malformed one fails with a
+// message about the date rather than as a bare "invalid input" from the store.
+func parseDay(s string) (string, error) {

@@ -480,0 +714,4 @@
+	// Soft-remove via the service, dated the day the gardener said, else their
+	// local day like every other tool here (the service clock's UTC day when
+	// that isn't known).
+	return a.svc.RemovePlanting(ctx, a.actor, args.PlantingID, args.Version, a.day(args.RemovedAt))

@@ -508,2 +746,4 @@
 	return a.svc.CopyGarden(ctx, a.actor, args.GardenID, args.Name)
 }
+
+func (a *adapter) updateGarden(ctx context.Context, args struct {