@sebamomann/plants-mcp 2.8.1 → 2.8.2

package/CHANGELOG.md

@@ -3,6 +3,19 @@
 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.2 — 2026-09-29
+
+**Correction to 2.8.1.** Tool count unchanged (78). A **patch** bump — nothing renamed or removed:
+
+- 2.8.1 said a plant with no watering schedule (reservoir/hydro) gets no fertilizing entry from
+  `list_due_care`, `list_overdue_care` or `get_care_calendar`. That was too broad and is reverted:
+  such a plant has no watering for a feeding to attach itself to, so its `wateringAlignedOn` is
+  always `null` and the feeding stays on its own due date — but it is still listed, like any other
+  task. Those plants are fertilized from the app's fertilizing view, where the combined button
+  records a refill (hydro: a top-up) instead of a watering event; dropping them removed a real
+  capability. Anyone who read 2.8.1's note and stopped asking about reservoir plants' feedings
+  should start again.
+
 ## 2.8.1 — 2026-09-29
 
 **Fertilizing schedule reads now match the app's calendar exactly.** Tool count unchanged (78

package/README.md

@@ -214,8 +214,8 @@ Four things to know when reading schedule results:
   `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.
+  schedule (reservoir/hydro) has nothing to attach a feeding to, so its `wateringAlignedOn` is always
+  `null` and the feeding stays on its own date — it is still a real task.
 - **Recommendations return i18n message keys plus values**, not rendered prose. Dismissed ones are
   excluded.
 

package/dist/index.js

@@ -99,7 +99,7 @@ server.tool("list_due_care", "What needs water or fertilizer now: overdue work p
         .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?'. 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.", {
+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) has no watering to attach a feeding to, so its `wateringAlignedOn` is always null and the feeding stays on its own due date.", {
     ...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));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sebamomann/plants-mcp",
-  "version": "2.8.1",
+  "version": "2.8.2",
   "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",