@rubytech/create-maxy-code 0.1.246 → 0.1.248

package/payload/platform/plugins/admin/mcp/dist/tools/admin-identity-authenticate.js

@@ -0,0 +1,32 @@
+// Task 619 — admin-identity-authenticate tool.
+//
+// The agent-callable PIN-submit surface for native-CC admin sessions. The
+// PreToolUse identity gate validates the PIN, writes per-session auth state, and
+// only then allows this tool to run; the tool itself re-asks the same loopback
+// endpoint solely to fetch and return the authenticated operator's profile to
+// the agent. It never touches users.json or Neo4j directly — the endpoint is the
+// single resolution surface, so `loadUserProfile` is not duplicated here.
+export async function runAuthenticate(pin, deps = {}) {
+    const f = deps.fetchImpl ?? fetch;
+    const port = deps.uiPort ?? process.env.MAXY_UI_INTERNAL_PORT ?? "";
+    const url = `http://127.0.0.1:${port}/api/admin/identity/validate`;
+    let data;
+    try {
+        const r = await f(url, {
+            method: "POST",
+            headers: { "content-type": "application/json" },
+            body: JSON.stringify({ pin }),
+        });
+        data = (await r.json());
+    }
+    catch {
+        return "Identity service unavailable; could not load your profile.";
+    }
+    if (data.kind !== "match")
+        return "Invalid PIN.";
+    const name = data.userName ?? "operator";
+    const profile = data.aboutOwner?.ok ? (data.aboutOwner.body ?? "") : "";
+    console.error(`[admin-identity] op=about-owner-loaded userId=${(data.userId ?? "").slice(0, 8)}`);
+    return `Authenticated as ${name}.\n\n${profile}`.trim();
+}
+//# sourceMappingURL=admin-identity-authenticate.js.map

package/payload/platform/plugins/admin/mcp/dist/tools/admin-identity-authenticate.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"admin-identity-authenticate.js","sourceRoot":"","sources":["../../src/tools/admin-identity-authenticate.ts"],"names":[],"mappings":"AAAA,+CAA+C;AAC/C,EAAE;AACF,0EAA0E;AAC1E,iFAAiF;AACjF,+EAA+E;AAC/E,8EAA8E;AAC9E,iFAAiF;AACjF,0EAA0E;AAc1E,MAAM,CAAC,KAAK,UAAU,eAAe,CAAC,GAAW,EAAE,OAAyB,EAAE;IAC5E,MAAM,CAAC,GAAG,IAAI,CAAC,SAAS,IAAI,KAAK,CAAA;IACjC,MAAM,IAAI,GAAG,IAAI,CAAC,MAAM,IAAI,OAAO,CAAC,GAAG,CAAC,qBAAqB,IAAI,EAAE,CAAA;IACnE,MAAM,GAAG,GAAG,oBAAoB,IAAI,8BAA8B,CAAA;IAElE,IAAI,IAAsB,CAAA;IAC1B,IAAI,CAAC;QACH,MAAM,CAAC,GAAG,MAAM,CAAC,CAAC,GAAG,EAAE;YACrB,MAAM,EAAE,MAAM;YACd,OAAO,EAAE,EAAE,cAAc,EAAE,kBAAkB,EAAE;YAC/C,IAAI,EAAE,IAAI,CAAC,SAAS,CAAC,EAAE,GAAG,EAAE,CAAC;SAC9B,CAAC,CAAA;QACF,IAAI,GAAG,CAAC,MAAM,CAAC,CAAC,IAAI,EAAE,CAAqB,CAAA;IAC7C,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,4DAA4D,CAAC;IACtE,CAAC;IAED,IAAI,IAAI,CAAC,IAAI,KAAK,OAAO;QAAE,OAAO,cAAc,CAAC;IAEjD,MAAM,IAAI,GAAG,IAAI,CAAC,QAAQ,IAAI,UAAU,CAAC;IACzC,MAAM,OAAO,GAAG,IAAI,CAAC,UAAU,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,IAAI,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;IACxE,OAAO,CAAC,KAAK,CAAC,iDAAiD,CAAC,IAAI,CAAC,MAAM,IAAI,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,EAAE,CAAC,CAAC,EAAE,CAAC,CAAC;IAClG,OAAO,oBAAoB,IAAI,QAAQ,OAAO,EAAE,CAAC,IAAI,EAAE,CAAC;AAC1D,CAAC"}

package/payload/platform/plugins/admin/skills/investigate/SKILL.md

@@ -41,6 +41,40 @@ deliverable is a task entry, written through the resolved task surface.
 
 ---
 
+## Step 0: Evidence First — prerequisites before any reasoning
+
+**Do this before resolving the task surface, searching prior work,
+reading code, or forming any hypothesis.** The failure mode this guards
+against is forming a hypothesis from the conversation context — the
+error text the user pasted, what you assume the code does — and then
+treating evidence retrieval as redundant. By the time you have read the
+rest of this skill you have already started doing it. Stop.
+
+First action in this skill: create a TodoWrite list of the
+prerequisites below. Work through them in order. Do not read code, do
+not search prior tasks, do not propose a cause while any prerequisite
+is still open.
+
+1. **Retrieve the requested evidence.** When the user provides a
+   specific artifact — a session key, log reference, error excerpt, or
+   pointer to a particular event — that artifact is the primary
+   evidence. Retrieve it with the canonical log-retrieval tool for the
+   surface (e.g. `logs-read` for Pi sessions on deployed maxy). If a
+   retrieval hook injects an exact command, execute it as given; do not
+   improvise.
+
+   This todo may not be marked complete until the **actual retrieved
+   output appears in the transcript** — the real log lines, not a
+   summary, not a paraphrase, not "the logs confirm X." If you cannot
+   produce the output, the todo stays open and that itself is the
+   finding: an observability or retrieval gap (see Phase 1 step 6).
+
+2. **If no specific artifact was provided**, mark item 1 N/A and
+   proceed to Phase 1 — but state explicitly that no evidence artifact
+   was supplied, so the investigation starts from code-path tracing.
+
+---
+
 ## Task surface (where tasks live in this environment)
 
 Before searching prior work or writing the deliverable, resolve where
@@ -64,23 +98,6 @@ Throughout this skill, "search prior tasks", "cite prior work", and
 "write a task" mean: use the resolved surface. Do not invent a new
 location.
 
----
-
-## Evidence First
-
-When the user provides a specific artifact — a session key, log
-reference, error excerpt, or pointer to a particular event — that
-artifact is the primary evidence. Retrieve it before prior-task
-searches, code reading, or hypothesis formation.
-
-Use the canonical log-retrieval tool for the surface in question (e.g.
-`logs-read` for Pi sessions on deployed maxy). If a retrieval hook
-injects an exact command, execute it as given; do not improvise.
-
-If no specific artifact was provided, proceed directly to Phase 1.
-
----
-
 ## Phase 1: Root Cause Investigation
 
 1. **Check prior work.** Search the task surface (graph or `.tasks/`)

package/payload/platform/plugins/admin/skills/public-agent-manager/SKILL.md

@@ -1,3 +1,8 @@
+---
+name: public-agent-manager
+description: "Create, edit, clone, list, preview, and delete public agents, each a self-contained directory with its own identity, personality, knowledge, and model. Use when asked to manage, configure, or set up public agents."
+---
+
 # Public Agent Manager
 
 Create, edit, clone, list, preview, and delete public agents. Each public agent is a self-contained directory under `agents/` with its own identity, personality, knowledge, and model.
@@ -10,7 +15,7 @@ Each agent lives at `{accountDir}/agents/{slug}/`:
 |------|---------|----------|
 | `config.json` | Model, display name, status, image identity, knowledge keywords | Yes |
 | `IDENTITY.md` | Boundaries, behavioural rules — copied verbatim from the Rubytech template | Yes |
-| `SOUL.md` | Personality and role — tone, voice, warmth, greeting; plus the agent's job: give basic public info and capture the visitor's contact details for human follow-up (the chat equivalent of the landing-page contact form) | Yes |
+| `SOUL.md` | Personality and the operator-defined role — tone, voice, warmth, greeting, and the role the operator gives the agent at creation | Yes |
 | `KNOWLEDGE.md` | The business's public-facing facts at landing-page detail — pricing, FAQs, services | Yes |
 | `KNOWLEDGE-SUMMARY.md` | Auto-generated summary when KNOWLEDGE.md exceeds context budget | No |
 | `assets/` | Per-agent images (logo, avatar, icon) | No |
@@ -22,7 +27,8 @@ Each agent lives at `{accountDir}/agents/{slug}/`:
 - Lowercase a-z, 0-9, hyphens only
 - 3-50 characters, must start with a letter
 - Reserved (rejected): `admin`, `api`, `assets`, `agent-assets`, `brand`, `bot`, `privacy`
-- `public` is the conventional default slug, but public agents are optional — the platform operates without any
+- Shadowed by a static route, also rejected: `public`, `chat`, `graph`, `sessions`, `data` — a slug equal to one of these would 404 at `/{slug}`. If the operator asks for one, reject it and name the collision.
+- Public agents are optional — the platform operates without any.
 
 ## config.json
 
@@ -82,10 +88,10 @@ Present as a `select` field within the agent configuration `form` during creatio
 SOUL.md is personality and role. When the user provides content for SOUL.md, route content that belongs elsewhere to the correct file:
 
 - **Facts, pricing, services, FAQs** → KNOWLEDGE.md
-- **Engagement and qualification — how the agent draws out what the visitor needs and captures their contact details for human follow-up** → SOUL.md (this is the agent's role; the public agent is toolless, so there are no plugins to embed)
+- **Personality and the operator-defined role — how the agent sounds and what the operator has tasked it to do** → SOUL.md (the role is whatever the operator specifies at creation; the public agent is toolless, so there are no plugins to embed)
 - **Boundaries and procedural rules** → IDENTITY.md (Rubytech-controlled and copied verbatim — the agent's hard limits live there, not in SOUL)
 
-SOUL.md answers "what does this agent feel like to talk to, and what is it here to do?" — tone, warmth, formality, greeting, and the role of giving basic public info and capturing contact details. SOUL.md must not restate constraints from IDENTITY.md. When user-provided content could belong to either file, apply this test: "does this restrict what the agent does?" → IDENTITY.md. "Does this describe how the agent sounds?" → SOUL.md. If content does both (e.g. "always respond politely"), route to SOUL — the constraint is a consequence of tone, not an operational boundary. Present SOUL.md via `document-editor` for the user to review and approve. Follow the document-editor encoding constraint in IDENTITY.md when generating content.
+SOUL.md answers "what does this agent feel like to talk to, and what is it here to do?" — tone, warmth, formality, greeting, and the operator-defined role the agent was created to fill. SOUL.md must not restate constraints from IDENTITY.md. When user-provided content could belong to either file, apply this test: "does this restrict what the agent does?" → IDENTITY.md. "Does this describe how the agent sounds?" → SOUL.md. If content does both (e.g. "always respond politely"), route to SOUL — the constraint is a consequence of tone, not an operational boundary. Present SOUL.md via `document-editor` for the user to review and approve. Follow the document-editor encoding constraint in IDENTITY.md when generating content.
 
 ## KNOWLEDGE.md Population
 
@@ -138,7 +144,7 @@ The following Create steps are modified when a template is provided:
 - **Step 5** — present the template's `SOUL.md` content via `document-editor` instead of drafting from conversation. The user can edit before approving.
 - **Step 6** — pre-populate form defaults: `model` from `template.json` (or `claude-haiku-4-5` if absent), `knowledgeKeywords` from `template.json` (or empty).
 
-All other steps (3, 7-12) proceed identically — knowledge discovery, direct tagging, KNOWLEDGE.md generation, config write, budget check, and confirmation are unchanged.
+All other steps (3, 7-13) proceed identically — knowledge discovery, direct tagging, KNOWLEDGE.md generation, config write, budget check, default-setting, and confirmation are unchanged.
 
 After creation, no template metadata persists in the agent's files. The resulting agent is indistinguishable from one created manually. The user owns it completely.
 
@@ -148,7 +154,7 @@ After creation, no template metadata persists in the agent's files. The resultin
 2. Ask for the agent's name (becomes the slug) and role description
 3. **Knowledge discovery** — search the graph with admin permissions (no `agentSlug` — the agent doesn't exist yet) to find available knowledge. Present available content grouped by category for the user to select.
 4. **Install `IDENTITY.md`** — copy the Rubytech-controlled template verbatim to `agents/{slug}/IDENTITY.md`. It is fixed (the toolless public directive — Task 615) and is never drafted, edited, or presented for review.
-5. Present `SOUL.md` via document-editor with `filePath: "agents/{slug}/SOUL.md"` (draft personality and role from user conversation — tone plus the job of giving basic public info and capturing the visitor's contact details). Write on approval. Must be non-empty; an empty SOUL is refused at spawn.
+5. Present `SOUL.md` via document-editor with `filePath: "agents/{slug}/SOUL.md"` (draft personality and the operator-defined role from user conversation — tone plus the role the operator describes for the agent). Write on approval. Must be non-empty; an empty SOUL is refused at spawn.
 6. Present agent configuration via a single `form` component with these fields:
    - `knowledgeKeywords` (`text`): label "Knowledge keywords (max 5, comma-separated)", placeholder with examples relevant to the agent's role
    - `model` (`select`): label "Model", options with descriptions:
@@ -169,7 +175,8 @@ After creation, no template metadata persists in the agent's files. The resultin
 9. Write `config.json` with selected model, status "active", and `knowledgeKeywords`. This is the last gated write — placed after IDENTITY.md, SOUL.md, and KNOWLEDGE.md to prevent cascade failure if one gate stalls.
 10. Check context budget — auto-summarise if over threshold
 11. **Project the agent into the graph** — delegate to the `specialists:database-operator` specialist with the instruction: "Project public agent `{slug}` into the graph by POSTing to `/api/admin/agents/{slug}/project`." The route reads the on-disk files and idempotently MERGEs the `:Agent` node, the four owned `:KnowledgeDocument` projections (IDENTITY/SOUL/KNOWLEDGE/KNOWLEDGE-SUMMARY when present, namespaced `attachmentId="agent:<slug>:<role>"`), the `HAS_*` edges, and the `USES_KNOWLEDGE` edges to every operator-tagged doc. Loud-fail: if the route returns non-2xx, surface the error to the user verbatim — the agent's files exist on disk but its graph projection is incomplete, which means the operator's /graph view will not show this agent. Re-running the projection is safe; it is the same idempotent MERGE.
-12. Confirm creation: "Agent created. Visitors can reach it at `/{slug}`"
+12. **Set the default if none exists.** Read `defaultAgent` from `account-manage`. If it is empty, set it to this new slug via `account-update` (`field: "defaultAgent"`, `value: "{slug}"`) — otherwise the agent answers at `/{slug}` but the bare root serves nothing. If a default already exists, do not change it silently: tell the operator the current default and ask whether to switch the root to this new agent; call `account-update` only if they say yes.
+13. Confirm creation: "Agent created and reachable at `/{slug}`." If you set or changed the default in step 12, add: "The site root also serves this agent." If a different default remains, add: "The site root still serves `{currentDefault}`."
 
 ### List
 
@@ -181,7 +188,7 @@ Read `defaultAgent` from `account-manage` to identify the current default. Read
 **support** — Haiku Low cost
 3,200 / 40,000 tokens (8%) · active
 
-**public** — Haiku Low cost
+**hello** — Haiku Low cost
 9,800 / 40,000 tokens (25%) · active
 
 ### Clone

package/payload/platform/plugins/admin/skills/publish-site/SKILL.md

@@ -1,3 +1,8 @@
+---
+name: publish-site
+description: "Move an already-extracted static-site tree into the per-account static-publish surface and emit one canonical path slug. Use when asked to publish, host, or put a site online."
+---
+
 # Publish Site
 
 Call `mcp__plugin_admin_admin__publish-site` to move an already-extracted static-site tree into the per-account static-publish surface (`<accountDir>/sites/<slug>/`) and emit one canonical path slug. Pair the slug with `mcp__plugin_admin_admin__public-hostname` to surface the full URL in the same turn.

package/payload/platform/plugins/admin/skills/unzip-attachment/SKILL.md

@@ -1,3 +1,8 @@
+---
+name: unzip-attachment
+description: "Safely extract a zip archive the admin has uploaded, inventory its contents, and route each entry to the right downstream specialist, refusing path traversal, symlink escape, and decompression bombs. Use when an admin uploads a zip to unzip or extract."
+---
+
 # Unzip Attachment
 
 Safely extract a zip archive the admin has uploaded, inventory its contents, and propose one concrete follow-up per entry class — refusing archives that attempt path traversal, symlink escape, or decompression-bomb pathologies.

package/payload/platform/plugins/admin/skills/update-knowledge/SKILL.md

@@ -1,3 +1,8 @@
+---
+name: update-knowledge
+description: "Refresh a public agent's KNOWLEDGE.md from the current graph, scoped to that agent's knowledge configuration. Use when asked to update, refresh, or regenerate a public agent's knowledge."
+---
+
 # Update Knowledge
 
 Refresh a public agent's KNOWLEDGE.md from the current graph, scoped to that agent's knowledge configuration.

package/payload/platform/plugins/docs/references/admin-identity-gate.md

@@ -0,0 +1,81 @@
+# Native-CC admin PIN identity gate
+
+Every native-CC admin session — the operator chatting through claude.ai/code (web,
+desktop, mobile) over the per-account `claude rc` daemon — must bind a
+PIN-authenticated `userId` before any tool runs. This closes the gap where the
+daemon stamped one boot-time `USER_ID` (from `users.json`) onto every session,
+which is correct for at most one human on a multi-admin install. (Task 619.)
+
+The legacy cookie/PIN browser login (`POST /api/admin/session`) is a separate
+surface documented in [`admin-session.md`](admin-session.md); this gate covers the
+native path, which that login never touched.
+
+## How it works
+
+Three pieces, plus a standing audit. No cross-process `session_id` plumbing: the
+hook keys state by the `session_id` it reads from stdin; validation and profile
+resolution live behind one loopback endpoint.
+
+1. **Shared validator** — `ui/app/lib/admin-identity/pin-validator.ts`. The single
+   PIN primitive (`validatePin` → `match` / `miss` / `unavailable` / `corrupt`),
+   shared by the legacy browser login and the gate so the two cannot drift.
+
+2. **Loopback validate endpoint** — `POST /api/admin/identity/validate`
+   (`ui/server/routes/admin/identity.ts`). Loopback-only (rejects any request
+   carrying `x-forwarded-for`, which only edge-proxied browser requests have).
+   Body `{ pin, sessionId? }`. On a match it resolves the operator's `userName`
+   and `aboutOwner` via the same helpers the browser path uses
+   (`resolveUserIdentity`, `resolveOwnerProfileBlock`) — `loadUserProfile` is never
+   duplicated. On a miss with a `sessionId` it fires a best-effort manager
+   `POST /<sessionId>/stop` (only the UI process reliably holds the manager port).
+
+3. **PreToolUse gate hook** — `plugins/admin/hooks/pin-identity-gate.sh`, wired in
+   `setup-account.sh` as the first universal PreToolUse entry. Runs only for native
+   operator sessions (`MAXY_SESSION_ROLE=admin` and empty `MAXY_SPECIALIST` — the
+   latter excludes pty-spawned specialist/recorder sessions). Per tool call: if an
+   auth-state file exists for the `session_id`, allow; if the tool is
+   `admin-identity-authenticate`, post the PIN to the validate endpoint and on a
+   match write the state file and allow (on a miss/unavailable, deny + terminate);
+   any other tool while unauthenticated is denied with an instruction to
+   authenticate first. Enforcement is in the hook, not the agent's choice — a model
+   that skips the prompt reaches no other tool.
+
+The agent-callable surface is the eager-loaded `admin-identity-authenticate` MCP
+tool (admin plugin); the gate validates and binds before allowing it, and the tool
+returns the authenticated operator's profile to the agent.
+
+Auth state: `<accountDir>/state/admin-identity/<session_id>.json` (`{userId, ts}`).
+One file per authenticated conversation; bound for the session lifetime, not
+re-prompted per message. Task-tool specialist subagents share the operator's
+`session_id`, so they pass once the operator is authenticated.
+
+## Cases
+
+- **Zero admins / absent / empty `users.json`** → `pin-unavailable`, the gate
+  refuses; never a bound empty `userId`. A real install always has `users.json`
+  (the installer/seed writes it), so this is a misconfiguration guard.
+- **One admin** → still prompts; the single matching PIN binds that `userId`.
+- **Many admins** → each PIN binds its own `userId`. The account is fixed (the
+  install's own scope); there is no multi-account picker on this path.
+- **Mismatch** → the session is terminated on the first miss (no retry budget).
+
+## Observability
+
+One structured `[admin-identity]` line per step, correlated by `sessionId`:
+
+```
+op=loopback-spawn-received → op=pin-prompted → (op=pin-bound source=pin |
+op=pin-miss → op=session-terminated) ; the MCP tool emits op=about-owner-loaded.
+```
+
+**Standing audit** (`services/claude-session-manager/src/admin-identity-audit.ts`,
+every 60s) reconciles, independently of the hook, live native-operator sessions
+(watcher rows with `role === null` — daemon-spawned, no sidecar) that reached real
+tool use against the auth-state files. Any such session with no state file emits
+`[admin-identity] op=audit-orphan sessionId=…
+reason=loopback-session-without-authenticated-userId`. This is the no-event
+detector: a silent gate bypass leaves no per-session log line, but the audit still
+surfaces it.
+
+Diagnostic path: `journalctl --user -u <brand>-admin | grep -E '\[admin-identity\]'`,
+then filter by `sessionId` for one session's full lifeline.

package/payload/platform/plugins/memory/skills/conversation-archive-enrich/SKILL.md

@@ -1,5 +1,6 @@
 ---
 name: conversation-archive-enrich
+description: "Walk an existing ConversationArchive's chunks and derive high-confidence claims and insights into the graph, one operator-gated proposal per row. Use when asked to enrich, derive insights from, or mine an existing conversation archive."
 ---
 
 # Conversation Archive — chunk-anchored insight derivation

package/payload/platform/plugins/memory/skills/conversational-memory/SKILL.md

@@ -1,3 +1,8 @@
+---
+name: conversational-memory
+description: "Notice, store, and recall who the owner is and how they work, accumulated from natural conversation rather than forms. Use when recording or retrieving user profile, preferences, and remembered context across sessions."
+---
+
 # Conversational Memory
 
 Memory accumulates from conversation — never from questionnaires, quizzes, or onboarding forms. The owner reveals who they are and how they work through natural interaction. Your role is to notice, store, and recall that knowledge so every session feels continuous rather than starting from scratch.

package/payload/platform/plugins/workflows/skills/workflow-manager/SKILL.md

@@ -1,3 +1,8 @@
+---
+name: workflow-manager
+description: "Create, test, and diagnose persistent workflows that automate recurring multi-step processes spanning different plugin tools. Use when the user describes a recurring multi-step process to automate."
+---
+
 # Workflow Manager
 
 Create, test, and diagnose persistent workflows that automate recurring multi-step processes.

package/payload/platform/scripts/check-skill-frontmatter.mjs

@@ -0,0 +1,139 @@
+#!/usr/bin/env node
+// Task 621 — bundle-time frontmatter check for every SKILL.md across the
+// plugins trees.
+//
+// Why: Claude Code surfaces a skill in the session's available-skills reminder,
+// and makes it matchable by the description-driven search tools (ToolSearch,
+// skill-find), ONLY if its SKILL.md opens with YAML frontmatter carrying a
+// `name:` and a `description:`. A SKILL.md that opens straight into an `#` H1
+// has no description for the reminder to list and nothing for fuzzy search to
+// match — it stays invisible until an operator finds the directory by hand,
+// while the agent burns turns on blind find/grep. The skill remains invokable
+// by exact name, so the defect is silent: no error, no log line. This module
+// is the standing guard that fails the bundle before such a payload ships, so
+// the next frontmatter-less skill cannot regress discovery the same way.
+//
+// A file passes iff it opens with a `---\n...\n---` frontmatter block whose
+// keys include both `name:` and `description:`. Three failure shapes are
+// reported distinctly: no frontmatter block at all, missing `name:`, missing
+// `description:`.
+
+import { existsSync, readdirSync, readFileSync, statSync } from "node:fs";
+import { resolve, relative, join, dirname } from "node:path";
+import { pathToFileURL } from "node:url";
+
+// Walk `dir` recursively, collecting every file whose basename matches `predicate`.
+function walk(dir, predicate, out = []) {
+  if (!existsSync(dir)) return out;
+  let entries;
+  try {
+    entries = readdirSync(dir);
+  } catch {
+    return out;
+  }
+  for (const entry of entries) {
+    const full = join(dir, entry);
+    let st;
+    try {
+      st = statSync(full);
+    } catch {
+      continue;
+    }
+    if (st.isDirectory()) {
+      walk(full, predicate, out);
+    } else if (predicate(entry, full)) {
+      out.push(full);
+    }
+  }
+  return out;
+}
+
+// Extract the leading frontmatter block. A block exists only when the very
+// first line is `---` and a closing `---` follows on its own line. The closing
+// fence is anchored to end-of-line (`\r?\n|$`) so a body line that merely
+// starts with `---` (a `---trailing` divider) cannot be mistaken for the
+// close, and a frontmatter-only file ending exactly at `---` still matches.
+// Returns the block body (between the fences) or null when there is no block.
+function frontmatterBody(raw) {
+  const m = raw.match(/^---\r?\n([\s\S]*?)\r?\n---(?:\r?\n|$)/);
+  return m ? m[1] : null;
+}
+
+// True if the block contains a `<key>:` line at the start of any line. The key
+// may be followed by a value, a block scalar (`|`/`>`), or nothing.
+function hasKey(block, key) {
+  const re = new RegExp(`^${key}:`, "m");
+  return re.test(block);
+}
+
+function scanFile(filePath, repoRoot) {
+  let raw;
+  try {
+    raw = readFileSync(filePath, "utf-8");
+  } catch {
+    return null;
+  }
+  const source = relative(repoRoot, filePath);
+  const block = frontmatterBody(raw);
+  if (block === null) {
+    return { source, reason: "no YAML frontmatter block (file opens without a leading `---`)" };
+  }
+  const missing = [];
+  if (!hasKey(block, "name")) missing.push("name");
+  if (!hasKey(block, "description")) missing.push("description");
+  if (missing.length > 0) {
+    return { source, reason: `frontmatter missing required key(s): ${missing.join(", ")}` };
+  }
+  return null;
+}
+
+export function runSkillFrontmatterCheck({ platformRoot, premiumRoot }) {
+  const repoRoot = resolve(platformRoot, "..");
+  const sources = [];
+
+  // platform: every SKILL.md under plugins/
+  walk(resolve(platformRoot, "plugins"), (name) => name === "SKILL.md", sources);
+
+  // premium: every SKILL.md under any bundle (standalone or sub)
+  if (premiumRoot && existsSync(premiumRoot)) {
+    walk(premiumRoot, (name) => name === "SKILL.md", sources);
+  }
+
+  const violations = [];
+  for (const src of sources) {
+    const v = scanFile(src, repoRoot);
+    if (v) violations.push(v);
+  }
+
+  return {
+    ok: violations.length === 0,
+    violations,
+    scanned: sources.length,
+  };
+}
+
+// CLI entry — `node check-skill-frontmatter.mjs [platformRoot] [premiumRoot]`.
+// pathToFileURL keeps the self-detect correct across paths with spaces or
+// non-ASCII characters. When loaded via `import` from bundle.js the URLs
+// differ and this block is skipped.
+if (process.argv[1] && import.meta.url === pathToFileURL(process.argv[1]).href) {
+  const defaultPlatform = resolve(import.meta.dirname, "..");
+  const defaultPremium = resolve(import.meta.dirname, "..", "..", "premium-plugins");
+  const platformRoot = process.argv[2] ? resolve(process.argv[2]) : defaultPlatform;
+  const premiumRoot = process.argv[3] ? resolve(process.argv[3]) : defaultPremium;
+  const r = runSkillFrontmatterCheck({ platformRoot, premiumRoot });
+  if (!r.ok) {
+    for (const v of r.violations) {
+      console.error(`[bundle-validator] skill frontmatter missing`);
+      console.error(`  source: ${v.source}`);
+      console.error(`  reason: ${v.reason}`);
+    }
+    console.error(
+      `FATAL: ${r.violations.length} SKILL.md file(s) without name/description frontmatter across ${r.scanned} scanned file(s).`,
+    );
+    process.exit(1);
+  }
+  console.log(
+    `[bundle-validator] skill frontmatter ok scanned=${r.scanned}`,
+  );
+}

package/payload/platform/scripts/setup-account.sh

@@ -75,6 +75,11 @@ cat > "$ACCOUNT_SETTINGS" << SETTINGS_EOF
   },
   "hooks": {
     "PreToolUse": [
+      {
+        "hooks": [
+          { "type": "command", "command": "bash $HOOKS_PATH/pin-identity-gate.sh" }
+        ]
+      },
       {
         "matcher": "Write",
         "hooks": [
@@ -255,22 +260,6 @@ if [ ! -f "$ACCOUNT_DIR/account.json" ]; then
   fi
 fi
 
-# Backfill defaultAgent in account.json if missing (existing accounts earlier).
-# Uses the first non-admin agent directory that has a config.json.
-if [ -f "$ACCOUNT_DIR/account.json" ] && ! grep -q '"defaultAgent"' "$ACCOUNT_DIR/account.json"; then
-  _DEFAULT_SLUG=""
-  for _AGENT_DIR in "$ACCOUNT_DIR/agents"/*/; do
-    _AGENT_NAME="$(basename "$_AGENT_DIR")"
-    [ "$_AGENT_NAME" = "admin" ] && continue
-    [ -f "$_AGENT_DIR/config.json" ] && { _DEFAULT_SLUG="$_AGENT_NAME"; break; }
-  done
-  if [ -n "$_DEFAULT_SLUG" ]; then
-    # Insert defaultAgent before the closing brace
-    sed -i'' "s/}$/,\"defaultAgent\":\"$_DEFAULT_SLUG\"}/" "$ACCOUNT_DIR/account.json"
-    echo "  Backfilled defaultAgent=$_DEFAULT_SLUG in account.json"
-  fi
-fi
-
 # ------------------------------------------------------------------
 # 5. Seed enabledPlugins from brand.json plugins.defaultEnabled
 # ------------------------------------------------------------------

package/payload/platform/services/claude-session-manager/dist/admin-identity-audit.d.ts

@@ -0,0 +1,39 @@
+import type { FsWatcher } from './fs-watcher.js';
+export type Logger = (line: string) => void;
+export interface AuditSession {
+    sessionId: string;
+    /** Sidecar role, or null for native rc-daemon operator sessions. */
+    role: string | null;
+    state: string;
+    /** True when the JSONL contains an assistant tool_use whose name is not the
+     *  auth tool. */
+    usedRealTool: boolean;
+}
+export interface AuditOnceDeps {
+    sessions: AuditSession[];
+    hasState: (sessionId: string) => boolean;
+    logger: Logger;
+}
+/** Pure reconciliation: emit one audit-orphan line per live native-operator
+ *  session that used a real tool but has no auth-state file. */
+export declare function auditOnce(deps: AuditOnceDeps): number;
+export interface IdentityAuditDeps {
+    watcher: FsWatcher;
+    /** Account dir (the manager's spawnCwd); used to derive JSONL + state paths. */
+    spawnCwd: string;
+    /** Directory holding per-session auth-state files written by the gate hook. */
+    stateDir: string;
+    intervalMs: number;
+    logger: Logger;
+}
+export interface IdentityAudit {
+    start(): void;
+    stop(): void;
+    /** Run one audit pass synchronously. Exposed for tests. */
+    tickOnce(): {
+        scanned: number;
+        orphans: number;
+    };
+}
+export declare function createIdentityAudit(deps: IdentityAuditDeps): IdentityAudit;
+//# sourceMappingURL=admin-identity-audit.d.ts.map

package/payload/platform/services/claude-session-manager/dist/admin-identity-audit.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"admin-identity-audit.d.ts","sourceRoot":"","sources":["../src/admin-identity-audit.ts"],"names":[],"mappings":"AA4BA,OAAO,KAAK,EAAE,SAAS,EAAc,MAAM,iBAAiB,CAAA;AAU5D,MAAM,MAAM,MAAM,GAAG,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,CAAA;AAE3C,MAAM,WAAW,YAAY;IAC3B,SAAS,EAAE,MAAM,CAAA;IACjB,oEAAoE;IACpE,IAAI,EAAE,MAAM,GAAG,IAAI,CAAA;IACnB,KAAK,EAAE,MAAM,CAAA;IACb;qBACiB;IACjB,YAAY,EAAE,OAAO,CAAA;CACtB;AAED,MAAM,WAAW,aAAa;IAC5B,QAAQ,EAAE,YAAY,EAAE,CAAA;IACxB,QAAQ,EAAE,CAAC,SAAS,EAAE,MAAM,KAAK,OAAO,CAAA;IACxC,MAAM,EAAE,MAAM,CAAA;CACf;AAED;gEACgE;AAChE,wBAAgB,SAAS,CAAC,IAAI,EAAE,aAAa,GAAG,MAAM,CAarD;AAiCD,MAAM,WAAW,iBAAiB;IAChC,OAAO,EAAE,SAAS,CAAA;IAClB,gFAAgF;IAChF,QAAQ,EAAE,MAAM,CAAA;IAChB,+EAA+E;IAC/E,QAAQ,EAAE,MAAM,CAAA;IAChB,UAAU,EAAE,MAAM,CAAA;IAClB,MAAM,EAAE,MAAM,CAAA;CACf;AAED,MAAM,WAAW,aAAa;IAC5B,KAAK,IAAI,IAAI,CAAA;IACb,IAAI,IAAI,IAAI,CAAA;IACZ,2DAA2D;IAC3D,QAAQ,IAAI;QAAE,OAAO,EAAE,MAAM,CAAC;QAAC,OAAO,EAAE,MAAM,CAAA;KAAE,CAAA;CACjD;AAED,wBAAgB,mBAAmB,CAAC,IAAI,EAAE,iBAAiB,GAAG,aAAa,CA0C1E"}