@rubytech/create-maxy-code 0.1.472 → 0.1.473

package/dist/__tests__/google-client-id-env.test.js

@@ -20,7 +20,7 @@ import assert from "node:assert/strict";
 import { buildClaudeSessionManagerUnitFile } from "../port-resolution.js";
 const ACCOUNT_ID = "12345678-9abc-def0-1234-56789abcdef0";
 const GOOGLE_ID = "1032860640027-p61l59fnog4mad5o7grginpaps9jnu8c.apps.googleusercontent.com";
-const PUBLIC_BASE = "https://public.sitedesk.online";
+const SECRET = "GOCSPX-test-value-not-real";
 const OUTLOOK_ID = "0fa68fe2-8bec-4007-a0c7-776636fbcf97";
 function build(opts) {
     return buildClaudeSessionManagerUnitFile({
@@ -36,20 +36,22 @@ function build(opts) {
         ...opts,
     });
 }
-test("both values present stamps both Environment lines", () => {
-    const unit = build({ googleClientId: GOOGLE_ID, googlePublicBase: PUBLIC_BASE });
+test("id and secret present stamps both Environment lines", () => {
+    const unit = build({ googleClientId: GOOGLE_ID, googleClientSecret: SECRET });
     assert.ok(unit.includes(`Environment=GOOGLE_CLIENT_ID=${GOOGLE_ID}`));
-    assert.ok(unit.includes(`Environment=GOOGLE_PUBLIC_BASE=${PUBLIC_BASE}`));
+    assert.ok(unit.includes(`Environment=GOOGLE_CLIENT_SECRET=${SECRET}`));
+    // The hosted callback is withdrawn (Task 1791); nothing consumes a public base.
+    assert.ok(!unit.includes("GOOGLE_PUBLIC_BASE"));
 });
-test("a client id with no public base stamps NEITHER line", () => {
+test("a client id with no secret stamps NEITHER line", () => {
     const unit = build({ googleClientId: GOOGLE_ID });
     assert.ok(!unit.includes("GOOGLE_CLIENT_ID"), "a half-stamp must not ship");
-    assert.ok(!unit.includes("GOOGLE_PUBLIC_BASE"));
+    assert.ok(!unit.includes("GOOGLE_CLIENT_SECRET"));
 });
-test("a public base with no client id stamps NEITHER line", () => {
-    const unit = build({ googlePublicBase: PUBLIC_BASE });
+test("a secret with no client id stamps NEITHER line", () => {
+    const unit = build({ googleClientSecret: SECRET });
     assert.ok(!unit.includes("GOOGLE_CLIENT_ID"));
-    assert.ok(!unit.includes("GOOGLE_PUBLIC_BASE"));
+    assert.ok(!unit.includes("GOOGLE_CLIENT_SECRET"));
 });
 test("a brand shipping no google app stamps neither line", () => {
     const unit = build({});
@@ -59,7 +61,7 @@ test("a brand shipping no google app stamps neither line", () => {
 test("google stamping leaves the outlook pair intact", () => {
     const unit = build({
         googleClientId: GOOGLE_ID,
-        googlePublicBase: PUBLIC_BASE,
+        googleClientSecret: SECRET,
         outlookClientId: OUTLOOK_ID,
     });
     assert.ok(unit.includes(`Environment=OUTLOOK_CLIENT_ID=${OUTLOOK_ID}`));

package/dist/index.js

@@ -51,26 +51,6 @@ catch (err) {
 }
 const INSTALL_DIR = resolve(process.env.HOME ?? "/root", BRAND.installDir);
 const PERSIST_DIR = resolve(process.env.HOME ?? "/root", BRAND.configDir);
-// Task 1761 — GOOGLE_PUBLIC_BASE is the https origin Google redirects back to
-// after consent. It is a property of THIS INSTALL's tunnel, not of the brand,
-// so it is read from the same cloudflared/tunnel.state the uninstaller reads.
-// Defined once here because BOTH env paths need it: the darwin .env mirror and
-// the Linux systemd unit. Absent tunnel → unset, and google-account-register
-// refuses with an actionable message rather than minting a consent URL whose
-// redirect_uri Google will reject on its byte-for-byte comparison.
-const googlePublicBase = (() => {
-    try {
-        const tunnelState = join(PERSIST_DIR, "cloudflared/tunnel.state");
-        if (!existsSync(tunnelState))
-            return "";
-        const parsed = JSON.parse(readFileSync(tunnelState, "utf-8"));
-        return parsed.domain ? `https://public.${parsed.domain}` : "";
-    }
-    catch {
-        // Unreadable tunnel state is not fatal to the install; the value stays unset.
-        return "";
-    }
-})();
 const LOG_DIR = join(PERSIST_DIR, "logs");
 const LOG_FILE = join(LOG_DIR, `install-${new Date().toISOString().replace(/[:.]/g, "-")}.log`);
 // every `claude plugin` shellout must read/write the per-brand
@@ -3741,13 +3721,10 @@ function installServiceDarwin() {
         }
         logFile(`  [installer] op=outlook-client-id brand=${BRAND.hostname} stamped=${BRAND.outlookClientId ? "true" : "false"}`);
         // Task 1761 — same upsert/strip discipline for the Google vendor app.
-        // GOOGLE_PUBLIC_BASE is the https origin the consent redirect returns to;
-        // it must match the authorized redirect URI on the vendor app byte-for-byte,
-        // so it is derived from the brand's public host, not guessed at call time.
-        if (BRAND.googleClientId) {
+        if (BRAND.googleClientId && BRAND.googleClientSecret) {
             for (const [key, value] of [
                 ["GOOGLE_CLIENT_ID", BRAND.googleClientId],
-                ["GOOGLE_PUBLIC_BASE", googlePublicBase],
+                ["GOOGLE_CLIENT_SECRET", BRAND.googleClientSecret],
             ]) {
                 const re = new RegExp(`^${key}=.*$`, "m");
                 if (re.test(envContent))
@@ -3757,11 +3734,11 @@ function installServiceDarwin() {
             }
         }
         else {
-            for (const key of ["GOOGLE_CLIENT_ID", "GOOGLE_PUBLIC_BASE"]) {
+            for (const key of ["GOOGLE_CLIENT_ID", "GOOGLE_CLIENT_SECRET"]) {
                 envContent = envContent.replace(new RegExp(`^${key}=.*\\n?`, "m"), "");
             }
         }
-        logFile(`  [installer] op=google-client-id brand=${BRAND.hostname} stamped=${BRAND.googleClientId ? "true" : "false"} publicBase=${googlePublicBase || "unset"}`);
+        logFile(`  [installer] op=google-client-id brand=${BRAND.hostname} stamped=${BRAND.googleClientId && BRAND.googleClientSecret ? "true" : "false"} clientId=${BRAND.googleClientId ? "set" : "unset"} secret=${BRAND.googleClientSecret ? "set" : "unset"}`);
         writeFileSync(envPath, envContent);
         logFile(`  .env: DISPLAY_MODE=${DISPLAY_MODE}, EMBED_MODEL=${EMBED_MODEL}, EMBED_DIMENSIONS=${EMBED_DIMS}, NEO4J_URI=bolt://localhost:${NEO4J_PORT}, PORT=${PORT}, MAXY_UI_INTERNAL_PORT=${PORT} (darwin-collapsed), CLAUDE_SESSION_MANAGER_PORT=${BRAND.claudeSessionManagerPort}, HOSTNAME=0.0.0.0, ACCOUNT_ID=${installAccountId.slice(0, 8)}…, CLAUDE_CONFIG_DIR=${persistDir}/.claude, CLAUDE_BIN=${canonicalClaude ?? "unresolved(PATH)"}, NODE_BIN=${nodeBin}, PATH=${darwinServiceEnvPath}`);
     }
@@ -4386,7 +4363,7 @@ function installService() {
         cdpPort: CDP_PORT_BRAND,
         outlookClientId: BRAND.outlookClientId,
         googleClientId: BRAND.googleClientId,
-        googlePublicBase: googlePublicBase || undefined,
+        googleClientSecret: BRAND.googleClientSecret,
     });
     writeFileSync(join(serviceDir, claudeSessionManagerUnitName), claudeSessionManagerUnit);
     logFile(`  ${claudeSessionManagerUnitName}: CLAUDE_SESSION_MANAGER_PORT=${CLAUDE_SESSION_MANAGER_PORT_BRAND} MAXY_UI_INTERNAL_PORT=${MAXY_UI_INTERNAL_PORT}`);
@@ -4397,7 +4374,7 @@ function installService() {
     // Task 1761 — the same standing signal for the Google vendor app. Both parts
     // are reported because a client id without a public base stamps NEITHER: a
     // consent URL built without the redirect origin is one Google rejects.
-    logFile(`  [installer] op=google-client-id brand=${BRAND.hostname} stamped=${BRAND.googleClientId && googlePublicBase ? "true" : "false"} clientId=${BRAND.googleClientId ? "set" : "unset"} publicBase=${googlePublicBase || "unset"}`);
+    logFile(`  [installer] op=google-client-id brand=${BRAND.hostname} stamped=${BRAND.googleClientId && BRAND.googleClientSecret ? "true" : "false"} clientId=${BRAND.googleClientId ? "set" : "unset"} secret=${BRAND.googleClientSecret ? "set" : "unset"}`);
     // Task 250 — write the brand-agnostic `claude-ptys.slice` unit. Every
     // brand's session manager drops its per-spawn scope units under this
     // slice. Writing it once per install is idempotent (the content is

package/dist/port-resolution.js

@@ -135,11 +135,11 @@ export function buildClaudeSessionManagerUnitFile(o) {
     const outlookEnv = o.outlookClientId
         ? `\nEnvironment=OUTLOOK_CLIENT_ID=${o.outlookClientId}\nEnvironment=OUTLOOK_TENANT_ID=common`
         : "";
-    // Task 1761 — same contract for the Google vendor app. The client id and the
-    // install's public base land together: a client id without a redirect origin
-    // produces a consent URL Google rejects, so a half-stamp is worse than none.
-    const googleEnv = o.googleClientId && o.googlePublicBase
-        ? `\nEnvironment=GOOGLE_CLIENT_ID=${o.googleClientId}\nEnvironment=GOOGLE_PUBLIC_BASE=${o.googlePublicBase}`
+    // Task 1791 — id and secret land together. A client id without its secret
+    // produces a consent URL the user can complete but an exchange that cannot,
+    // which fails later and less legibly than not offering the flow at all.
+    const googleEnv = o.googleClientId && o.googleClientSecret
+        ? `\nEnvironment=GOOGLE_CLIENT_ID=${o.googleClientId}\nEnvironment=GOOGLE_CLIENT_SECRET=${o.googleClientSecret}`
         : "";
     return `[Unit]
 Description=${o.productName} Claude Session Manager

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy-code",
-  "version": "0.1.472",
+  "version": "0.1.473",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy-code": "./dist/index.js"

package/payload/platform/config/brand.json

@@ -16,6 +16,7 @@
   "claudeSessionManagerPort": 19400,
   "outlookClientId": "",
   "googleClientId": "",
+  "googleClientSecret": "",
   "commercialMode": false,
   "vertical": "schema-knowledge-work",
   "shipsPremiumBundles": ["venture-studio", "writer-craft", "teaching", "management-consulting"],

package/payload/platform/docs/superpowers/plans/2026-07-18-ledger-write-path-fix.md

@@ -0,0 +1,109 @@
+# Ledger write path fix — implementation plan
+
+> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax.
+
+**Goal:** Every ledger write tool successfully creates its node, because relationships carry the element id `writeNodeWithEdges` actually requires.
+
+**Architecture:** Delete the ledger's invented `GraphRelationship` and the cast that forced it past the type checker; import the real type so the shape becomes a compile-time constraint. Resolve each relationship target to an element id before writing. Add a census counter so a dead write path can no longer read as a healthy empty ledger.
+
+**Spec:** [`.tasks/1788-...md`](../../../../.tasks/1788-ledger-write-tools-pass-an-invented-relationship-shape-so-every-write-is-rejected.md). No separate design doc; the task carries the decisions.
+
+## Global constraints
+
+- Node 22. Never `npm install` in this worktree; deps are symlinked from the parent.
+- Build and test from `maxy-code/platform`.
+- The four write tools must not be tested with a stubbed `write`. That stub is why the bug shipped.
+- Do not touch `lib/ledger-core`'s arithmetic (money, balance, ageing) — only `reconcile.ts` gains a counter.
+- Baseline before changes: 56 ledger tests, 508 memory-plugin tests.
+
+---
+
+### Task 1: Make the wrong shape a compile error
+
+**Files:** `plugins/ledger/mcp/src/lib/types.ts`, `plugins/ledger/mcp/src/index.ts`
+
+**Produces:** the real `GraphRelationship { type, direction, targetNodeId }` in scope for every tool.
+
+- [ ] **Step 1: Prove the current code is wrong at the type level.** In `types.ts`, delete the local `GraphRelationship` and re-export the real one:
+
+```ts
+export type { GraphRelationship } from "../../../../../lib/graph-write/dist/index.js";
+```
+
+- [ ] **Step 2: Delete the cast in `index.ts`.** Replace the `writeNodeWithEdges as unknown as (...)` wrapper with a direct reference. Run `tsc -p plugins/ledger/mcp/tsconfig.json` and record every error. Expect failures in `invoice-record.ts`, `payment-record.ts`, `cash-record.ts` on `targetLabel`/`targetProps`. **Those errors are the bug** — they are what the cast was hiding.
+
+- [ ] **Step 3: Fix the attribution while here.** `createdBy` becomes `{ agent: agentSlug, session: sessionId, tool, source: "ledger" }` with no `?? ""`, so `graph-write:254`'s `agent ?? source ?? "unknown"` chain can work.
+
+- [ ] **Step 4: Commit** once the remaining errors are only the three tool files.
+
+---
+
+### Task 2: Resolve targets to element ids
+
+**Files:** `plugins/ledger/mcp/src/lib/read.ts`, `tools/{invoice-record,payment-record,cash-record}.ts`, `index.ts`, `PLUGIN.md`
+
+**Consumes:** the real type from Task 1.
+
+- [ ] **Step 1: `readInvoice` returns the node's id.** Add `nodeId: string` to `InvoiceRead`; add `elementId(i) AS nodeId` to the Cypher and map it.
+
+- [ ] **Step 2: Write the failing tests first.** For each of the three tools, assert the relationship carries a `targetNodeId` equal to the id supplied or resolved, and that no relationship carries `targetLabel`:
+
+```ts
+it('targets the counterparty by element id', async () => {
+  const write = okWrite()
+  await invoiceRecord({ ...base, counterpartyNodeId: '4:abc:12', session: {} as never, write })
+  const rel = write.mock.calls[0]![0].relationships[0]
+  expect(rel.targetNodeId).toBe('4:abc:12')
+  expect(rel).not.toHaveProperty('targetLabel')
+})
+```
+
+- [ ] **Step 3: Implement.** `invoice-record` and `cash-record` take a required `counterpartyNodeId`. `payment-record` and `credit-record` use `invoice.nodeId` from the read. Each `zod` schema gains the field with a description telling the agent to look the organisation up first.
+
+- [ ] **Step 4: Reject a blank id** before writing, with `op=reject reason=missing-counterparty`, so the failure names the cause rather than surfacing as `unresolved-target`.
+
+- [ ] **Step 5: `tsc` clean, ledger tests green, commit.**
+
+---
+
+### Task 3: The test that would have caught it
+
+**Files:** `plugins/ledger/mcp/src/tools/__tests__/write-contract.test.ts` (new)
+
+One integration test per write tool that calls the **real** `writeNodeWithEdges` against a fake `Session` (`run` + `close`), asserting the issued Cypher carries the resolved target id and that no `unresolved-target` rejection occurs.
+
+- [ ] **Step 1: Write it against the current code and watch it fail** if Tasks 1 and 2 were somehow incomplete.
+- [ ] **Step 2: Confirm it passes.**
+- [ ] **Step 3: Prove it is load-bearing.** Temporarily reintroduce `targetLabel` in one tool; the build must fail. Revert.
+- [ ] **Step 4: Commit.**
+
+---
+
+### Task 4: Make a dead write path visible
+
+**Files:** `lib/ledger-core/src/reconcile.ts`, `plugins/ledger/mcp/src/lib/read.ts`, `tools/reconcile.ts`, `ui/app/lib/ledger-census.ts`, tests
+
+`[ledger-census]` currently prints `invoices=0 payments=0` identically whether the ledger is healthy-and-empty or wholly broken. That is why this bug ran all day unseen.
+
+- [ ] **Step 1: Failing test.** `reconcileLedger` alarms when `writeRejects24h > 0`.
+- [ ] **Step 2: Implement.** Add `writeRejects24h` to `LedgerCensusRows`, `LedgerCensusFinding`, the alarm condition, and `formatCensusLine`.
+- [ ] **Step 3: Source the count.** Both the census and the reconcile tool count `[graph-write] reject` lines in `<LOG_DIR>/mcp-ledger-*.log` with a timestamp inside the trailing 24 hours.
+- [ ] **Step 4: Tests green, commit.**
+
+---
+
+### Task 5: Docs
+
+**Files:** `plugins/ledger/PLUGIN.md`, `plugins/docs/references/ledger.md`
+
+State that the counterparty must be looked up first and passed by id, that the ledger never creates organisations, and what `writeRejects24h` means. Keep the shipped reference free of em-dashes.
+
+- [ ] Commit.
+
+---
+
+## Self-review
+
+**Spec coverage.** Type import and cast removal: Task 1. Attribution: Task 1 step 3. Element-id resolution for all four write tools: Task 2. The banned-stub integration test: Task 3. Census counter: Task 4. Docs: Task 5. Out-of-scope items (duplicate-org matching, `:InvoiceLine`, read tools, ledger-core arithmetic) are untouched.
+
+**Risk.** Task 2 changes the tool signatures, so any agent prompt or skill that calls `ledger-invoice-record` with a bare counterparty name breaks. Nothing calls these tools yet except live agent turns, and they have never succeeded, so there is no working caller to regress.

package/payload/platform/lib/ledger-core/dist/reconcile.d.ts

@@ -31,6 +31,12 @@ export interface LedgerCensusRows {
     storedBalanceProps: number;
     paymentKeys: readonly PaymentKey[];
     declaredNotLive: readonly string[];
+    /** Count of `[graph-write] reject` lines from the ledger's MCP logs in the
+     *  trailing 24 hours. Without it the census cannot tell a healthy empty
+     *  ledger from one whose write path is wholly dead: both print
+     *  `invoices=0 payments=0`. Task 1788, after exactly that went unseen for a
+     *  day. */
+    writeRejects24h: number;
 }
 export interface LedgerCensusFinding {
     invoices: number;
@@ -39,6 +45,7 @@ export interface LedgerCensusFinding {
     storedBalanceProps: number;
     suspectDuplicates: number;
     declaredNotLive: readonly string[];
+    writeRejects24h: number;
     alarm: boolean;
 }
 export declare function reconcileLedger(rows: LedgerCensusRows, _now: number): LedgerCensusFinding;

package/payload/platform/lib/ledger-core/dist/reconcile.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"reconcile.d.ts","sourceRoot":"","sources":["../src/reconcile.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAEH;;;;mEAImE;AACnE,eAAO,MAAM,kBAAkB,EAAE,SAAS,MAAM,EAO/C,CAAA;AAED,MAAM,WAAW,UAAU;IACzB,SAAS,EAAE,MAAM,CAAA;IACjB,SAAS,EAAE,MAAM,CAAA;IACjB,MAAM,EAAE,MAAM,CAAA;IACd,IAAI,EAAE,MAAM,CAAA;CACb;AAED,MAAM,WAAW,gBAAgB;IAC/B,QAAQ,EAAE,MAAM,CAAA;IAChB,QAAQ,EAAE,MAAM,CAAA;IAChB,cAAc,EAAE,MAAM,CAAA;IACtB,kBAAkB,EAAE,MAAM,CAAA;IAC1B,WAAW,EAAE,SAAS,UAAU,EAAE,CAAA;IAClC,eAAe,EAAE,SAAS,MAAM,EAAE,CAAA;CACnC;AAED,MAAM,WAAW,mBAAmB;IAClC,QAAQ,EAAE,MAAM,CAAA;IAChB,QAAQ,EAAE,MAAM,CAAA;IAChB,cAAc,EAAE,MAAM,CAAA;IACtB,kBAAkB,EAAE,MAAM,CAAA;IAC1B,iBAAiB,EAAE,MAAM,CAAA;IACzB,eAAe,EAAE,SAAS,MAAM,EAAE,CAAA;IAClC,KAAK,EAAE,OAAO,CAAA;CACf;AAwBD,wBAAgB,eAAe,CAAC,IAAI,EAAE,gBAAgB,EAAE,IAAI,EAAE,MAAM,GAAG,mBAAmB,CAiBzF;AAED;;;;GAIG;AACH,wBAAgB,gBAAgB,CAAC,CAAC,EAAE,mBAAmB,GAAG,MAAM,CAO/D"}
+{"version":3,"file":"reconcile.d.ts","sourceRoot":"","sources":["../src/reconcile.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAEH;;;;mEAImE;AACnE,eAAO,MAAM,kBAAkB,EAAE,SAAS,MAAM,EAO/C,CAAA;AAED,MAAM,WAAW,UAAU;IACzB,SAAS,EAAE,MAAM,CAAA;IACjB,SAAS,EAAE,MAAM,CAAA;IACjB,MAAM,EAAE,MAAM,CAAA;IACd,IAAI,EAAE,MAAM,CAAA;CACb;AAED,MAAM,WAAW,gBAAgB;IAC/B,QAAQ,EAAE,MAAM,CAAA;IAChB,QAAQ,EAAE,MAAM,CAAA;IAChB,cAAc,EAAE,MAAM,CAAA;IACtB,kBAAkB,EAAE,MAAM,CAAA;IAC1B,WAAW,EAAE,SAAS,UAAU,EAAE,CAAA;IAClC,eAAe,EAAE,SAAS,MAAM,EAAE,CAAA;IAClC;;;;eAIW;IACX,eAAe,EAAE,MAAM,CAAA;CACxB;AAED,MAAM,WAAW,mBAAmB;IAClC,QAAQ,EAAE,MAAM,CAAA;IAChB,QAAQ,EAAE,MAAM,CAAA;IAChB,cAAc,EAAE,MAAM,CAAA;IACtB,kBAAkB,EAAE,MAAM,CAAA;IAC1B,iBAAiB,EAAE,MAAM,CAAA;IACzB,eAAe,EAAE,SAAS,MAAM,EAAE,CAAA;IAClC,eAAe,EAAE,MAAM,CAAA;IACvB,KAAK,EAAE,OAAO,CAAA;CACf;AAwBD,wBAAgB,eAAe,CAAC,IAAI,EAAE,gBAAgB,EAAE,IAAI,EAAE,MAAM,GAAG,mBAAmB,CAmBzF;AAED;;;;GAIG;AACH,wBAAgB,gBAAgB,CAAC,CAAC,EAAE,mBAAmB,GAAG,MAAM,CAQ/D"}

package/payload/platform/lib/ledger-core/dist/reconcile.js

@@ -52,7 +52,8 @@ export function reconcileLedger(rows, _now) {
     const alarm = rows.orphanPayments > 0 ||
         rows.storedBalanceProps > 0 ||
         suspectDuplicates > 0 ||
-        rows.declaredNotLive.length > 0;
+        rows.declaredNotLive.length > 0 ||
+        rows.writeRejects24h > 0;
     return {
         invoices: rows.invoices,
         payments: rows.payments,
@@ -60,6 +61,7 @@ export function reconcileLedger(rows, _now) {
         storedBalanceProps: rows.storedBalanceProps,
         suspectDuplicates,
         declaredNotLive: rows.declaredNotLive,
+        writeRejects24h: rows.writeRejects24h,
         alarm,
     };
 }
@@ -72,6 +74,7 @@ export function formatCensusLine(f) {
     return (`[ledger-census] invoices=${f.invoices} payments=${f.payments} ` +
         `orphanPayments=${f.orphanPayments} storedBalanceProps=${f.storedBalanceProps} ` +
         `suspectDuplicates=${f.suspectDuplicates} ` +
-        `declaredNotLive=${f.declaredNotLive.length === 0 ? "none" : f.declaredNotLive.join(",")}`);
+        `declaredNotLive=${f.declaredNotLive.length === 0 ? "none" : f.declaredNotLive.join(",")} ` +
+        `writeRejects24h=${f.writeRejects24h}`);
 }
 //# sourceMappingURL=reconcile.js.map

package/payload/platform/lib/ledger-core/dist/reconcile.js.map

@@ -1 +1 @@
-{"version":3,"file":"reconcile.js","sourceRoot":"","sources":["../src/reconcile.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAEH;;;;mEAImE;AACnE,MAAM,CAAC,MAAM,kBAAkB,GAAsB;IACnD,qCAAqC;IACrC,mCAAmC;IACnC,oBAAoB;IACpB,sBAAsB;IACtB,yBAAyB;IACzB,gBAAgB;CACjB,CAAA;AA4BD;;;;;;;;GAQG;AACH,SAAS,sBAAsB,CAAC,IAA2B;IACzD,MAAM,MAAM,GAAG,IAAI,GAAG,EAAuB,CAAA;IAC7C,KAAK,MAAM,CAAC,IAAI,IAAI,EAAE,CAAC;QACrB,MAAM,SAAS,GAAG,GAAG,CAAC,CAAC,SAAS,IAAI,CAAC,CAAC,MAAM,IAAI,CAAC,CAAC,IAAI,EAAE,CAAA;QACxD,MAAM,GAAG,GAAG,MAAM,CAAC,GAAG,CAAC,SAAS,CAAC,IAAI,IAAI,GAAG,EAAU,CAAA;QACtD,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC,SAAS,CAAC,CAAA;QACpB,MAAM,CAAC,GAAG,CAAC,SAAS,EAAE,GAAG,CAAC,CAAA;IAC5B,CAAC;IACD,IAAI,KAAK,GAAG,CAAC,CAAA;IACb,KAAK,MAAM,GAAG,IAAI,MAAM,CAAC,MAAM,EAAE;QAAE,KAAK,IAAI,IAAI,CAAC,GAAG,CAAC,CAAC,EAAE,GAAG,CAAC,IAAI,GAAG,CAAC,CAAC,CAAA;IACrE,OAAO,KAAK,CAAA;AACd,CAAC;AAED,MAAM,UAAU,eAAe,CAAC,IAAsB,EAAE,IAAY;IAClE,MAAM,iBAAiB,GAAG,sBAAsB,CAAC,IAAI,CAAC,WAAW,CAAC,CAAA;IAClE,MAAM,KAAK,GACT,IAAI,CAAC,cAAc,GAAG,CAAC;QACvB,IAAI,CAAC,kBAAkB,GAAG,CAAC;QAC3B,iBAAiB,GAAG,CAAC;QACrB,IAAI,CAAC,eAAe,CAAC,MAAM,GAAG,CAAC,CAAA;IAEjC,OAAO;QACL,QAAQ,EAAE,IAAI,CAAC,QAAQ;QACvB,QAAQ,EAAE,IAAI,CAAC,QAAQ;QACvB,cAAc,EAAE,IAAI,CAAC,cAAc;QACnC,kBAAkB,EAAE,IAAI,CAAC,kBAAkB;QAC3C,iBAAiB;QACjB,eAAe,EAAE,IAAI,CAAC,eAAe;QACrC,KAAK;KACN,CAAA;AACH,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,gBAAgB,CAAC,CAAsB;IACrD,OAAO,CACL,4BAA4B,CAAC,CAAC,QAAQ,aAAa,CAAC,CAAC,QAAQ,GAAG;QAChE,kBAAkB,CAAC,CAAC,cAAc,uBAAuB,CAAC,CAAC,kBAAkB,GAAG;QAChF,qBAAqB,CAAC,CAAC,iBAAiB,GAAG;QAC3C,mBAAmB,CAAC,CAAC,eAAe,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,eAAe,CAAC,IAAI,CAAC,GAAG,CAAC,EAAE,CAC3F,CAAA;AACH,CAAC"}
+{"version":3,"file":"reconcile.js","sourceRoot":"","sources":["../src/reconcile.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAEH;;;;mEAImE;AACnE,MAAM,CAAC,MAAM,kBAAkB,GAAsB;IACnD,qCAAqC;IACrC,mCAAmC;IACnC,oBAAoB;IACpB,sBAAsB;IACtB,yBAAyB;IACzB,gBAAgB;CACjB,CAAA;AAmCD;;;;;;;;GAQG;AACH,SAAS,sBAAsB,CAAC,IAA2B;IACzD,MAAM,MAAM,GAAG,IAAI,GAAG,EAAuB,CAAA;IAC7C,KAAK,MAAM,CAAC,IAAI,IAAI,EAAE,CAAC;QACrB,MAAM,SAAS,GAAG,GAAG,CAAC,CAAC,SAAS,IAAI,CAAC,CAAC,MAAM,IAAI,CAAC,CAAC,IAAI,EAAE,CAAA;QACxD,MAAM,GAAG,GAAG,MAAM,CAAC,GAAG,CAAC,SAAS,CAAC,IAAI,IAAI,GAAG,EAAU,CAAA;QACtD,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC,SAAS,CAAC,CAAA;QACpB,MAAM,CAAC,GAAG,CAAC,SAAS,EAAE,GAAG,CAAC,CAAA;IAC5B,CAAC;IACD,IAAI,KAAK,GAAG,CAAC,CAAA;IACb,KAAK,MAAM,GAAG,IAAI,MAAM,CAAC,MAAM,EAAE;QAAE,KAAK,IAAI,IAAI,CAAC,GAAG,CAAC,CAAC,EAAE,GAAG,CAAC,IAAI,GAAG,CAAC,CAAC,CAAA;IACrE,OAAO,KAAK,CAAA;AACd,CAAC;AAED,MAAM,UAAU,eAAe,CAAC,IAAsB,EAAE,IAAY;IAClE,MAAM,iBAAiB,GAAG,sBAAsB,CAAC,IAAI,CAAC,WAAW,CAAC,CAAA;IAClE,MAAM,KAAK,GACT,IAAI,CAAC,cAAc,GAAG,CAAC;QACvB,IAAI,CAAC,kBAAkB,GAAG,CAAC;QAC3B,iBAAiB,GAAG,CAAC;QACrB,IAAI,CAAC,eAAe,CAAC,MAAM,GAAG,CAAC;QAC/B,IAAI,CAAC,eAAe,GAAG,CAAC,CAAA;IAE1B,OAAO;QACL,QAAQ,EAAE,IAAI,CAAC,QAAQ;QACvB,QAAQ,EAAE,IAAI,CAAC,QAAQ;QACvB,cAAc,EAAE,IAAI,CAAC,cAAc;QACnC,kBAAkB,EAAE,IAAI,CAAC,kBAAkB;QAC3C,iBAAiB;QACjB,eAAe,EAAE,IAAI,CAAC,eAAe;QACrC,eAAe,EAAE,IAAI,CAAC,eAAe;QACrC,KAAK;KACN,CAAA;AACH,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,gBAAgB,CAAC,CAAsB;IACrD,OAAO,CACL,4BAA4B,CAAC,CAAC,QAAQ,aAAa,CAAC,CAAC,QAAQ,GAAG;QAChE,kBAAkB,CAAC,CAAC,cAAc,uBAAuB,CAAC,CAAC,kBAAkB,GAAG;QAChF,qBAAqB,CAAC,CAAC,iBAAiB,GAAG;QAC3C,mBAAmB,CAAC,CAAC,eAAe,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,eAAe,CAAC,IAAI,CAAC,GAAG,CAAC,GAAG;QAC3F,mBAAmB,CAAC,CAAC,eAAe,EAAE,CACvC,CAAA;AACH,CAAC"}

package/payload/platform/lib/ledger-core/src/__tests__/reconcile.test.ts

@@ -8,6 +8,7 @@ const clean = {
   storedBalanceProps: 0,
   paymentKeys: [],
   declaredNotLive: [],
+  writeRejects24h: 0,
 }
 const NOW = Date.parse('2026-07-18T00:00:00Z')
 
@@ -84,4 +85,23 @@ describe('reconcileLedger', () => {
     expect(LEDGER_INDEX_NAMES).toHaveLength(6)
     expect(LEDGER_INDEX_NAMES).toContain('cash_entry_account_entryid_unique')
   })
+
+  it('alarms when the write path is rejecting', () => {
+    // The case this counter exists for: on 2026-07-18 every ledger write was
+    // rejected all day while the census printed invoices=0 payments=0, which
+    // is byte-identical to a healthy ledger nobody has used yet.
+    const f = reconcileLedger({ ...clean, writeRejects24h: 4 }, NOW)
+    expect(f.alarm).toBe(true)
+    expect(formatCensusLine(f)).toContain('writeRejects24h=4')
+  })
+
+  it('a healthy empty ledger is distinguishable from a broken one', () => {
+    const empty = { ...clean, invoices: 0, payments: 0 }
+    const broken = { ...empty, writeRejects24h: 4 }
+    expect(formatCensusLine(reconcileLedger(empty, NOW))).not.toEqual(
+      formatCensusLine(reconcileLedger(broken, NOW)),
+    )
+    expect(reconcileLedger(empty, NOW).alarm).toBe(false)
+    expect(reconcileLedger(broken, NOW).alarm).toBe(true)
+  })
 })

package/payload/platform/lib/ledger-core/src/reconcile.ts

@@ -41,6 +41,12 @@ export interface LedgerCensusRows {
   storedBalanceProps: number
   paymentKeys: readonly PaymentKey[]
   declaredNotLive: readonly string[]
+  /** Count of `[graph-write] reject` lines from the ledger's MCP logs in the
+   *  trailing 24 hours. Without it the census cannot tell a healthy empty
+   *  ledger from one whose write path is wholly dead: both print
+   *  `invoices=0 payments=0`. Task 1788, after exactly that went unseen for a
+   *  day. */
+  writeRejects24h: number
 }
 
 export interface LedgerCensusFinding {
@@ -50,6 +56,7 @@ export interface LedgerCensusFinding {
   storedBalanceProps: number
   suspectDuplicates: number
   declaredNotLive: readonly string[]
+  writeRejects24h: number
   alarm: boolean
 }
 
@@ -81,7 +88,8 @@ export function reconcileLedger(rows: LedgerCensusRows, _now: number): LedgerCen
     rows.orphanPayments > 0 ||
     rows.storedBalanceProps > 0 ||
     suspectDuplicates > 0 ||
-    rows.declaredNotLive.length > 0
+    rows.declaredNotLive.length > 0 ||
+    rows.writeRejects24h > 0
 
   return {
     invoices: rows.invoices,
@@ -90,6 +98,7 @@ export function reconcileLedger(rows: LedgerCensusRows, _now: number): LedgerCen
     storedBalanceProps: rows.storedBalanceProps,
     suspectDuplicates,
     declaredNotLive: rows.declaredNotLive,
+    writeRejects24h: rows.writeRejects24h,
     alarm,
   }
 }
@@ -104,6 +113,7 @@ export function formatCensusLine(f: LedgerCensusFinding): string {
     `[ledger-census] invoices=${f.invoices} payments=${f.payments} ` +
     `orphanPayments=${f.orphanPayments} storedBalanceProps=${f.storedBalanceProps} ` +
     `suspectDuplicates=${f.suspectDuplicates} ` +
-    `declaredNotLive=${f.declaredNotLive.length === 0 ? "none" : f.declaredNotLive.join(",")}`
+    `declaredNotLive=${f.declaredNotLive.length === 0 ? "none" : f.declaredNotLive.join(",")} ` +
+    `writeRejects24h=${f.writeRejects24h}`
   )
 }

package/payload/platform/plugins/admin/skills/platform-architecture/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: platform-architecture
 description: Use when grounding any documented-surface claim about what Maxy ships — plugins, skills, specialists, install/deploy flows, internals. This is the install catalogue, not evidence of what is enabled on the current account. For install state on this account, call `capabilities-here`; for documented surface, cite the `Source:` URL inline.
-content-hash: sha256:46e07a18921b711849e53f63b8c29b72f3324f91bc682eb5be585ccd64c98971
+content-hash: sha256:c15214d349505b6337668b0362b849c9c5301fd25304800cf7384888a6a21435
 brand: maxy-code
 product-name: Maxy
 ---
@@ -636,6 +636,12 @@ If you need statutory accounts, this is not that. It is the answer to "who owes
 
 **Ask for a statement.** Everything owed to you and everything you owe, sorted into 0-30, 31-60, 61-90 and 90+ days overdue, plus net cash.
 
+## You look the customer up first
+
+When you record an invoice or a cash movement, the agent finds the company or person in your records first, then attaches the money to that exact record. It will not create a new company for you, and the name that appears on the invoice is taken from the record it attached to, so the two can never disagree.
+
+That is on purpose. Deciding whether "Beagle Direct Ltd" is the same firm as an existing "Beagle Direct" is a judgement about your records, not a bookkeeping step, and getting it wrong quietly splits one customer's payment history across two entries.
+
 ## Three behaviours worth knowing about
 
 **What is outstanding is never stored.** It is worked out from the payments each time you ask. This means the figure cannot fall out of step with the payments behind it. If it were stored, a payment recorded by any route that forgot to update it would leave the invoice quietly reporting a wrong number, and nothing would fail.
@@ -648,7 +654,9 @@ If you need statutory accounts, this is not that. It is the answer to "who owes
 
 Some ways this can go wrong announce themselves. Others do not: a payment that ends up attached to no invoice, a stale balance field reappearing, or the same payment recorded twice under two different ids. None of those produce an error at the time, because nothing goes wrong at the moment they happen.
 
-So there is a check that runs by itself every fifteen minutes and writes one line to the log beginning `[ledger-census]`. When it is healthy the counters are all zero. When something is wrong the line ends with `alarm=true` and says which of the four it found.
+So there is a check that runs by itself every fifteen minutes and writes one line to the log beginning `[ledger-census]`. When it is healthy the counters are all zero. When something is wrong the line ends with `alarm=true` and says which of them it found.
+
+One of those counters is the number of writes that were refused in the last day. It is there because of a real failure: for a whole day every attempt to record money was refused, and the check still read as healthy, because a ledger nobody has used and a ledger that cannot be written to both show nothing.
 
 You can also ask for that check on demand at any time, and it reports the same thing in plain words.
 
@@ -2218,9 +2226,16 @@ force Google's annual third-party security assessment. Calendar is only a
 ## Connecting an account
 
 `google-account-register` returns a consent URL. Relay it to the user: they open
-it on any device, sign in, and approve. Google redirects to this install's
-public host at `/api/google/oauth/callback`, which exchanges the code and stores
-encrypted tokens. `google-account-register-poll` then reports the outcome.
+it on any device, sign in, and approve.
+
+Their browser then lands on a page that **fails to load**. That is expected, not
+a fault — the vendor app is a Desktop client, so Google redirects to a loopback
+address on the user's own device where nothing is listening. The address bar
+carries the code. Ask them to copy it and pass it to
+`google-account-register-submit`, which completes the connection.
+
+If they paste the whole `code=...` fragment, or a value containing `%2F`, the
+tool handles it. `google-account-register-poll` reports the outcome at any point.
 
 The register tool does not block and does not wait. A second register while one
 is already live is refused rather than overwriting it; that refusal names how
@@ -4891,6 +4906,10 @@ To deliberately disconnect the wrong account, use the header menu's **Disconnect
 3. `grep '\[auth-health\]' ~/.${brand}/logs/server.log | tail -n 5` — the heartbeat fires every five minutes. `status=dead expiresIn=...` means the refresh token is gone; only a re-login fixes it. `status=ok` heartbeats with no spawns in between mean the credentials file is healthy and the failure lives elsewhere.
 4. The spawn-failure surface now carries `reason=auth-refresh-failed` (with `authStatus` in the JSON body) instead of generic `pid-file-timeout` whenever the credentials file is in `dead` or `expired` state at the moment of failure — visible in `grep '\[spawn-failed\]'` on server.log.
 
+**A WhatsApp message you can see on your phone never appears in the app.** First check whether it was ever stored, rather than assuming it routed elsewhere: ask Maxy for the most recent ingest reconcile, or `grep '\[wa-ingest-audit\]' ~/.${brand}/logs/server.log | tail -1`. A healthy line reads `op=reconcile … unpersisted=0 inFlight=0 guard=installed`. If `unpersisted` is above zero, the `ids=` field names the exact message ids that arrived at the wire and were never written to the store — those messages are genuinely lost to the platform, not hidden in another workspace or sub-account, and they cannot be re-fetched because WhatsApp only delivers an acked message once. Forward the message from your phone to get it back in; it re-enters as a new message through the normal path.
+
+The audit runs every 15 minutes and holds a stanza for 10 minutes before judging it, so a message can take up to 25 minutes to be reported. The wait is deliberate: a large batch of photos arriving at once can take several minutes to finish storing, and a false "a message was lost" alarm would make the real one easy to ignore. Three classes are resolved rather than reported, each counted separately: `skippedStatus` (status broadcasts, never stored), `skippedReaction` (reactions, stored under the message they react to rather than under their own id — a consequence being that a lost *reaction* is not detectable), and `declined` (messages carrying neither text nor a file, such as a shared contact card, a poll, or a delete-for-everyone, which are dropped by design). `oldestUnpersistedMin` tells you whether a reported loss is new or one you have already seen, since the same id is re-reported every 15 minutes for a day. `guard=absent` or `inFlight` stuck above zero on an idle install are both faults worth surfacing to support: the first means the media-download crash guard failed to install at boot, the second means its counter leaked. `contained` counts crashes the guard prevented — a number that climbs while media traffic stays flat is also worth reporting.
+
 ---
 
 ## Memory Not Working

package/payload/platform/plugins/docs/references/google-guide.md

@@ -12,9 +12,16 @@ force Google's annual third-party security assessment. Calendar is only a
 ## Connecting an account
 
 `google-account-register` returns a consent URL. Relay it to the user: they open
-it on any device, sign in, and approve. Google redirects to this install's
-public host at `/api/google/oauth/callback`, which exchanges the code and stores
-encrypted tokens. `google-account-register-poll` then reports the outcome.
+it on any device, sign in, and approve.
+
+Their browser then lands on a page that **fails to load**. That is expected, not
+a fault — the vendor app is a Desktop client, so Google redirects to a loopback
+address on the user's own device where nothing is listening. The address bar
+carries the code. Ask them to copy it and pass it to
+`google-account-register-submit`, which completes the connection.
+
+If they paste the whole `code=...` fragment, or a value containing `%2F`, the
+tool handles it. `google-account-register-poll` reports the outcome at any point.
 
 The register tool does not block and does not wait. A second register while one
 is already live is refused rather than overwriting it; that refusal names how

package/payload/platform/plugins/docs/references/ledger.md

@@ -24,6 +24,12 @@ If you need statutory accounts, this is not that. It is the answer to "who owes
 
 **Ask for a statement.** Everything owed to you and everything you owe, sorted into 0-30, 31-60, 61-90 and 90+ days overdue, plus net cash.
 
+## You look the customer up first
+
+When you record an invoice or a cash movement, the agent finds the company or person in your records first, then attaches the money to that exact record. It will not create a new company for you, and the name that appears on the invoice is taken from the record it attached to, so the two can never disagree.
+
+That is on purpose. Deciding whether "Beagle Direct Ltd" is the same firm as an existing "Beagle Direct" is a judgement about your records, not a bookkeeping step, and getting it wrong quietly splits one customer's payment history across two entries.
+
 ## Three behaviours worth knowing about
 
 **What is outstanding is never stored.** It is worked out from the payments each time you ask. This means the figure cannot fall out of step with the payments behind it. If it were stored, a payment recorded by any route that forgot to update it would leave the invoice quietly reporting a wrong number, and nothing would fail.
@@ -36,7 +42,9 @@ If you need statutory accounts, this is not that. It is the answer to "who owes
 
 Some ways this can go wrong announce themselves. Others do not: a payment that ends up attached to no invoice, a stale balance field reappearing, or the same payment recorded twice under two different ids. None of those produce an error at the time, because nothing goes wrong at the moment they happen.
 
-So there is a check that runs by itself every fifteen minutes and writes one line to the log beginning `[ledger-census]`. When it is healthy the counters are all zero. When something is wrong the line ends with `alarm=true` and says which of the four it found.
+So there is a check that runs by itself every fifteen minutes and writes one line to the log beginning `[ledger-census]`. When it is healthy the counters are all zero. When something is wrong the line ends with `alarm=true` and says which of them it found.
+
+One of those counters is the number of writes that were refused in the last day. It is there because of a real failure: for a whole day every attempt to record money was refused, and the check still read as healthy, because a ledger nobody has used and a ledger that cannot be written to both show nothing.
 
 You can also ask for that check on demand at any time, and it reports the same thing in plain words.
 

package/payload/platform/plugins/docs/references/troubleshooting.md

@@ -147,6 +147,10 @@ To deliberately disconnect the wrong account, use the header menu's **Disconnect
 3. `grep '\[auth-health\]' ~/.${brand}/logs/server.log | tail -n 5` — the heartbeat fires every five minutes. `status=dead expiresIn=...` means the refresh token is gone; only a re-login fixes it. `status=ok` heartbeats with no spawns in between mean the credentials file is healthy and the failure lives elsewhere.
 4. The spawn-failure surface now carries `reason=auth-refresh-failed` (with `authStatus` in the JSON body) instead of generic `pid-file-timeout` whenever the credentials file is in `dead` or `expired` state at the moment of failure — visible in `grep '\[spawn-failed\]'` on server.log.
 
+**A WhatsApp message you can see on your phone never appears in the app.** First check whether it was ever stored, rather than assuming it routed elsewhere: ask {{productName}} for the most recent ingest reconcile, or `grep '\[wa-ingest-audit\]' ~/.${brand}/logs/server.log | tail -1`. A healthy line reads `op=reconcile … unpersisted=0 inFlight=0 guard=installed`. If `unpersisted` is above zero, the `ids=` field names the exact message ids that arrived at the wire and were never written to the store — those messages are genuinely lost to the platform, not hidden in another workspace or sub-account, and they cannot be re-fetched because WhatsApp only delivers an acked message once. Forward the message from your phone to get it back in; it re-enters as a new message through the normal path.
+
+The audit runs every 15 minutes and holds a stanza for 10 minutes before judging it, so a message can take up to 25 minutes to be reported. The wait is deliberate: a large batch of photos arriving at once can take several minutes to finish storing, and a false "a message was lost" alarm would make the real one easy to ignore. Three classes are resolved rather than reported, each counted separately: `skippedStatus` (status broadcasts, never stored), `skippedReaction` (reactions, stored under the message they react to rather than under their own id — a consequence being that a lost *reaction* is not detectable), and `declined` (messages carrying neither text nor a file, such as a shared contact card, a poll, or a delete-for-everyone, which are dropped by design). `oldestUnpersistedMin` tells you whether a reported loss is new or one you have already seen, since the same id is re-reported every 15 minutes for a day. `guard=absent` or `inFlight` stuck above zero on an idle install are both faults worth surfacing to support: the first means the media-download crash guard failed to install at boot, the second means its counter leaked. `contained` counts crashes the guard prevented — a number that climbs while media traffic stays flat is also worth reporting.
+
 ---
 
 ## Memory Not Working

package/payload/platform/plugins/google/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "google",
-  "description": "Live Google Calendar for one account via the Google Calendar API v3 — read plus control. Per-account OAuth authorization-code + PKCE; the consent URL is minted by the plugin and the code is exchanged by platform/ui, which holds the house-only client secret. One account can connect several Google accounts; every operational tool takes an optional account selector (the email address) and refuses ambiguously when two or more are connected and none is named. There is deliberately no Gmail surface — mail runs on the `email` plugin's IMAP/SMTP path, and Gmail's restricted scopes would force Google's annual third-party security assessment, whereas Calendar is only a sensitive scope. Tools — google-account-register / google-account-register-poll: connect a Google Calendar (returns a consent URL, then reports the outcome from local state); google-calendar-list: events in the next rangeDays days, recurring series expanded; google-calendar-event: one event by id; google-calendar-create / google-calendar-update / google-calendar-cancel: control events, attendees notified, update changes only the fields named; google-calendar-respond: accept, decline or tentatively accept an invitation, leaving other attendees' responses untouched; google-calendar-freebusy: busy blocks for this or named calendars; google-account-info: auth state for one connected Google account; google-account-list: every connected Google account with its own status.",
+  "description": "Live Google Calendar for one account via the Google Calendar API v3 — read plus control. Per-account OAuth authorization-code + PKCE; the consent URL is minted by the plugin and the code is exchanged by platform/ui, which holds the house-only client secret. One account can connect several Google accounts; every operational tool takes an optional account selector (the email address) and refuses ambiguously when two or more are connected and none is named. There is deliberately no Gmail surface — mail runs on the `email` plugin's IMAP/SMTP path, and Gmail's restricted scopes would force Google's annual third-party security assessment, whereas Calendar is only a sensitive scope. Tools — google-account-register / google-account-register-submit / google-account-register-poll: connect a Google Calendar (returns a consent URL; the user approves, lands on a page that fails to load by design, and pastes the code back to submit); google-calendar-list: events in the next rangeDays days, recurring series expanded; google-calendar-event: one event by id; google-calendar-create / google-calendar-update / google-calendar-cancel: control events, attendees notified, update changes only the fields named; google-calendar-respond: accept, decline or tentatively accept an invitation, leaving other attendees' responses untouched; google-calendar-freebusy: busy blocks for this or named calendars; google-account-info: auth state for one connected Google account; google-account-list: every connected Google account with its own status.",
   "version": "0.1.0",
   "author": {
     "name": "Rubytech LLC"

package/payload/platform/plugins/google/PLUGIN.md

@@ -1,6 +1,6 @@
 ---
 name: google
-description: Live Google Calendar for one account via the Google Calendar API v3 — read plus control. Per-account OAuth authorization-code + PKCE; the consent URL is minted by the plugin and the code is exchanged by platform/ui, which holds the house-only client secret. One account can connect several Google accounts; every operational tool takes an optional account selector (the email address) and refuses ambiguously when two or more are connected and none is named. There is deliberately no Gmail surface — mail runs on the `email` plugin's IMAP/SMTP path, and Gmail's restricted scopes would force Google's annual third-party security assessment, whereas Calendar is only a sensitive scope. Tools — google-account-register / google-account-register-poll: connect a Google Calendar (returns a consent URL, then reports the outcome from local state); google-calendar-list: events in the next rangeDays days, recurring series expanded; google-calendar-event: one event by id; google-calendar-create / google-calendar-update / google-calendar-cancel: control events, attendees notified, update changes only the fields named; google-calendar-respond: accept, decline or tentatively accept an invitation, leaving other attendees' responses untouched; google-calendar-freebusy: busy blocks for this or named calendars; google-account-info: auth state for one connected Google account; google-account-list: every connected Google account with its own status.
+description: Live Google Calendar for one account via the Google Calendar API v3 — read plus control. Per-account OAuth authorization-code + PKCE; the consent URL is minted by the plugin and the code is exchanged by platform/ui, which holds the house-only client secret. One account can connect several Google accounts; every operational tool takes an optional account selector (the email address) and refuses ambiguously when two or more are connected and none is named. There is deliberately no Gmail surface — mail runs on the `email` plugin's IMAP/SMTP path, and Gmail's restricted scopes would force Google's annual third-party security assessment, whereas Calendar is only a sensitive scope. Tools — google-account-register / google-account-register-submit / google-account-register-poll: connect a Google Calendar (returns a consent URL; the user approves, lands on a page that fails to load by design, and pastes the code back to submit); google-calendar-list: events in the next rangeDays days, recurring series expanded; google-calendar-event: one event by id; google-calendar-create / google-calendar-update / google-calendar-cancel: control events, attendees notified, update changes only the fields named; google-calendar-respond: accept, decline or tentatively accept an invitation, leaving other attendees' responses untouched; google-calendar-freebusy: busy blocks for this or named calendars; google-account-info: auth state for one connected Google account; google-account-list: every connected Google account with its own status.
 tools:
   - name: google-account-register
     publicAllowlist: false
@@ -8,6 +8,9 @@ tools:
   - name: google-account-register-poll
     publicAllowlist: false
     adminAllowlist: false
+  - name: google-account-register-submit
+    publicAllowlist: false
+    adminAllowlist: false
   - name: google-calendar-list
     publicAllowlist: false
     adminAllowlist: false