@sebamomann/plants-mcp 2.7.1 → 2.8.1

package/CHANGELOG.md

@@ -3,6 +3,38 @@
 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.1 — 2026-09-29
+
+**Fertilizing schedule reads now match the app's calendar exactly.** Tool count unchanged (78
+overall). A **patch** bump — nothing renamed or removed:
+
+- `list_due_care`, `list_overdue_care`, and `get_care_calendar` gain `wateringAlignedOn` (a
+  `YYYY-MM-DD` day, `null` when absent) on every fertilizing entry: the day the app's calendar
+  water-align rule has attached that feeding to a watering, when it has. A feeding due before a
+  plant's next watering is grouped there unconditionally; one due shortly after may ride along with
+  it (within a third of the watering interval, capped at a quarter of the feeding's own cycle).
+  `get_care_calendar` now buckets a fertilizing entry on this effective day instead of its own, and
+  `list_due_care`/`list_overdue_care` judge their window and overdue membership by it too — a
+  feeding waiting on a future watering no longer shows as overdue even when its own due date has
+  passed. `nextDue` is unchanged: it still names the feeding's own due date.
+- A plant with no watering schedule (reservoir/hydro) no longer gets a fertilizing entry from any
+  of the three tools, matching the calendar's reservoir view — its fertilizing status is still
+  readable via `get_plant`/`list_plants`, just not asked for here.
+
+## 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 —

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
@@ -201,12 +201,21 @@ overrides the Apr–Sep default), `locationId`.
 | `get_care_calendar` | `GET /api/v1/care/calendar` | `days` (1–60, default 14) | Day-by-day projection plus an overdue group |
 | `list_care_recommendations` | `GET /api/v1/care/recommendations` | none | Detected problems: cycle mismatch, chronic lateness, missed seasonal fertilizing, fertilizer pause after repotting, repotting overdue, stale photos |
 
-Three things to know when reading schedule results:
+Four things to know when reading schedule results:
 
 - **Days, not timestamps.** `nextDue` and `date` are local `YYYY-MM-DD` strings — a UTC timestamp
   would render as the wrong day east of Greenwich.
 - **`neverLogged` is its own bucket.** A plant with a cycle but no event yet has no anchor, so no
   due date can be computed. Those are returned separately rather than reported as overdue.
+- **Fertilizing follows the app's calendar, including where it's grouped.** A fertilizing entry
+  carries `wateringAlignedOn` (a `YYYY-MM-DD` day, `null` when absent) — set when the app's
+  water-align rule has attached that feeding to a watering: unconditionally when it's due before
+  the plant's next watering, or when it's due shortly after and close enough to ride along.
+  `get_care_calendar` buckets the entry there instead of under its own date, and
+  `list_due_care`/`list_overdue_care` judge their window/overdue membership by the same day.
+  `nextDue` keeps its own meaning throughout — the feeding's own due date. A plant with no watering
+  schedule (reservoir/hydro) never gets a fertilizing entry from these tools at all, matching the
+  calendar's own reservoir view.
 - **Recommendations return i18n message keys plus values**, not rendered prose. Dismissed ones are
   excluded.
 
@@ -438,6 +447,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
@@ -474,6 +484,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 |
@@ -497,8 +512,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

@@ -84,7 +84,7 @@ const careArgs = {
         .describe("Override the season (Apr–Sep is summer). Defaults to the season of `date`."),
     locationId: z.number().int().optional().describe("Only consider plants in this location."),
 };
-server.tool("list_due_care", "What needs water or fertilizer now: overdue work plus anything due on the given day. Use `windowDays` to look ahead. This is the right tool for 'what should I do today?'.", {
+server.tool("list_due_care", "What needs water or fertilizer now: overdue work plus anything due on the given day. Use `windowDays` to look ahead. This is the right tool for 'what should I do today?'. A fertilizing entry carries `wateringAlignedOn` (YYYY-MM-DD, null when absent) when the app's calendar has grouped that feeding with a watering; `windowDays`/`includeOverdue` are judged by that day, not the feeding's own `nextDue` — see `get_care_calendar`'s description for the full rule.", {
     ...careArgs,
     windowDays: z
         .number()
@@ -98,8 +98,8 @@ server.tool("list_due_care", "What needs water or fertilizer now: overdue work p
         .optional()
         .describe("Include already-overdue work (default true)."),
 }, async (args) => apiGet("/api/v1/care/due", { ...args, includeOverdue: args.includeOverdue?.toString() }));
-server.tool("list_overdue_care", "Only work whose due date has already passed, most overdue first, with how many days each is late. Use for 'what have I fallen behind on?'.", careArgs, async (args) => apiGet("/api/v1/care/overdue", args));
-server.tool("get_care_calendar", "Day-by-day care schedule over a date range, plus an overdue group. Each plant appears on its next due day only — this projects the current schedule rather than simulating future waterings.", {
+server.tool("list_overdue_care", "Only work whose due date has already passed, most overdue first, with how many days each is late. Use for 'what have I fallen behind on?'. A feeding waiting on a future watering (`wateringAlignedOn` set — see `get_care_calendar`) is not listed here even when its own `nextDue` has passed: it's due on the watering's day, not neglected.", careArgs, async (args) => apiGet("/api/v1/care/overdue", args));
+server.tool("get_care_calendar", "Day-by-day care schedule over a date range, plus an overdue group. Each plant appears on its next due day only — this projects the current schedule rather than simulating future waterings. Fertilizing follows the app calendar's water-align rule: a feeding due before a plant's next watering is bucketed there unconditionally, and one due shortly after may ride along with it (within a third of the watering interval, capped at a quarter of the feeding's own cycle) — either way the fertilizing entry's `wateringAlignedOn` (YYYY-MM-DD) names that day and the bucket it's placed in follows it, while `nextDue` keeps the feeding's own, unchanged due date. A plant with no watering schedule (reservoir/hydro) never gets a fertilizing entry here at all — its fertilizing is entirely the reservoir view's job.", {
     ...careArgs,
     days: z.number().int().min(1).max(60).optional().describe("Number of days to project (default 14, max 60)."),
 }, async (args) => apiGet("/api/v1/care/calendar", args));
@@ -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.1",
-  "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.1",
+  "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>",