@sebamomann/plants-mcp 2.7.0 → 2.8.0

package/CHANGELOG.md

@@ -3,6 +3,30 @@
 Notable changes to `@sebamomann/plants-mcp`. Versioning is semver against the **tool surface** —
 see the table in `AGENTS.md` for what counts as major, minor, and patch.
 
+## 2.8.0 — 2026-09-27
+
+**Is it still a cutting?** 78 tools registered overall (28 read, 32 write, 18 admin). A **minor**
+bump — one new tool and one new enum value, nothing renamed or removed:
+
+- `establish_propagation` — promote a `PROPAGATING` plant to `ESTABLISHED`, stamping
+  `establishedAt` to now. The same one-way transition the app's plant edit form applies manually,
+  and the action behind the new `propagationCheckDue` care recommendation.
+- `list_care_recommendations`/`dismiss_care_recommendation` gain `propagationCheckDue`: a plant
+  left `PROPAGATING` long enough is now flagged, asking whether it should be promoted. Its
+  dismissal is deliberately temporary (it re-fires a few weeks later) rather than permanent, so a
+  stale `PROPAGATING` row can't silently skew the propagation success rate in `collection_stats`
+  forever.
+
+## 2.7.1 — 2026-09-26
+
+**A moved watering carries its feeding.** Tool count unchanged (77 overall). A **patch** bump —
+nothing renamed or removed, and the change is in the app's behaviour plus `snooze_care`'s wording:
+
+- `snooze_care` on the `water` axis now also snoozes a fertilizing due date that falls between today
+  and the watering's new day — fertilizer goes into the watering can, so a feeding left in between
+  would have nothing to deliver it. The extra row is **added** to the response as `fertRider` (`null`
+  when nothing moved), so existing callers are unaffected. An already-overdue feeding stays put.
+
 ## 2.7.0 — 2026-09-24
 
 **Nudges.** 77 tools registered overall (28 read, 31 write, 18 admin). A **minor** bump — one new

package/README.md

@@ -60,7 +60,7 @@ needs a running Sprig instance and an API key from it. Start at the
 
 ## What an assistant can do
 
-**77 tools** over your collection: 28 that read it, 31 that write to it. **18 admin tools** are also
+**78 tools** over your collection: 28 that read it, 32 that write to it. **18 admin tools** are also
 available — but only to a key created by an admin — for finding and understanding duplicates in the
 shared global plant type catalog, restructuring its genus/species/cultivar tree, reading, directly
 editing, merging, and reviewing proposals and duplicate candidates in that catalog, and (7 read-only,
@@ -111,7 +111,7 @@ healthy server, not a hang — press Ctrl-C.
 The scope lives on the API key, is enforced by the app, and cannot be widened from this side.
 
 - **`read`** — on every key. Gates all 28 read tools.
-- **`write`** — opt-in when you create the key. Gates the 31 write tools.
+- **`write`** — opt-in when you create the key. Gates the 32 write tools.
 - **`admin`** — only offered when the key's creator is themselves an admin, and only while they
   still are one (the app re-checks this on every admin-tool call, not just at key creation). Gates
   the 18 admin catalog tools — 7 read-only, 11 that write — see **Admin tools** below. `admin` alone
@@ -380,6 +380,12 @@ hub offers. `originalDueAt` is the due date being pushed out (`nextDue` from `li
 an overdue plant means three days from now) or `snoozedUntil` (an explicit day: tomorrow at the
 earliest, at most a year out).
 
+Moving a **watering** past a feeding that was due before it moves that feeding too: fertilizer goes
+into the watering can, so a feeding left between today and the watering's new day would have nothing
+to deliver it. The second snooze comes back as `fertRider` on the response (`null` when nothing rode
+along), so it can be reported rather than discovered later. An already-overdue feeding is left where
+it is — that backlog is not the watering's doing.
+
 ### Plant edits
 
 | Tool | Endpoint | Arguments |
@@ -432,6 +438,7 @@ don't exist yet, `propagate_plant` creates them *and* sets the link in one call.
 | `unmerge_plant` | `POST /api/v1/plants/:id/unmerge` | `plantId` **(required)** |
 | `set_plant_status` | `PATCH /api/v1/plants/:id/status` | `plantId`, `status` (`LIVING`\|`DEAD`\|`LOST`) **(both required)**, plus `deadDeclaredAt`/`deathCause` (only apply when `status` is `DEAD`) |
 | `set_plant_reference` | `PATCH /api/v1/plants/:id/reference` | `plantId`, `reference` (boolean) **(both required)** |
+| `establish_propagation` | `PATCH /api/v1/plants/:id/establish` | `plantId` **(required)** |
 
 `create_plant`'s `plantTypeId` is now **optional**: pass an existing global type id (from
 `list_plant_types`/`search_plant_types`) when the species is known, or omit it (or pass `null`) to
@@ -468,6 +475,11 @@ Marking a plant as a reference also removes it from any vacation plan, since a r
 never cared for. `create_plant`'s `reference: true` covers making a *new* reference plant; this is
 for converting one already in the collection.
 
+`establish_propagation` promotes a `PROPAGATING` plant to `ESTABLISHED` and stamps `establishedAt`
+to now — the same one-way transition the app's plant edit form applies manually, and the action
+behind the `propagationCheckDue` recommendation ("is it still a cutting?", see **Recommendations**
+below) on the Improvements page. It answers HTTP 400 if the plant isn't currently `PROPAGATING`.
+
 ### Health entries
 
 | Tool | Endpoint | Arguments |
@@ -491,8 +503,15 @@ Pass all three **exactly as returned by `list_care_recommendations`**. The `fing
 that specific occurrence, so dismissing one never suppresses a later, different recurrence.
 
 Dismissible `type` values: `wateringOftenLate`, `fertilizingOftenLate`, `noFertilizerThisSeason`,
-`recentlyRepottedAvoidFertilizer`, `noRecentPhoto`. `wateringCycleMismatch` is **not** dismissible —
-it is a configuration contradiction, fixed by editing the plant rather than hidden.
+`recentlyRepottedAvoidFertilizer`, `noRecentPhoto`, `propagationCheckDue`. `wateringCycleMismatch` is
+**not** dismissible — it is a configuration contradiction, fixed by editing the plant rather than
+hidden.
+
+`propagationCheckDue` ("is it still a cutting?") fires for a plant that has been `PROPAGATING` for a
+while and asks whether it has rooted. Dismissing it only hides it for a few weeks, not permanently —
+it re-fires periodically rather than letting a stale `PROPAGATING` row silently skew the propagation
+success rate in `collection_stats`. `establish_propagation` (see **Plant lifecycle** above) is how an
+assistant acts on it — promoting the plant is the actual fix, not just dismissing the prompt.
 
 ### Wishlist
 

package/dist/index.js

@@ -176,7 +176,7 @@ server.tool("record_hydro_event", "WRITE: log a hydro-culture event for a hydro-
     recordedAt: optionalPlantDate(""),
     notes: z.string().max(2000).optional().describe("Free-text notes."),
 }, async ({ plantId, ...body }) => apiSend("POST", `/api/v1/plants/${plantId}/hydro`, body));
-server.tool("snooze_care", "WRITE: postpone a plant's next watering or fertilizing due date — the same snooze picker the care hub offers. originalDueAt is the due date being pushed out (the nextDue value from list_due_care/get_care_calendar for that plant/careType), not today's date. Pass exactly one of durationDays (a preset: 1, 3, 7, or 14 days, counted from originalDueAt or from today when that date has already passed) or snoozedUntil (an explicit YYYY-MM-DD day, tomorrow at the earliest and at most a year out). Requires a write-scoped API key.", {
+server.tool("snooze_care", "WRITE: postpone a plant's next watering or fertilizing due date — the same snooze picker the care hub offers. originalDueAt is the due date being pushed out (the nextDue value from list_due_care/get_care_calendar for that plant/careType), not today's date. Pass exactly one of durationDays (a preset: 1, 3, 7, or 14 days, counted from originalDueAt or from today when that date has already passed) or snoozedUntil (an explicit YYYY-MM-DD day, tomorrow at the earliest and at most a year out). Moving a WATERING past a feeding that was due before it moves that feeding onto the same day too — fertilizer goes into the watering can, so a feeding left in between would have nothing to deliver it; that second snooze comes back as fertRider (null when nothing moved), and an already-overdue feeding is left where it is. Requires a write-scoped API key.", {
     plantId: z.number().int().positive().describe("Plant id."),
     careType: z.enum(["water", "fert"]).describe("Which schedule to postpone."),
     durationDays: z.union([z.literal(1), z.literal(3), z.literal(7), z.literal(14)]).optional().describe("Snooze duration in days — one of the app's presets, counted from originalDueAt, or from today if that date has passed. Omit when passing snoozedUntil."),
@@ -238,6 +238,7 @@ server.tool("dismiss_care_recommendation", "WRITE: hide one care recommendation,
         "noFertilizerThisSeason",
         "recentlyRepottedAvoidFertilizer",
         "noRecentPhoto",
+        "propagationCheckDue",
     ])
         .describe("Recommendation type, from list_care_recommendations."),
     fingerprint: z.string().min(1).describe("Occurrence fingerprint, from list_care_recommendations."),
@@ -289,6 +290,9 @@ server.tool("set_plant_reference", "WRITE: flip a plant between LIVING (the call
     plantId: z.number().int().positive().describe("Plant id."),
     reference: z.boolean().describe("true: mark as a reference plant (must be LIVING now). false: turn a reference plant back into the caller's own (must be EXTERNAL now)."),
 }, async ({ plantId, reference }) => apiSend("PATCH", `/api/v1/plants/${plantId}/reference`, { reference }));
+server.tool("establish_propagation", "WRITE: promote a plant from PROPAGATING to ESTABLISHED, stamping establishedAt to now. This is the same one-way transition the app's plant edit form applies manually, and the action behind the 'is it still a cutting?' recommendation (propagationCheckDue, from list_care_recommendations) on the Improvements page. Fails with a 400 if the plant is not currently PROPAGATING. Requires a write-scoped API key.", {
+    plantId: z.number().int().positive().describe("The PROPAGATING plant to promote."),
+}, async ({ plantId }) => apiSend("PATCH", `/api/v1/plants/${plantId}/establish`));
 // --- Wishlist ----------------------------------------------------------
 /**
  * The caller's personal wishlist (R2-15) — plants they want but don't own

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@sebamomann/plants-mcp",
-  "version": "2.7.0",
-  "description": "MCP server for the Sprig plant app: 77 tools to read a plant collection, browse the shared global plant type catalog, log care (watering, fertilizing, repotting, refills, hydro events), edit a plant's identity/care/lifecycle status, add, propagate or merge plants, snooze a due date, check for nudges worth mentioning, manage a wishlist and notifications, watch a plant type for changes, check vacation status, read past problem diagnoses, create a location/soil/fertilizer/pot, and contribute a new species to the catalog. Read-only by default; writes need a write-scoped API key. Two tools can delete a watering/fertilization event; nothing else deletes collection history. 18 more tools read, edit, merge and review the shared global plant type catalog and the instance's operational status (queues, catalog health, activity, growth, community, trade and content aggregates) for an admin-scoped key.",
+  "version": "2.8.0",
+  "description": "MCP server for the Sprig plant app: 78 tools to read a plant collection, browse the shared global plant type catalog, log care (watering, fertilizing, repotting, refills, hydro events), edit a plant's identity/care/lifecycle status, add, propagate or merge plants, snooze a due date, check for nudges worth mentioning, manage a wishlist and notifications, watch a plant type for changes, check vacation status, read past problem diagnoses, create a location/soil/fertilizer/pot, and contribute a new species to the catalog. Read-only by default; writes need a write-scoped API key. Two tools can delete a watering/fertilization event; nothing else deletes collection history. 18 more tools read, edit, merge and review the shared global plant type catalog and the instance's operational status (queues, catalog health, activity, growth, community, trade and content aggregates) for an admin-scoped key.",
   "type": "module",
   "license": "MIT",
   "author": "sebamomann <github@sebamomann.de>",