@fullwell/fullwell 1.1.12 → 1.1.13

package/.claude-plugin/plugin.json

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

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 1.1.13 - 2026-07-24
+
+- Add the required top-level object type to the local household-update tool schema so Claude can fetch every Fullwell local tool after connecting.
+- Replace Claude's system-like setup instruction with the conversational `Hi Fullwell.` greeting and route that exact greeting through name-first onboarding.
+
 ## 1.1.12 - 2026-07-24
 
 - Ask and remember the member name before account routing; derive the first local or cloud household name, synchronize the cloud display name on connection, support local/cloud renames and chat-driven runner/reminder shutdown, and suggest eligible invitations or collections with concrete examples.

package/README.md

@@ -2,7 +2,7 @@
 
 One shared skill package gives Codex and Claude a local-first food journal and an optional connection to the hosted Household Food Journal MCP service. A new user can collect grocery and recipe history without an account. The service performs authentication and every cloud-household mutation; the published package contains no credentials or bundled household data and includes no Git client or background synchronization engine.
 
-After installation, start with `@Fullwell hi` in Codex or `Set up Fullwell.` in Claude. A fresh greeting first asks `What should I call you?` and remembers the answer in a private revisioned local profile. Fullwell then asks whether the person already has an account. Existing account holders use hosted OAuth, copy the confirmed name to their cloud display name, and receive a first household named `Name's Household` (or `Names' Household`) only when they are not joining or resuming another household. Everyone else initializes that named private guest household under `~/.codex/fullwell/local/household.json`, begins one grocery-history pass for snacks, ingredients, condiments, and more, and advances to recipes without any Fullwell cloud call. The plugin-provided `fullwell-local` server exposes stable profile, household, runner-control, and collecting-only deletion tools, so narrow host permissions can survive package upgrades without allowing arbitrary Node commands. Local files use atomic revision-checked writes and exclude credentials, browser state, screenshots, and raw pages. After the journal is usable locally, the agent offers optional account creation and cloud backup for WhatsApp, sharing, or family access.
+After installation, start with `@Fullwell hi` in Codex or `Hi Fullwell.` in Claude. A fresh greeting first asks `What should I call you?` and remembers the answer in a private revisioned local profile. Fullwell then asks whether the person already has an account. Existing account holders use hosted OAuth, copy the confirmed name to their cloud display name, and receive a first household named `Name's Household` (or `Names' Household`) only when they are not joining or resuming another household. Everyone else initializes that named private guest household under `~/.codex/fullwell/local/household.json`, begins one grocery-history pass for snacks, ingredients, condiments, and more, and advances to recipes without any Fullwell cloud call. The plugin-provided `fullwell-local` server exposes stable profile, household, runner-control, and collecting-only deletion tools, so narrow host permissions can survive package upgrades without allowing arbitrary Node commands. Local files use atomic revision-checked writes and exclude credentials, browser state, screenshots, and raw pages. After the journal is usable locally, the agent offers optional account creation and cloud backup for WhatsApp, sharing, or family access.
 
 Authenticated onboarding still checkpoints unconfirmed work under `~/.codex/fullwell/drafts`, isolated by the stable Fullwell user and household IDs and bound to the current snapshot. One confirmed hosted commit persists it. Promoting a guest journal retains the local copy and records cloud linkage only after a successful hosted response.
 

package/install-metadata.json

@@ -1,6 +1,6 @@
 {
   "schema_version": 1,
-  "release": "1.1.12",
+  "release": "1.1.13",
   "mcp_url": "https://fullwell.souschefstudio.com/mcp",
   "install_page": "https://fullwell.souschefstudio.com/install",
   "platforms": {
@@ -22,7 +22,7 @@
       "marketplace": "fullwell",
       "plugin": "fullwell",
       "primary_action": "After installation, start Fullwell with the prompt below.",
-      "setup_prompt": "Set up Fullwell.",
+      "setup_prompt": "Hi Fullwell.",
       "setup_href": null,
       "fallback_commands": [
         "claude plugin marketplace add moorage/fullwell",

package/package.json

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

package/runtime/local-household-mcp.mjs

@@ -154,6 +154,7 @@ const updateOperationSchema = (operation, properties = {}) => ({
   additionalProperties: false,
 });
 const householdUpdateSchema = {
+  type: "object",
   oneOf: [
     {
       type: "object",

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

@@ -14,7 +14,7 @@ Use the plugin-provided `fullwell-local` tools for guest data and the bundled [l
 
 ## Remember the member before choosing authority
 
-Treat every greeting addressed to Fullwell, including a bare `@Fullwell hi`, as a request to start or resume this flow. Never call a Fullwell MCP tool merely to discover whether the person has an account.
+Treat every greeting addressed to Fullwell, including a bare `@Fullwell hi` or `Hi Fullwell.`, as a request to start or resume this flow. Never call a Fullwell MCP tool merely to discover whether the person has an account.
 
 1. Call `fullwell_local_profile_load` with no arguments before loading a household or contacting the cloud.
 2. If the profile is `missing` and the user has not already supplied a preferred name, ask exactly: "What should I call you?" Stop there. The account question, household setup, audits, and hosted calls all wait for this answer.