@sebamomann/plants-mcp 2.8.0 → 2.8.2

package/CHANGELOG.md

@@ -3,6 +3,37 @@
 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
+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**

package/README.md

@@ -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) 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

@@ -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) 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.0",
+  "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",