@fullwell/fullwell 1.1.1 → 1.1.2

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "fullwell",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "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.1",
+  "version": "1.1.2",
   "description": "Keep an evidence-backed family food journal with Codex.",
   "homepage": "https://fullwell.souschefstudio.com/install",
   "license": "UNLICENSED",

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## Unreleased
 
+## 1.1.2 - 2026-07-21
+
+- Route a bare `@Fullwell hi` through unresolved onboarding before general help, starting snacks and then recipes with only the missing source, authorization, and preference questions each audit needs.
+- Add an exact bare-greeting regression eval and forbid generic greetings while onboarding remains open.
+
 ## 1.1.1 - 2026-07-21
 
 - Renamed the public Codex and Claude plugin selectors to `fullwell@fullwell` while retaining the `@fullwell/fullwell` npm package and `household-food-journal` MCP service identifier.

package/README.md

@@ -2,7 +2,7 @@
 
 One shared skill package connects Codex and Claude to the hosted Household Food Journal MCP service and defines the local-only grocery-restocking workflow. The service performs authentication and all canonical journal mutations; this package contains no credentials, household data, Git client, or synchronization state.
 
-After installation, start with `@Fullwell hi` in Codex or `Set up Fullwell.` in Claude. The shared skills ask about grocery sources first and recipe sources second, skip a declined section without showing a setup menu, and resume per-user progress through the hosted MCP service. A section is complete only when its canonical household report exists.
+After installation, start with `@Fullwell hi` in Codex or `Set up Fullwell.` in Claude. A bare greeting checks onboarding state before replying: while work remains, the shared skills begin snacks, ask only for missing source authorization and preferences, then advance to recipes without a setup menu or generic help question. A declined section is skipped and per-user progress resumes through the hosted MCP service. A section is complete only when its canonical household report exists.
 
 The restocking skill reads only a private revisioned snapshot prepared by `@fullwell/local-runner`. Product selection and retailer cart control stay on the user's Mac; the WhatsApp gateway relays encrypted user-facing text and transport state only.
 

package/install-metadata.json

@@ -1,6 +1,6 @@
 {
   "schema_version": 1,
-  "release": "1.1.1",
+  "release": "1.1.2",
   "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.1",
+  "version": "1.1.2",
   "private": false,
   "description": "Shared Codex and Claude client for Fullwell",
   "type": "module",

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

@@ -1,6 +1,6 @@
 ---
 name: audit-grocery-purchases
-description: Audit grocery purchase histories for snacks and drinks, update pantry profiles, compare stores, or recalculate evidence-backed recurrence reports.
+description: Start or continue Fullwell snack onboarding and audit grocery purchase histories for snacks and drinks, including store scope, browser authorization, household preferences, pantry profiles, comparisons, and evidence-backed recurrence reports.
 ---
 
 # Audit Grocery Purchases
@@ -8,7 +8,7 @@ description: Audit grocery purchase histories for snacks and drinks, update pant
 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. Call `hfj_get_context` and choose an editable household. If snack onboarding is `not_started`, call `hfj_update_onboarding` with `transition.action: "start"` and `expected_revision: 0`; if it is `skipped`, resume it with the returned revision. Do not mutate a `complete` section.
-2. Call `hfj_get_profile` for `snacks`. Ask which stores to inspect when the profile is absent, then ask which installed browser the user authorizes for background access.
+2. Call `hfj_get_profile` for `snacks`. 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. Call `hfj_append_evidence` in batches of at most 100 with the current HEAD and a stable idempotency key.

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

@@ -1,6 +1,6 @@
 ---
 name: manage-household-food-journal
-description: Start or resume Fullwell's conversational first run, set up or migrate a household food journal, authenticate, manage family access, or export data.
+description: Handle every Fullwell greeting or setup request, including a bare @Fullwell hi, by checking unresolved snack-then-recipe onboarding before general help; also authenticate, select or migrate a household, manage family access, profiles, and exports.
 ---
 
 # Manage Household Food Journal
@@ -9,7 +9,7 @@ Use the hosted MCP service for all reads and writes. Follow [the MCP contract](.
 
 ## Start or resume
 
-1. Call `hfj_get_context`.
+1. Call `hfj_get_context` before replying to any Fullwell greeting or setup request.
 2. If authentication is required, tell the user to finish in the service browser window. Never request a token.
 3. Resume a pending family invitation or collection import before ordinary setup.
 4. If there is no pending intent and no household, ask for a short household name and call `hfj_create_household` with an idempotency key.
@@ -18,13 +18,13 @@ Use the hosted MCP service for all reads and writes. Follow [the MCP contract](.
 
 ## Guided first run
 
-When the user greets Fullwell, asks to set it up, or selects the setup starter, begin the questions below. Do not ask what they want to set up and do not present snacks-versus-recipes choices.
+Treat every greeting addressed to Fullwell, including a bare `@Fullwell hi`, as a request to start or resume guided first run. If `hfj_get_context` reports any `not_started`, `in_progress`, or `skipped` section, continue the flow in the same response after the required tool calls. Do not return a generic greeting, list capabilities, ask what is on the user's mind, ask what they want to set up, or present snacks-versus-recipes choices while onboarding work remains. General help is appropriate only when both sections are `complete`.
 
 1. Use the `onboarding` object from `hfj_get_context`. Handle `snacks` first, then `recipes`.
 2. For a `not_started` section, call `hfj_update_onboarding` with `transition: { "action": "start" }` and `expected_revision: 0` before asking its first question. For `in_progress`, continue without another transition. For `complete`, advance immediately.
 3. Leave a `skipped` section alone while another section is `not_started` or `in_progress`. On a later greeting or setup request, when no such section remains, call `hfj_update_onboarding` with `transition: { "action": "resume" }` and the returned revision before revisiting the earliest skipped section. Never revisit a section during the same guided run in which the user skipped it.
-4. Start snacks by asking which grocery stores the user orders from. Use the grocery-audit skill for the remaining source authorization and audit. Unless the user asks to change them, use a trailing 12-month window and a recurrence threshold of two distinct orders instead of asking extra setup questions.
-5. After snacks completes or is skipped, start recipes by asking where the user saves, finds, or discusses recipes. Use the recipe-history skill for source scope, meaning, authorization, and collection.
+4. Start snacks by calling `hfj_get_profile` for `snacks`. 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 the browser authorization and preference or exclusion details needed to interpret the audit. Use the grocery-audit skill for collection. Unless the user asks to change them, use a trailing 12-month window and a recurrence threshold of two distinct orders instead of asking extra setup questions.
+5. After snacks completes or is skipped, start recipes by calling `hfj_get_profile` for `recipes`. Reuse confirmed sources and preferences without re-asking. Ask where the user saves, finds, or discusses recipes, then ask only the source-scope, meaning, authorization, and preference questions needed for collection. Use the recipe-history skill for the audit.
 6. If the user naturally declines the current section, call `hfj_update_onboarding` with `transition.action: "skip"`, its current revision, and exactly one reason: `no_sources` when they have no applicable sources, `not_now` when they defer or say never mind, or `user_declined` for another refusal. Then advance to the next section without asking permission to continue. After recipes is skipped, end the current guided run precisely instead of looping back to snacks.
 7. Interpret the user's meaning conversationally. Do not implement or imitate keyword matching. If the user explicitly asks to stop, cancel, or quit the whole setup, end it without starting or skipping the next section; an `in_progress` section remains resumable.
 8. Never send `complete` to `hfj_update_onboarding`. A section becomes complete only when its canonical report exists, which the next `hfj_get_context` reports.

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

@@ -1,6 +1,6 @@
 ---
 name: track-recipe-history
-description: Track recipe discovery, Saved, Cooked, and Liked evidence, cooking dates, preparation changes, source scope, and recipe images.
+description: Start or continue Fullwell recipe onboarding and track recipe discovery, source scope and meaning, household preferences, Saved, Cooked, and Liked evidence, cooking dates, preparation changes, and recipe images.
 ---
 
 # Track Recipe History
@@ -8,7 +8,7 @@ description: Track recipe discovery, Saved, Cooked, and Liked evidence, cooking
 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. Call `hfj_get_context` and choose an editable household. If recipe onboarding is `not_started`, call `hfj_update_onboarding` with `transition.action: "start"` and `expected_revision: 0`; if it is `skipped`, resume it with the returned revision. Do not mutate a `complete` section.
-2. Call `hfj_get_profile` for `recipes`. Ask which websites, bookmark services, notes, communications, and other sources are authorized. For each site, clarify the whole discoverable site or exact subsection and what presence means.
+2. Call `hfj_get_profile` for `recipes`. 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. Append discovery, cooking, confirmation, or correction evidence with `hfj_append_evidence` before conclusions. Preserve canonical URL, audited page, displayed image URL, author/publisher, scope meaning, dates, limitations, and provenance.
 5. Use `hfj_search_items` and `hfj_get_item` to find current candidates. Decide recipe identity in reasoning. Keep Saved, Cooked, and Liked independent.