@fullwell/fullwell 1.1.3 → 1.1.4

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "fullwell",
-  "version": "1.1.3",
+  "version": "1.1.4",
   "description": "Keep an evidence-backed family food journal with Claude.",
   "author": {
     "name": "Fullwell"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "fullwell",
-  "version": "1.1.3",
+  "version": "1.1.4",
   "description": "Keep an evidence-backed family food journal with Codex.",
   "homepage": "https://fullwell.souschefstudio.com/install",
   "license": "UNLICENSED",

package/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 ## Unreleased
 
+## 1.1.4 - 2026-07-21
+
+- Explain how snack purchase history powers familiar-product restocking and how recipe history helps recall family favorites before asking onboarding source questions, including when resuming a section.
+
 ## 1.1.3 - 2026-07-21
 
 - Read onboarding state, profiles, and the bounded item index once, keep the unconfirmed snack-and-recipe draft in the active conversation, and write it with one final `hfj_commit_onboarding` call after explicit confirmation.

package/install-metadata.json

@@ -1,6 +1,6 @@
 {
   "schema_version": 1,
-  "release": "1.1.3",
+  "release": "1.1.4",
   "mcp_url": "https://fullwell.souschefstudio.com/mcp",
   "install_page": "https://fullwell.souschefstudio.com/install",
   "platforms": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fullwell/fullwell",
-  "version": "1.1.3",
+  "version": "1.1.4",
   "private": false,
   "description": "Shared Codex and Claude client for Fullwell",
   "type": "module",

package/skills/audit-grocery-purchases/SKILL.md

@@ -8,7 +8,7 @@ description: Start or continue Fullwell snack onboarding and audit grocery purch
 Follow [the MCP contract](../../references/mcp-tool-contract.md), [semantic rules](../../references/semantic-food-rules.md), and [privacy rules](../../references/privacy-and-sharing.md).
 
 1. For a standalone audit, call `hfj_get_context` and choose an editable household. During guided first run, reuse the managing skill's context snapshot and do not call Fullwell tools before final confirmation.
-2. Read the snack profile from the guided snapshot, or call `hfj_get_profile` for a standalone audit. Reuse confirmed store scope and household preferences. Ask only for missing or changed stores, snack/drink preferences or exclusions that affect interpretation, and which installed browser the user authorizes for background access.
+2. Read the snack profile from the guided snapshot, or call `hfj_get_profile` for a standalone audit. When opening or resuming snack onboarding, explain once that learning from past orders lets Fullwell respond to a request such as "Restock cashews" with the familiar product instead of guessing, while still requiring confirmation before adding it to the cart. Do not call it "snack setup" without that context. Reuse confirmed store scope and household preferences. Ask only for missing or changed stores, snack/drink preferences or exclusions that affect interpretation, and which installed browser the user authorizes for background access.
 3. Before collecting any store, verify the user is already signed in to every authorized store. Never request credentials or one-time codes.
 4. Use a trailing 12-month window and recurrence threshold of two distinct orders unless the user requests different values. Inspect every qualifying order, expand every item list, and preserve exact store, order, date, and line-item evidence privately.
 5. In a standalone audit, call `hfj_append_evidence` in batches of at most 100 with the current HEAD and a stable idempotency key. In guided draft mode, retain typed evidence in the active conversation for `hfj_commit_onboarding`.

package/skills/manage-household-food-journal/SKILL.md

@@ -24,8 +24,8 @@ Keep the evolving draft only in the active conversation. Do not save it to a wor
 
 1. Use `onboarding`, both profiles, the bounded item identity index, and `items_truncated` from the single `hfj_get_context` response. Handle `snacks` first, then `recipes`; omit sections already `complete`.
 2. Revisit a previously skipped section only when no unskipped section remains and the user has started a later setup conversation. Its returned revision remains the final compare-and-set revision; do not write a resume transition.
-3. Start snacks from the snapshot's snack profile. Reuse confirmed stores and preferences without re-asking. Ask the first missing question about grocery stores the user orders from; after sources are named, ask only for browser authorization and preference or exclusion details needed to interpret the audit. Use the grocery-audit skill in guided draft mode. Unless the user asks to change them, use a trailing 12-month window and recurrence threshold of two distinct orders.
-4. After the snack draft is complete or locally marked skipped, start recipes from the snapshot's recipe profile. Reuse confirmed sources and preferences without re-asking. Ask where the user saves, finds, or discusses recipes, then only the source-scope, meaning, authorization, and preference questions needed for collection. Use the recipe-history skill in guided draft mode.
+3. Start snacks from the snapshot's snack profile. Before the first snack question, briefly explain the practical benefit in friendly, plain language, even when resuming: "Fullwell can help keep your family's favorite snacks stocked. Later, you can say, 'Restock cashews,' and I can use your past orders to identify the cashews you usually buy and help add them to your cart after you confirm. I just need to know which grocery sites to look on." Do not use an unexplained label such as "snack setup." Say the benefit once per section in this conversation, then reuse confirmed stores and preferences without re-asking. Ask the first missing question about grocery stores the user orders from; after sources are named, ask only for browser authorization and preference or exclusion details needed to interpret the audit. Use the grocery-audit skill in guided draft mode. Unless the user asks to change them, use a trailing 12-month window and recurrence threshold of two distinct orders.
+4. After the snack draft is complete or locally marked skipped, start recipes from the snapshot's recipe profile. Before the first recipe question, briefly explain the practical benefit in friendly, plain language, even when resuming: "Fullwell can remember the recipes your family saves, cooks, and likes. Later, you can ask, 'What was that pasta we loved?' or 'What should we make again?' and I can answer from your actual recipe history instead of guessing. I just need to know where you save or discuss recipes." Do not use an unexplained label such as "recipe setup." Say the benefit once per section in this conversation, then reuse confirmed sources and preferences without re-asking. Ask where the user saves, finds, or discusses recipes, then only the source-scope, meaning, authorization, and preference questions needed for collection. Use the recipe-history skill in guided draft mode.
 5. If the user naturally declines the current section, record a draft `skip` outcome with its snapshot revision and exactly one reason: `no_sources` when there are no applicable sources, `not_now` when they defer or say never mind, or `user_declined` for another refusal. Advance to the next section without asking permission. Do not revisit a section skipped in this guided run.
 6. Interpret meaning conversationally; never imitate keyword matching. If the user explicitly stops, cancels, or quits the whole setup, discard the uncommitted draft and end without a Fullwell write.
 7. Before any write, validate that the draft fits the final tool bounds and does not depend on an omitted item when `items_truncated` is true. If exact current items are required, explain why and use the narrow legacy read tools before presenting the confirmation. If the payload is too large, explain that bounded batches will be necessary instead of claiming one-write completion.

package/skills/track-recipe-history/SKILL.md

@@ -8,7 +8,7 @@ description: Start or continue Fullwell recipe onboarding and track recipe disco
 Follow [the MCP contract](../../references/mcp-tool-contract.md), [semantic rules](../../references/semantic-food-rules.md), and [privacy rules](../../references/privacy-and-sharing.md).
 
 1. For standalone tracking, call `hfj_get_context` and choose an editable household. During guided first run, reuse the managing skill's context snapshot and do not call Fullwell tools before final confirmation.
-2. Read the recipe profile from the guided snapshot, or call `hfj_get_profile` for standalone tracking. Reuse confirmed source scope, meaning, and household preferences. Ask only for missing or changed websites, bookmark services, notes, communications, preferences, and other authorized sources. For each site, clarify the whole discoverable site or exact subsection and what presence means.
+2. Read the recipe profile from the guided snapshot, or call `hfj_get_profile` for standalone tracking. When opening or resuming recipe onboarding, explain once that remembering what the family saves, cooks, and likes lets Fullwell answer questions such as "What was that pasta we loved?" or "What should we make again?" from their actual history. Do not call it "recipe setup" without that context. Reuse confirmed source scope, meaning, and household preferences. Ask only for missing or changed websites, bookmark services, notes, communications, preferences, and other authorized sources. For each site, clarify the whole discoverable site or exact subsection and what presence means.
 3. Verify access and sign-in before collection without requesting credentials. Inspect every authorized occurrence, including duplicates and conflicts.
 4. Preserve discovery, cooking, confirmation, or correction evidence before conclusions, including canonical URL, audited page, displayed image URL, author/publisher, scope meaning, dates, limitations, and provenance. In guided draft mode, retain the typed evidence in the active conversation; otherwise append it with `hfj_append_evidence`.
 5. Use the guided snapshot item index, or `hfj_search_items` and `hfj_get_item` for standalone tracking, to find current candidates. If the index is truncated or lacks enough detail for a safe update, return the exact missing reads to the managing skill. Decide recipe identity in reasoning. Keep Saved, Cooked, and Liked independent.