@rubytech/create-maxy-code 0.1.557 → 0.1.559

package/package.json

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

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

@@ -221,7 +221,7 @@ Tools are available via the `admin` MCP server.
 
 **Intent → skill resolution.** `skill-search query="<free text>"` is the description-driven resolver: it walks every plugin's `skills/<slug>/SKILL.md`, reads frontmatter `name`+`description` only, and returns the top owners ranked by a frequency-aware match (distinctive terms dominate; common trigger words contribute little) with each owner's canonical `skills/<slug>/SKILL.md` path. It exists because the session's available-skills menu — the only other description-driven surface — is injected at session start and resume but **not** after a context compaction; once it leaves context, intent-phrased guesses miss `skill-find` (which is exact-slug only) and the agent falls back to blind `find`/`grep`. `skill-search` makes the mapping a single deterministic call regardless of whether the menu is present; feed the returned slug straight to `skill-load`. `skill-find` and `skill-load` stay exact-slug — they resolve a slug you already know — and are unchanged.
 
-**Admin-seat authoring-skill gate.** `skill-load` and `plugin-read` refuse to return the body of a content-producer-owned authoring skill — `professional-document`, `a4-print-documents`, `publish-site` — when the caller is the admin seat (`MAXY_SESSION_ROLE=admin` with no `MAXY_SPECIALIST`). The refusal relays one line — "This deliverable is owned by content-producer. Dispatch it with the Agent tool and subagent_type content-producer." — so the admin's next action is the dispatch, not inline authoring. `plugin-read` extracts the skill slug from a `skills/<slug>/…` file path (or a slug buried in `pluginName`), so the raw-SKILL.md read path can't bypass the gate; `PLUGIN.md` and plain `references/*` reads are untouched. content-producer's own spawns carry `MAXY_SPECIALIST=content-producer` and resolve these skills normally (it reaches them via the native `Skill` tool regardless), and the public seat is out of scope. The gate is a pure name+env check before any filesystem read and fails open for any non-admin or unidentified seat — it never bricks a legitimate load. Each block emits `[admin-skill-gate] role=admin skill=<name> decision=block reason=content-producer-owned`. This is the enforcement layer; the IDENTITY.md delegation paragraph documents the intent but is not the gate ([[feedback_deterministic_means_remove_llm]], [[feedback_doctrine_paragraph_is_not_a_gate]]). Skills the admin invokes directly are deliberately excluded: `unzip-attachment` (its SKILL.md says "Invoked by the admin agent directly — admin owns all unzipping", then routes the extracted tree to a specialist) and `deck-pages` (admin-owned, a content-producer refusal target). The set is each skill's own SKILL.md "Invoked by" declaration, not the admin plugin's skill catalogue (which lists these admin-hosted skills for discovery — the catalogue is the inline path this gate closes).
+**Admin-seat authoring-skill gate.** `skill-load` and `plugin-read` refuse to return the body of a content-producer-owned authoring skill — `professional-document`, `a4-print-documents`, `publish-site`, `video-production` — when the caller is the admin seat (`MAXY_SESSION_ROLE=admin` with no `MAXY_SPECIALIST`). The refusal relays one line — "This deliverable is owned by content-producer. Dispatch it with the Agent tool and subagent_type content-producer." — so the admin's next action is the dispatch, not inline authoring. `plugin-read` extracts the skill slug from a `skills/<slug>/…` file path (or a slug buried in `pluginName`), so the raw-SKILL.md read path can't bypass the gate; `PLUGIN.md` and plain `references/*` reads are untouched. content-producer's own spawns carry `MAXY_SPECIALIST=content-producer` and resolve these skills normally (it reaches them via the native `Skill` tool regardless), and the public seat is out of scope. The gate is a pure name+env check before any filesystem read and fails open for any non-admin or unidentified seat — it never bricks a legitimate load. Each block emits `[admin-skill-gate] role=admin skill=<name> decision=block reason=content-producer-owned`. This is the enforcement layer; the IDENTITY.md delegation paragraph documents the intent but is not the gate ([[feedback_deterministic_means_remove_llm]], [[feedback_doctrine_paragraph_is_not_a_gate]]). Skills the admin invokes directly are deliberately excluded: `unzip-attachment` (its SKILL.md says "Invoked by the admin agent directly — admin owns all unzipping", then routes the extracted tree to a specialist) and `deck-pages` (admin-owned, a content-producer refusal target). The set is each skill's own SKILL.md "Invoked by" declaration, not the admin plugin's skill catalogue (which lists these admin-hosted skills for discovery — the catalogue is the inline path this gate closes).
 
 **Client sub-accounts carry one owner identity, no operator seats.** Since admin access is install-wide (`canAccessAdmin` never reads `admins[]`), so `admin-add` on a `role:'client'` sub-account refuses before any store write and logs `[admin-add] op=refused-on-client reason=install-wide-access-no-seat account=<id8>`; only the house account seats admins. A standing session-manager audit (`redundant-operator-seat-audit.ts`) flags any pre-fix non-owner `AdminUser` on a client account with `[identity-audit] op=redundant-operator-seat`; removal of a flagged seat is a deliberate remediation, never automatic. See `.docs/admin-identity-surface.md`.
 
@@ -264,6 +264,7 @@ Tools are available via the `admin` MCP server.
 | Capture work as a task before implementing | User asks to "task it", create a task, or describes work that should be a task file before a sprint | `skills/task/SKILL.md` |
 | Run an insight pass on this session | Operator asks to run an insight pass, review this session, capture what we learned, or do a retrospective on the conversation | `skills/insight/SKILL.md` |
 | Summarise the last turn | User asks to summarise, recap, or give the "in short" version of what the agent just said or asked | `skills/summarise/SKILL.md` |
+| Produce a video, reel, or animation | User asks for a video, reel, MP4, animation, motion graphic, social clip, or a recording of a page playing its own animation | `skills/video-production/SKILL.md` |
 
 ## Hooks
 

package/payload/platform/plugins/admin/mcp/dist/content-producer-authoring-skills.d.ts

@@ -1,2 +1,2 @@
-export declare const CONTENT_PRODUCER_AUTHORING_SKILL_SLUGS: readonly ["professional-document", "a4-print-documents", "publish-site", "decision-memo", "narrative-builder", "property-brochure"];
+export declare const CONTENT_PRODUCER_AUTHORING_SKILL_SLUGS: readonly ["professional-document", "a4-print-documents", "publish-site", "decision-memo", "narrative-builder", "property-brochure", "video-production"];
 //# sourceMappingURL=content-producer-authoring-skills.d.ts.map

package/payload/platform/plugins/admin/mcp/dist/content-producer-authoring-skills.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"content-producer-authoring-skills.d.ts","sourceRoot":"","sources":["../src/content-producer-authoring-skills.ts"],"names":[],"mappings":"AAiCA,eAAO,MAAM,sCAAsC,qIAOzC,CAAC"}
+{"version":3,"file":"content-producer-authoring-skills.d.ts","sourceRoot":"","sources":["../src/content-producer-authoring-skills.ts"],"names":[],"mappings":"AAuCA,eAAO,MAAM,sCAAsC,yJAQzC,CAAC"}

package/payload/platform/plugins/admin/mcp/dist/content-producer-authoring-skills.js

@@ -12,6 +12,12 @@
 // generator's declaration scan already excludes them; this list is the gate's
 // compiled-in guard against a declaration regression.
 //
+// video-production is the moving-picture twin of the render skills: it drives its
+// own headless browser frame by frame and encodes with ffmpeg. It is owned for the
+// same reason as the rest — the deliverable is composed end-to-end on
+// content-producer, and an admin that authors it inline reinvents the pipeline,
+// which is exactly what happened before the skill existed (Task 2401).
+//
 // The first three are the original render/publish/print authoring skills.
 // decision-memo and narrative-builder are management-consulting prose
 // deliverables; property-brochure is the estate-agent brochure. Each is
@@ -38,5 +44,6 @@ export const CONTENT_PRODUCER_AUTHORING_SKILL_SLUGS = [
     "decision-memo",
     "narrative-builder",
     "property-brochure",
+    "video-production",
 ];
 //# sourceMappingURL=content-producer-authoring-skills.js.map

package/payload/platform/plugins/admin/mcp/dist/content-producer-authoring-skills.js.map

@@ -1 +1 @@
-{"version":3,"file":"content-producer-authoring-skills.js","sourceRoot":"","sources":["../src/content-producer-authoring-skills.ts"],"names":[],"mappings":"AAAA,6EAA6E;AAC7E,gFAAgF;AAChF,+EAA+E;AAC/E,8EAA8E;AAC9E,gFAAgF;AAChF,oDAAoD;AACpD,EAAE;AACF,wEAAwE;AACxE,4EAA4E;AAC5E,6EAA6E;AAC7E,+EAA+E;AAC/E,8EAA8E;AAC9E,sDAAsD;AACtD,EAAE;AACF,0EAA0E;AAC1E,sEAAsE;AACtE,wEAAwE;AACxE,8EAA8E;AAC9E,wEAAwE;AACxE,0EAA0E;AAC1E,EAAE;AACF,gFAAgF;AAChF,+EAA+E;AAC/E,8EAA8E;AAC9E,iFAAiF;AACjF,0EAA0E;AAC1E,EAAE;AACF,gFAAgF;AAChF,6EAA6E;AAC7E,8EAA8E;AAC9E,+EAA+E;AAC/E,iFAAiF;AACjF,iEAAiE;AACjE,MAAM,CAAC,MAAM,sCAAsC,GAAG;IACpD,uBAAuB;IACvB,oBAAoB;IACpB,cAAc;IACd,eAAe;IACf,mBAAmB;IACnB,mBAAmB;CACX,CAAC"}
+{"version":3,"file":"content-producer-authoring-skills.js","sourceRoot":"","sources":["../src/content-producer-authoring-skills.ts"],"names":[],"mappings":"AAAA,6EAA6E;AAC7E,gFAAgF;AAChF,+EAA+E;AAC/E,8EAA8E;AAC9E,gFAAgF;AAChF,oDAAoD;AACpD,EAAE;AACF,wEAAwE;AACxE,4EAA4E;AAC5E,6EAA6E;AAC7E,+EAA+E;AAC/E,8EAA8E;AAC9E,sDAAsD;AACtD,EAAE;AACF,kFAAkF;AAClF,mFAAmF;AACnF,sEAAsE;AACtE,gFAAgF;AAChF,uEAAuE;AACvE,EAAE;AACF,0EAA0E;AAC1E,sEAAsE;AACtE,wEAAwE;AACxE,8EAA8E;AAC9E,wEAAwE;AACxE,0EAA0E;AAC1E,EAAE;AACF,gFAAgF;AAChF,+EAA+E;AAC/E,8EAA8E;AAC9E,iFAAiF;AACjF,0EAA0E;AAC1E,EAAE;AACF,gFAAgF;AAChF,6EAA6E;AAC7E,8EAA8E;AAC9E,+EAA+E;AAC/E,iFAAiF;AACjF,iEAAiE;AACjE,MAAM,CAAC,MAAM,sCAAsC,GAAG;IACpD,uBAAuB;IACvB,oBAAoB;IACpB,cAAc;IACd,eAAe;IACf,mBAAmB;IACnB,mBAAmB;IACnB,kBAAkB;CACV,CAAC"}

package/payload/platform/plugins/admin/mcp/dist/index.js

@@ -32,6 +32,7 @@ import { resolveIngestToken } from "./tools/linkedin-ingest-token.js";
 import { startCpuTriage, readCpuTriage } from "./tools/cpu-triage.js";
 import { readMcpLogsByKey, readLatestMcpLog } from "./tools/logs-read-mcp.js";
 import { runCatalogueCensus } from "./lib/catalogue-census.js";
+import { runRosterCensus } from "./lib/roster-census.js";
 import { lifelineTool } from "../../../../lib/mcp-lifeline/dist/index.js";
 // Task 2130 — the same roster and the same MERGE seed-neo4j.sh runs for the
 // house account. Shared rather than reimplemented: two copies would drift, and
@@ -183,6 +184,25 @@ try {
 catch (err) {
     process.stderr.write(`[catalogue-census] error reason=${err.message}\n`);
 }
+// Task 2415 — boot-time roster census, the opposite direction to the catalogue
+// census above. Emits every specialist the admin's AGENTS.md advertises that
+// has no file in the dispatch directory. The provisioning loop used to delete
+// authored specialists and leave their roster lines standing; that deletion
+// emits no event and does not reproduce on demand, so this walk on every spawn
+// is the only surface that can see it.
+if (ACCOUNT_ID) {
+    try {
+        const accountDir = getAccountDir();
+        const roster = runRosterCensus({
+            agentsMdPath: resolve(accountDir, "agents", "admin", "AGENTS.md"),
+            specialistsAgentsDir: resolve(accountDir, "specialists", "agents"),
+        });
+        process.stderr.write(`[roster-census] declared=${roster.declared} dispatchable=${roster.dispatchable} orphaned=${roster.orphaned.join(",")}\n`);
+    }
+    catch (err) {
+        process.stderr.write(`[roster-census] error reason=${err.message}\n`);
+    }
+}
 // Entitlement input shape for the verifier. configDir is rooted under $HOME
 // (where entitlement.json is delivered post-purchase). platformRoot is needed
 // because the verifier runs in two bundle contexts (CJS dist for MCP, ESM tsup