@rubytech/create-maxy-code 0.1.308 → 0.1.310

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:3dc18de6b756569b69f9991344abc2af34919802f4e632a815f2250b8a11f786
+content-hash: sha256:8fd7006bd54f69d5932bc831cf46f9ced8e01318f5fac0963f4285bc1e4b21a0
 brand: maxy-code
 product-name: Maxy
 ---
@@ -2489,6 +2489,26 @@ authoritative. This section names the surfaces and what backs each.
 > via the same admin-gated reader routes, never the operator's own session. The
 > operator surface is documented in full in the internal doc
 > `maxy-code/.docs/operator-dashboard.md`.
+>
+> **Width.** The operator header, the operator chat column, and the `/data`
+> header+toolbar+body all render in one centred column bounded to
+> `--chat-measure` (48rem). That token is a `:root` design token (beside
+> `--measure`/`--gutter`); the operator-header clamp
+> (`.admin-shell-root:has(> .platform-operator) > .admin-header`), the chat-column
+> clamp (`.platform-operator > .webchat-page`), and the `/data` clamp
+> (`.data-main`) all read it, so logo and burger align to the panel edges on both
+> surfaces. The admin shell carries no `--chat-measure` consumer and stays
+> edge-to-edge; the public webchat (`.public-surface`) inherits the same value.
+>
+> **Conversations item.** The dynamic Conversations burger item appears on
+> **both** the operator chat surface and `/data` whenever ≥1 reviewable
+> conversation exists (the count/channels are fetched per surface from
+> `/whatsapp-reader/conversations` with the operator's session key). On `/data`
+> selecting it renders the same read-only reader in place (the file browser is
+> swapped for it; Back returns). The flyout-open signal
+> `[operator-ui] op=conversations-menu present=<bool> channels=[…] count=<n>`
+> fires on `/data` too — `present=false` there while the chat surface shows the
+> item is the props-not-wired signature.
 
 | Surface | What it does | Backed by |
 |---|---|---|

package/payload/platform/plugins/admin/skills/plugin-management/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: plugin-management
-description: "Install, remove, enable, and configure plugins and account settings via conversation."
+description: "Install, remove, enable, and configure plugins and account settings via conversation. This is how an operator turns the assistant's capabilities and integrations on and off — \"turn on email\", \"enable WhatsApp\", \"add a Telegram integration\", \"connect a new integration\", \"what can you connect to\", \"what plugins are available\", \"set up an integration\", \"disable X\", or changing an account setting. Each plugin is an integration or capability the assistant can gain; this skill is the surface for adding, removing, or reconfiguring them."
 ---
 
 # Plugin Management

package/payload/platform/plugins/admin/skills/specialist-management/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: specialist-management
-description: "Install, remove, and manage specialist subagents and premium plugin agents."
+description: "Install, remove, and manage specialist subagents and premium plugin agents — the dedicated helpers the assistant can hand work to. This is how an operator adds a new helper or worker agent: \"add a content writer\", \"set up a research agent\", \"give me a helper that writes documents\", \"add an agent that does X\", \"hire an assistant for Y\", \"what specialists can I add\", or removing one. Each specialist is a focused agent the assistant delegates a domain to (writing, research, and the like)."
 ---
 
 # Specialist Management

package/payload/platform/plugins/cloudflare/skills/cloudflare/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cloudflare
-description: Cloudflare operations for the install — tunnel setup/diagnosis/reset, DNS edits, Pages hosting, and D1 data capture. The agent drives `cloudflared` and `wrangler` directly via Bash and reads the matching reference before each operation class; success is always a live behavioural signal (external HTTP 200, a deployed URL, a D1 round-trip), never an exit code.
+description: Cloudflare operations for the install — tunnel setup/diagnosis/reset, DNS edits, Pages hosting, and D1 data capture. This is the skill behind operator-facing goals like "set up the operator dashboard", "set up the operator host", "give me (or a colleague) a remote dashboard to run the assistant", "let me access the assistant from anywhere", "put my dashboard or site online", "point a custom domain at this", and "why is my site or hostname returning a 404 / 502". It provisions the operator-dashboard host — the trimmed remote control panel (sessions, chat, data; no graph, no browser) — by adding the tunnel ingress and the operator-domains.json classification, stands up admin / public / operator hostnames over the Cloudflare tunnel so the install is reachable on the internet, hosts static sites on Pages, and captures form submissions to D1. The agent drives `cloudflared` and `wrangler` directly via Bash and reads the matching reference before each operation class; success is always a live behavioural signal (external HTTP 200, a deployed URL, a D1 round-trip), never an exit code.
 ---
 
 # Cloudflare operations

package/payload/platform/plugins/docs/references/admin-ui.md

@@ -258,6 +258,26 @@ authoritative. This section names the surfaces and what backs each.
 > via the same admin-gated reader routes, never the operator's own session. The
 > operator surface is documented in full in the internal doc
 > `maxy-code/.docs/operator-dashboard.md`.
+>
+> **Width.** The operator header, the operator chat column, and the `/data`
+> header+toolbar+body all render in one centred column bounded to
+> `--chat-measure` (48rem). That token is a `:root` design token (beside
+> `--measure`/`--gutter`); the operator-header clamp
+> (`.admin-shell-root:has(> .platform-operator) > .admin-header`), the chat-column
+> clamp (`.platform-operator > .webchat-page`), and the `/data` clamp
+> (`.data-main`) all read it, so logo and burger align to the panel edges on both
+> surfaces. The admin shell carries no `--chat-measure` consumer and stays
+> edge-to-edge; the public webchat (`.public-surface`) inherits the same value.
+>
+> **Conversations item.** The dynamic Conversations burger item appears on
+> **both** the operator chat surface and `/data` whenever ≥1 reviewable
+> conversation exists (the count/channels are fetched per surface from
+> `/whatsapp-reader/conversations` with the operator's session key). On `/data`
+> selecting it renders the same read-only reader in place (the file browser is
+> swapped for it; Back returns). The flyout-open signal
+> `[operator-ui] op=conversations-menu present=<bool> channels=[…] count=<n>`
+> fires on `/data` too — `present=false` there while the chat surface shows the
+> item is the props-not-wired signature.
 
 | Surface | What it does | Backed by |
 |---|---|---|

package/payload/platform/services/claude-session-manager/dist/http-server.d.ts

@@ -36,6 +36,8 @@ export interface HttpDeps extends Omit<SpawnDeps, 'onSessionReady' | 'watcher'>
     rcSpawnUrlWaitMs?: number;
 }
 export declare function forkArgvSegment(fromSessionId: string, newSessionId: string, model: string): string[];
+export declare function reseatIdentityPrompt(model: string): string;
+export declare function authenticatedIdentityPrompt(name: string | null): string;
 export declare function formatReseatLine(fromModel: string | null, toModel: string, oldSessionId: string, newSessionId: string, observed: string | null): string;
 export declare function firstPostArmAssistantModel(lines: string[], armTimeMs: number): string | null;
 /** Task 189 — Hono instance with the test-only fan-out trigger attached.

package/payload/platform/services/claude-session-manager/dist/http-server.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"http-server.d.ts","sourceRoot":"","sources":["../src/http-server.ts"],"names":[],"mappings":"AAsBA,OAAO,EAAE,IAAI,EAAE,MAAM,MAAM,CAAA;AAY3B,OAAO,EAgBL,KAAK,SAAS,EAEf,MAAM,kBAAkB,CAAA;AAqBzB,OAAO,KAAK,EAAE,SAAS,EAAyB,MAAM,iBAAiB,CAAA;AAEvE,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,yBAAyB,CAAA;AAC1D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,wBAAwB,CAAA;AAC3D,OAAO,EAAqB,KAAK,cAAc,EAAE,MAAM,uBAAuB,CAAA;AAC9E,OAAO,EAAE,cAAc,EAAE,MAAM,uBAAuB,CAAA;AACtD,OAAO,EAAE,mBAAmB,EAAE,MAAM,4BAA4B,CAAA;AAgFhE,eAAO,MAAM,kBAAkB,QAA2B,CAAA;AAS1D,eAAO,MAAM,4BAA4B,QAAS,CAAA;AAIlD,MAAM,WAAW,QAAS,SAAQ,IAAI,CAAC,SAAS,EAAE,gBAAgB,GAAG,SAAS,CAAC;IAC7E;;qEAEiE;IACjE,MAAM,CAAC,EAAE,MAAM,CAAA;IACf,OAAO,EAAE,SAAS,CAAA;IAClB,WAAW,EAAE,MAAM,CAAA;IACnB,iBAAiB,EAAE,MAAM,CAAA;IACzB,kBAAkB,EAAE,WAAW,CAAA;IAC/B,eAAe,EAAE,aAAa,CAAA;IAC9B;kFAC8E;IAC9E,cAAc,EAAE,cAAc,CAAA;IAC9B;;gFAE4E;IAC5E,cAAc,EAAE,cAAc,CAAA;IAC9B;;;6BAGyB;IACzB,mBAAmB,CAAC,EAAE,mBAAmB,CAAA;IACzC;;gFAE4E;IAC5E,gBAAgB,CAAC,EAAE,MAAM,CAAA;CAC1B;AAwGD,wBAAgB,eAAe,CAAC,aAAa,EAAE,MAAM,EAAE,YAAY,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,MAAM,EAAE,CAEpG;AAMD,wBAAgB,gBAAgB,CAC9B,SAAS,EAAE,MAAM,GAAG,IAAI,EACxB,OAAO,EAAE,MAAM,EACf,YAAY,EAAE,MAAM,EACpB,YAAY,EAAE,MAAM,EACpB,QAAQ,EAAE,MAAM,GAAG,IAAI,GACtB,MAAM,CAER;AAkCD,wBAAgB,0BAA0B,CAAC,KAAK,EAAE,MAAM,EAAE,EAAE,SAAS,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAe5F;AAwJD;;;kEAGkE;AAClE,MAAM,MAAM,OAAO,GAAG,IAAI,GAAG;IAC3B,2BAA2B,CAAC,SAAS,EAAE,MAAM,GAAG,IAAI,CAAA;IACpD;;;+CAG2C;IAC3C,sBAAsB,CAAC,SAAS,EAAE,MAAM,GAAG,IAAI,CAAA;CAChD,CAAA;AAmBD,wBAAgB,YAAY,CAAC,IAAI,EAAE,QAAQ,GAAG,OAAO,CA+lEpD"}
+{"version":3,"file":"http-server.d.ts","sourceRoot":"","sources":["../src/http-server.ts"],"names":[],"mappings":"AAsBA,OAAO,EAAE,IAAI,EAAE,MAAM,MAAM,CAAA;AAY3B,OAAO,EAgBL,KAAK,SAAS,EAEf,MAAM,kBAAkB,CAAA;AAqBzB,OAAO,KAAK,EAAE,SAAS,EAAyB,MAAM,iBAAiB,CAAA;AAEvE,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,yBAAyB,CAAA;AAC1D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,wBAAwB,CAAA;AAC3D,OAAO,EAAqB,KAAK,cAAc,EAAE,MAAM,uBAAuB,CAAA;AAC9E,OAAO,EAAE,cAAc,EAAE,MAAM,uBAAuB,CAAA;AACtD,OAAO,EAAE,mBAAmB,EAAE,MAAM,4BAA4B,CAAA;AAgFhE,eAAO,MAAM,kBAAkB,QAA2B,CAAA;AAS1D,eAAO,MAAM,4BAA4B,QAAS,CAAA;AAIlD,MAAM,WAAW,QAAS,SAAQ,IAAI,CAAC,SAAS,EAAE,gBAAgB,GAAG,SAAS,CAAC;IAC7E;;qEAEiE;IACjE,MAAM,CAAC,EAAE,MAAM,CAAA;IACf,OAAO,EAAE,SAAS,CAAA;IAClB,WAAW,EAAE,MAAM,CAAA;IACnB,iBAAiB,EAAE,MAAM,CAAA;IACzB,kBAAkB,EAAE,WAAW,CAAA;IAC/B,eAAe,EAAE,aAAa,CAAA;IAC9B;kFAC8E;IAC9E,cAAc,EAAE,cAAc,CAAA;IAC9B;;gFAE4E;IAC5E,cAAc,EAAE,cAAc,CAAA;IAC9B;;;6BAGyB;IACzB,mBAAmB,CAAC,EAAE,mBAAmB,CAAA;IACzC;;gFAE4E;IAC5E,gBAAgB,CAAC,EAAE,MAAM,CAAA;CAC1B;AAwGD,wBAAgB,eAAe,CAAC,aAAa,EAAE,MAAM,EAAE,YAAY,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,MAAM,EAAE,CAEpG;AAQD,wBAAgB,oBAAoB,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,CAE1D;AAUD,wBAAgB,2BAA2B,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,GAAG,MAAM,CAMvE;AAMD,wBAAgB,gBAAgB,CAC9B,SAAS,EAAE,MAAM,GAAG,IAAI,EACxB,OAAO,EAAE,MAAM,EACf,YAAY,EAAE,MAAM,EACpB,YAAY,EAAE,MAAM,EACpB,QAAQ,EAAE,MAAM,GAAG,IAAI,GACtB,MAAM,CAER;AAkCD,wBAAgB,0BAA0B,CAAC,KAAK,EAAE,MAAM,EAAE,EAAE,SAAS,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAe5F;AAwJD;;;kEAGkE;AAClE,MAAM,MAAM,OAAO,GAAG,IAAI,GAAG;IAC3B,2BAA2B,CAAC,SAAS,EAAE,MAAM,GAAG,IAAI,CAAA;IACpD;;;+CAG2C;IAC3C,sBAAsB,CAAC,SAAS,EAAE,MAAM,GAAG,IAAI,CAAA;CAChD,CAAA;AAmBD,wBAAgB,YAAY,CAAC,IAAI,EAAE,QAAQ,GAAG,OAAO,CA4nEpD"}

package/payload/platform/services/claude-session-manager/dist/http-server.js

@@ -190,6 +190,30 @@ const AUTO_ARCHIVE_SPECIALIST = 'database-operator';
 export function forkArgvSegment(fromSessionId, newSessionId, model) {
     return ['--resume', fromSessionId, '--fork-session', '--session-id', newSessionId, '--model', model];
 }
+// Task 879 — the re-seated fork inherits the source's history, including the
+// source's earlier self-identification on the OLD model. The rc-spawn path does
+// not compose --append-system-prompt (only fresh spawnSession does), so the
+// fork alone gets an authoritative current-model line on its argv: the agent
+// answers the live model on the first ask, without being challenged. General
+// self-ID accuracy (absent a re-seat) is out of scope — only the fork gets it.
+export function reseatIdentityPrompt(model) {
+    return `This conversation now runs on the model ${model}. Earlier messages may show you identifying as a different model; that is stale context from before a model change — disregard it and state ${model} as your current model if asked.`;
+}
+// Task 889 — the authenticated-admin identity line for a webchat-bound admin
+// rc session. The rc-spawn path composes no fresh-spawn system prompt, so this
+// --append-system-prompt segment is the agent's only signal of who it is
+// talking to. Re-passed on every spawn (fresh and resume) because the append
+// fact is not persisted in the JSONL; without it the agent guesses the
+// Anthropic account email visible in its context. `name` is the resolved
+// `AdminUser` display name, or null/empty when the identity could not be
+// resolved — the not-resolvable line is still injected to suppress the guess.
+export function authenticatedIdentityPrompt(name) {
+    const trimmed = name?.trim() ?? '';
+    if (trimmed.length > 0) {
+        return `This admin webchat session is authenticated as ${trimmed}. If you are asked who you are talking to or who this session is authenticated as, answer ${trimmed}; never infer the operator's identity from an email address or account label visible in your context.`;
+    }
+    return `This admin webchat session's authenticated identity could not be resolved. If you are asked who you are talking to or who this session is authenticated as, say the identity is not resolvable; never infer it from an email address or account label visible in your context.`;
+}
 // Task 876 — the re-seat post-condition line. Emitted ONLY after a real
 // assistant turn on the fork is read (intention is not logged, per the
 // observability contract): a re-seat that silently lands on the wrong model
@@ -1758,6 +1782,13 @@ export function buildHttpApp(deps) {
         const adminUserId = typeof body.adminUserId === 'string' && body.adminUserId.length > 0 && body.adminUserId.length <= 128
             ? body.adminUserId
             : undefined;
+        // Task 889 — the resolved authenticated-admin display name, resolved by the
+        // UI from USER_ID -> AdminUser (the manager holds no Neo4j driver) and
+        // shape-bounded here. Absent => the identity line renders its not-resolvable
+        // form. Only consumed for webchat-bound admin spawns.
+        const authenticatedName = typeof body.authenticatedName === 'string' && body.authenticatedName.length > 0 && body.authenticatedName.length <= 256
+            ? body.authenticatedName
+            : undefined;
         // Task 682 — per-session userId override. Server-resolved by the UI from the
         // authoritative users.json/account.json (never message content) and shape-
         // validated here the same way as personId. Absent for owner self-phone and
@@ -1874,10 +1905,16 @@ export function buildHttpApp(deps) {
         const argv = ['--remote-control'];
         if (name)
             argv.push(name);
+        // Task 889 — append-system-prompt segments are accumulated and pushed once
+        // (below, after channel resolution) so the re-seat model line and the
+        // authenticated-identity line share a single flag.
+        const appendSegments = [];
         // Task 876 — a re-seat forks the source onto the pre-minted target id; the
         // ordinary fresh/resume single-id push is replaced by the fork segment.
         if (forkFromSessionId !== null && reseatModel !== null && sessionId) {
             argv.push(...forkArgvSegment(forkFromSessionId, sessionId, reseatModel));
+            // Task 879 — authoritative current-model signal for the fork only.
+            appendSegments.push(reseatIdentityPrompt(reseatModel));
         }
         else if (sessionId) {
             argv.push(mode === 'resume' ? '--resume' : '--session-id', sessionId);
@@ -1999,6 +2036,19 @@ export function buildHttpApp(deps) {
                 }
             }
         }
+        // Task 889 — a webchat-bound admin rc session is the /chat admin surface.
+        // Inject the authenticated-identity line (resolved name, or the explicit
+        // not-resolvable form) so the agent states who it is talking to instead of
+        // guessing the account email. Gated on the webchat binding + admin role so
+        // public visitor spawns and the one-shot admin jobs are untouched. The
+        // breadcrumb makes a silent resolution regression visible without a chat.
+        if (effectiveWebchatChannel && rcRole === 'admin') {
+            appendSegments.push(authenticatedIdentityPrompt(authenticatedName ?? null));
+            deps.logger(`[rc-spawn] op=identity-injected userId=${adminUserId ? adminUserId.slice(0, 8) : 'none'} resolved=${authenticatedName ? 1 : 0}`);
+        }
+        if (appendSegments.length > 0) {
+            argv.push('--append-system-prompt', appendSegments.join('\n\n'));
+        }
         // Task 626 — the initial message is the trailing positional, processed as
         // the session's first user turn at PTY startup. One-shot jobs omit `name`
         // so the prompt is the sole positional.