@topy-ai/maggie 0.7.54 → 0.7.55

package/README-zh-TW.md

@@ -29,27 +29,27 @@ npx @topy-ai/maggie init --scope project --agent all
 npx @topy-ai/maggie doctor --scope project --project .
 ```
 
-目前 npm 版本為 `0.7.54`：完成 feedback batch 30，共 13 條 feedback，來自一個在自家網站上執行 MaggieDash 的內容與社群產品，並同步發布 MaggieDash 0.2.14。
-
-- **MaggieDash 先裝核心**：`maggie dash install` 現在只安裝儀表板、登入、`/_maggie/admin` 路由與核心資料表。接著讀取專案（框架、既有登入、資料庫、金流、是否提供服務或經營 Blog、語言），逐項推薦選配模組並說明原因。沒有你的指示不會安裝任何選配：`maggie dash add booking --confirm`（或 `maggie booking install`）。純內容網站不再被裝上 Stripe、預約路由與 worker。`maggie dash recommend` 可隨時重新分析。
-- **MaggieDash 0.2.14 不再把密鑰寫進 build**：Astro scaffold 以 `import.meta.env` 讀取伺服器設定，Vite 會把它寫進建置輸出；只要 build 時環境中有 `DATABASE_URL` 或 `BOOKING_TOKEN_SECRET`，就會出現在 `dist/server`。現在改為執行時讀取，用舊 scaffold 安裝的 host 請重新 build。管理介面側欄只顯示 host 實際提供的面板（capability manifest）；從 GitHub 安裝時也會拿到 Booking 的 env 範例檔。
-- **agent 資料夾不再有特定客戶的文件**：舊版會把某個客戶的整合稽核、進度記錄與交付看板裝進 `~/.claude/references` 與 `~/.codex/references`。現在只打包一般性的 Booking 文件。打包時若有檔案提到客戶，或連到沒有打包的文件，release gate 會直接失敗。`maggie update` 會移除舊版裝了、新版不再提供、且你沒改過的檔案；`maggie doctor --scope user` 會列出剩下的。
-- **Feedback 一定送得到**：`maggie feedback submit` 不需要 `--endpoint`。先送 NoBlox；只有在該主機儲存前失敗（連不上或 526 之類的 5xx）才改送 `feedback.cmo.so`，兩邊都以 `feedbackId` 去重。
-- **社群貼文**：
-  - `link-check`（及 `plan --check-link`）在規劃貼文前排除連結已失效（404／410）的文章；被擋或暫時出錯的頁面會保留。
-  - `pictures` 確保同一個點子寫給多個頻道的貼文共用同一張圖。
-- **Blog API Pull**：`maggie blog live-urls` 記錄已交付文章的實際上線網址（來自網站回報或 sitemap 比對）。比對只會新增、不會撤回先前的結果，且優先採用原文頁而不是翻譯頁。
-- **大量產生的頁面**：
-  - `maggie design bulk` 用同一份 brief、facts 與 validator 產生大量相似頁面：只替已通過驗證、之後沒再改過的頁面畫圖；頁面被改過，寫手必須重新讀取；規則收緊時，先前通過的頁面會退回重新驗證；所有頁面都通過才寫入。
-  - `maggie localization key-check` 找出需要「每頁位置 key」而不能共用文字 key 的翻譯。
-  - `maggie localization fragments` 找出被品牌名切成太短、無法單獨翻譯的片段。
-- **圖片**：`maggie media generate --engine codex|gemini` 產生圖片；`maggie media engine-plan` 在大量產生前列出各引擎的時間與費用（例如 2400x1000 在 Gemini 會用 21:9、2K）。
-- **App**：
-  - `maggie design sheet-check` 抓出 iOS 凍結問題：關閉 sheet 的同時顯示 toast、重新整理、換頁或開另一個 sheet。
-  - `maggie mobile ota-guard` 只把更新發佈到已安裝 build 擁有的 runtime；在 pnpm monorepo 中，fingerprint 可能因不相關的套件變動而改變。
-- **發佈**：
-  - `maggie deployment preview-auth-check` 找出仍在送資料到已加密碼的 preview 主機的 workflow 與 webhook。
-  - `maggie product published` 等到 staged 的 npm 版本真正成為 `latest`。
+目前 npm 版本為 `0.7.55`：完成 feedback batch 31，共 16 條，來自一個以排程 AI agent 操作自家行銷產品、同時維護 PHP 主機的團隊，並同步發布 MaggieDash 0.2.15。
+
+- **排程 agent（`maggie-ops`）**：
+  - Skill 的「Routine mode」範本：何時執行、讀什麼、可確認哪些寫入與每日上限、失敗時怎麼辦，最後一定存一份報告。排程規則：排在伺服器自己的工作之後、避開整點，並留在平台每日執行次數上限內。
+  - `maggie ops routines-check routines.json` 依上述規則檢查 routines 檔；`maggie ops routines-payload` 產生 agents repository 送給 MaggieDash Routines 分頁的內容。
+  - Ops Autopilot 模式：每日例行工作在伺服器上以網站當地時間、每個週期只跑一次，絕不重發可能已上線的內容；agent 先讀它的狀態，只補上判斷。
+- **AI 助理工具（`maggie-assistant-tools`）**：
+  - 報告收件匣：每次無人值守的執行都在這裡留下結果（存、列、讀；每站每日上限；標題、摘要與內文視為不可信）。`maggie assistant report-check` 檢查報告。
+  - 限制由伺服器執行：agent key 的長期工具要有每日數量；登入（OAuth）連線能用到的每個寫入工具都要有每日上限。登入連線預設取得該角色的完整工具集，縮小時必須說明原因。
+  - 會截短文字的列表工具，每一筆都要標示已截短，並指名能取得全文的 get 工具。`maggie assistant list-check` 找出看起來被截斷的項目。
+- **PHP 主機與安全公告（`maggie-deployment`）**：
+  - `maggie deployment runtime-inventory` 從 `nginx -T`（包含 symlink 到 `sites-enabled` 的設定）列出每個網站的 PHP runtime，標出已停止支援的作業系統與過舊的固定 image 版本，並為每個受影響的網站產生遷移計畫：綁在 127.0.0.1 的容器、唯讀掛載網站、nginx 變更、啟動後檢查與回復步驟。
+  - PHP image 一律以 `--entrypoint docker-php-entrypoint` 啟動。`wordpress:*-fpm` 的預設 entrypoint 會把 WordPress 複製進沒有 `wp-config.php` 的掛載目錄。
+  - `maggie deployment host-lock` 避免兩個 agent session 同時修改同一台主機，並列出最近的變更。
+- **Blog API Pull**：改寫內容現在會送到 pull 網站：讀取 `/updates`，新內文套用到它所屬的文章（依原始 content id、slug 或網址），並保留上線網址。`live-urls match` 也會補上網址為空的已追蹤文章。
+- **Search Console 點子**：`maggie seo query-ideas` 不會把 `site:` 查詢、單純網域或只有品牌名的查詢變成點子，單複數視為同一主題。
+- **社群佇列**：`maggie tool maggie_social_share.py used-on` / `queue-check`：同一篇文章在某個頻道分享後 30 天內不會在該頻道重用（其他頻道不受影響）；每則貼文都要有圖片；自動模式下選配檢查不再擋住貼文；「全部核准」包含被擋住的貼文。
+- **單一版本來源**：`VERSION` 與 `package.json` 不一致時拒絕打包，發佈前會檢查所有 release 文件，`maggie skills package` 必須明確指定版本來源。
+- **MaggieDash 0.2.15** 新增 AI agents 工作區，管理 host 自己的 MCP：附工具與每日上限的 token、登入連線、逐次呼叫復原、Google 分析連線，以及同步的 routines。
+
+前一版 `0.7.54` 完成 feedback batch 30（13 條，來自在自家網站執行 MaggieDash 的內容與社群產品）：MaggieDash 先裝核心、release privacy gate、feedback 備援到 `feedback.cmo.so`、社群 `link-check` 與 `pictures`、`blog live-urls`、`design bulk`、`sheet-check`、`media generate`、`mobile ota-guard`、`preview-auth-check` 與 `product published`。
 
 前一版 `0.7.53` 完成 feedback batch 29（56 條，來自預約平台與社群／AI 助理產品）：預約規則與共用測試向量、Stripe Connect 平台指引與 `connect-qa`、MaggieDash 0.2.13 預約修正、`cloudflare-preflight`、`vps-release`、`qa fit-check`、`mobile ota --build-ref`、助理 registry 卡片與長期核准、社群只用自家網域文章，以及 `seo origin-check`。
 
@@ -137,7 +137,7 @@ structure drift 或重複 treatment product 時 fail closed。
 deployment、memory、feedback 和 MaggieDash。內容先 draft/review，外部寫入、
 publish 與 production deployment 需要明確確認。
 
-目前 npm 版本為 `0.7.54`，包含 batch 30 MaggieDash 先裝核心、release privacy gate、feedback 備援、社群連結與圖片檢查、大量頁面產生與 app 檢查，batch 29 預約規則、部署、app QA、助理與社群功能，以及 batch 28 產品 app、assistant tools、mobile、product release、skills catalog 與 bridge host 功能、batch 26、27 feedback 修正與 idempotent `maggie update`與 Booking email-template 合約/CLI validator 同步。本版完成 2026-09-24 booking feedback batch：Calendar grid/free-slot entry 與 host modal focus-restoration evidence。本版新增 Starter marketplace provisioning plan；本版完成 feedback batches 22、23：加入 declarative browser interaction evidence、design markup/style/content-key gate、compiler source anchoring、entity double-escape protection、`update --help` read-only、noindex hypothetical indexability、可過期 baseline acknowledgement、DOM-only link extraction regression，以及 MaggieDash 0.2.10 的 content override、短期 browser session、CDN-safe public-session cache contracts。authentication 和 isolated dev server 仍由 host 負責。`maggie-booking` workflow、傳統 email/password、Stripe、Resend、public booking flow 及既有安全邊界維持不變；provider-bound video generation 與 transactional delivery 仍記錄在 issue #39，前一批延後功能仍在 issue #38，不會直接成為 active memory。0.7.33 記錄並審查一筆更正回饋；確認 0.7.32 已正確處理 batch index，沒有修改已驗證的 shared behavior。0.7.32 加入 feedback 一基索引支援、MaggieDash panel 的 source/freshness/error evidence、Consent Mode 與實際 write/no-op reconciliation、SEO baseline recapture、sitemap origin rebasing、content-diff scope、migration ledger reconciliation、deployment credential preflight、release provenance/runtime preflight、icon release gate、opt-in blog auto-publish gate，以及 least-privilege VPS deployer。也修復 top-level `maggie feedback` dispatcher parity。0.7.31 加入 update 差異摘要、atomic installer copy、subset install manifest merge，以及 inventory drift 時 doctor non-zero。0.7.30 補上 feedback tracking issue closeout gate 與 batch 14/15 audit ledger。0.7.29 修正 npm package landing page 使用英文 README；0.7.28 加入 versioned Gemini model policy、明確 fallback 與 provenance、bundled-first CLI
+目前 npm 版本為 `0.7.55`，包含 batch 31 排程 agent routines、報告收件匣與無人值守 agent 限制、PHP runtime 盤點與主機鎖、pull 網站改寫、query 點子與社群佇列檢查，batch 30 MaggieDash 先裝核心、release privacy gate、feedback 備援、社群連結與圖片檢查、大量頁面產生與 app 檢查，batch 29 預約規則、部署、app QA、助理與社群功能，以及 batch 28 產品 app、assistant tools、mobile、product release、skills catalog 與 bridge host 功能、batch 26、27 feedback 修正與 idempotent `maggie update`與 Booking email-template 合約/CLI validator 同步。本版完成 2026-09-24 booking feedback batch：Calendar grid/free-slot entry 與 host modal focus-restoration evidence。本版新增 Starter marketplace provisioning plan；本版完成 feedback batches 22、23：加入 declarative browser interaction evidence、design markup/style/content-key gate、compiler source anchoring、entity double-escape protection、`update --help` read-only、noindex hypothetical indexability、可過期 baseline acknowledgement、DOM-only link extraction regression，以及 MaggieDash 0.2.10 的 content override、短期 browser session、CDN-safe public-session cache contracts。authentication 和 isolated dev server 仍由 host 負責。`maggie-booking` workflow、傳統 email/password、Stripe、Resend、public booking flow 及既有安全邊界維持不變；provider-bound video generation 與 transactional delivery 仍記錄在 issue #39，前一批延後功能仍在 issue #38，不會直接成為 active memory。0.7.33 記錄並審查一筆更正回饋；確認 0.7.32 已正確處理 batch index，沒有修改已驗證的 shared behavior。0.7.32 加入 feedback 一基索引支援、MaggieDash panel 的 source/freshness/error evidence、Consent Mode 與實際 write/no-op reconciliation、SEO baseline recapture、sitemap origin rebasing、content-diff scope、migration ledger reconciliation、deployment credential preflight、release provenance/runtime preflight、icon release gate、opt-in blog auto-publish gate，以及 least-privilege VPS deployer。也修復 top-level `maggie feedback` dispatcher parity。0.7.31 加入 update 差異摘要、atomic installer copy、subset install manifest merge，以及 inventory drift 時 doctor non-zero。0.7.30 補上 feedback tracking issue closeout gate 與 batch 14/15 audit ledger。0.7.29 修正 npm package landing page 使用英文 README；0.7.28 加入 versioned Gemini model policy、明確 fallback 與 provenance、bundled-first CLI
 dispatch、`maggie --version`、feedback batch review 聚合與重複偵測、marketplace enrichment evidence、booking
 worker/resolver evidence，以及 read-only migration preflight。它也包含 host-owned mobile app surface contract、signed-in
 camera-state QA、直接 Astro route resolution、correlated feedback batch，以及

package/README.md

@@ -89,71 +89,66 @@ Maggie keeps the existing project foundation and asks for decisions before
 shared routes, analytics, or publishing boundaries change. The current
 package ships 22 installable skills and a local-first MaggieDash foundation.
 
-This package is `0.7.54`. It closes feedback batch 30: 13 records
-from a content and social product that runs MaggieDash on its own website,
-plus MaggieDash 0.2.14.
-
-- **MaggieDash installs the core first.** `maggie dash install` now installs
-  only the dashboard, sign-in, the `/_maggie/admin` route and the core schema.
-  It then reads your project (framework, existing sign-in, database, payments,
-  whether you sell services or run a blog, languages) and recommends optional
-  modules, each with a reason. Nothing optional is installed until you ask:
-  `maggie dash add booking --confirm` (or `maggie booking install`). A content
-  site no longer gets Stripe, booking routes and a worker it never asked for.
-  `maggie dash recommend` repeats the analysis at any time.
-- **MaggieDash 0.2.14 keeps secrets out of the build.** The Astro scaffold
-  read server settings through `import.meta.env`, which Vite writes into the
-  build output: an `astro build` with `DATABASE_URL` or `BOOKING_TOKEN_SECRET`
-  in the environment put them into `dist/server`. They are now read at run
-  time. Rebuild any host installed from an earlier scaffold. The admin
-  sidebar shows only the panels your host serves (capability manifest), and
-  the Booking env example now reaches installs from GitHub.
-- **Nothing client-specific in your agent folders.** Earlier packages
-  installed one client's integration audit, progress logs and a delivery
-  board into `~/.claude/references` and `~/.codex/references`. Only general
-  Booking documents ship now. A release gate fails packaging when a packaged
-  file names a client or links to an unshipped document. `maggie update`
-  removes files an older package installed and this one no longer ships
-  (only when you have not changed them), and `maggie doctor --scope user`
-  reports any that are left.
-- **Feedback always arrives.** `maggie feedback submit` needs no
-  `--endpoint`. It tries the NoBlox host first and, only when that host fails
-  before storing the draft (no connection or a 5xx such as 526), sends it to
-  `feedback.cmo.so`. Both hosts drop duplicates by `feedbackId`.
-- **Social posts.**
-  - `link-check` (and `plan --check-link`) drops articles whose link is gone
-    (404 or 410) before posts are planned. Blocked or failing pages are kept.
-  - `pictures` makes posts written together for several channels share one
-    picture.
-- **Blog API Pull.** `maggie blog live-urls` records where a delivered post
-  went live, from the site's own report or a sitemap match. Matching only
-  adds URLs, never retires earlier matches, and prefers the original page
-  over translated copies.
-- **Generated pages.**
-  - `maggie design bulk` runs many similar pages from one brief, facts file
-    and validator. Pictures are drawn only for validated pages that have not
-    changed since. A writer must re-read a page that changed. Tightened rules
-    send earlier passes back for validation. Nothing is seeded until every
-    page passes.
-  - `maggie localization key-check` finds texts that need per-page position
-    keys instead of site-wide text keys.
-  - `maggie localization fragments` finds sentences split around a brand
-    name into pieces too short to translate.
-- **Pictures.** `maggie media generate --engine codex|gemini` draws a picture,
-  and `maggie media engine-plan` states the time and cost of each engine
-  before a large run (for example, 2400x1000 becomes 21:9 at 2K on Gemini).
-- **Apps.**
-  - `maggie design sheet-check` catches the iOS freeze: closing a sheet and,
-    in the same moment, showing a toast, refreshing, navigating or opening
-    another sheet.
-  - `maggie mobile ota-guard` publishes an update only to a runtime an
-    installed build has. In pnpm monorepos the fingerprint can move with
-    unrelated dependency changes.
-- **Releases.**
-  - `maggie deployment preview-auth-check` finds workflows and webhooks that
-    still post to a preview host you protected with a password.
-  - `maggie product published` waits until a staged npm version is really
-    `latest`.
+This package is `0.7.55`. It closes feedback batch 31: 16 records from a team that runs scheduled AI
+agents against its own marketing product and maintains PHP hosts, plus
+MaggieDash 0.2.15.
+
+- **Scheduled agents (`maggie-ops`).**
+  - A "Routine mode" template for skills: when it runs, what it reads, which
+    writes it may confirm and how many a day, what to do on failure, and that
+    it ends by saving a report. Scheduling rules: start after the server's own
+    jobs and off the hour, and stay inside the platform's daily run cap.
+  - `maggie ops routines-check routines.json` checks a routines file against
+    those rules. `maggie ops routines-payload` builds the body an agents
+    repository sends to MaggieDash's Routines tab.
+  - The Ops Autopilot pattern: daily chores run on the server, once per
+    period, in the site's local time, and never repost something that may
+    already be live. Agents read its state first and add judgement.
+- **AI assistant tools (`maggie-assistant-tools`).**
+  - A report inbox where every unattended run leaves its result (save, list,
+    get; daily cap per site; title, summary and body treated as untrusted).
+    `maggie assistant report-check` checks a report.
+  - Limits are the server's: agent keys get standing tools with a daily
+    number, and every write a sign-in (OAuth) connection can reach needs a
+    daily cap. A sign-in connection gets the role's whole tool set unless the
+    narrowing is stated.
+  - A list tool that shortens text must say so on each item and name a get
+    tool that returns the full text. `maggie assistant list-check` finds
+    items that look cut off.
+- **PHP hosts and advisories (`maggie-deployment`).**
+  - `maggie deployment runtime-inventory` lists each site's PHP runtime from
+    `nginx -T` (symlinked `sites-enabled` files included), flags end-of-life
+    operating systems and stale pinned images, and writes a migration plan
+    per affected site: a container on 127.0.0.1, the site mounted read-only,
+    the nginx change, checks after start and a rollback.
+  - PHP images always start with `--entrypoint docker-php-entrypoint`. The
+    `wordpress:*-fpm` default entrypoint copies WordPress into a mounted site
+    that has no `wp-config.php`.
+  - `maggie deployment host-lock` stops two agent sessions from changing the
+    same host at once and shows what changed recently.
+- **Blog API Pull.** Rewrites now reach pull-delivered sites: `/updates` is
+  read, the new body lands on the post it belongs to (by its original content
+  id, slug or address) and keeps its live URL. `live-urls match` also fills
+  posts tracked with an empty URL.
+- **Search Console ideas.** `maggie seo query-ideas` never turns `site:`
+  queries, bare domains or the brand name alone into ideas, and treats
+  singular and plural as one topic.
+- **Social queue.** `maggie tool maggie_social_share.py used-on` / `queue-check`: an article
+  shared on a channel is not reused there for 30 days (other channels stay
+  free); every post needs a picture; in auto mode optional checks no longer
+  hold posts; Approve all includes held posts.
+- **One version source.** Packaging refuses when `VERSION` and
+  `package.json` disagree, publishing checks every release document, and
+  `maggie skills package` needs an explicit version source.
+- **MaggieDash 0.2.15** adds the AI agents workspace for a host's own MCP:
+  tokens with tools and a daily limit, sign-in connections, per-call undo,
+  Google analytics connection and synced routines.
+
+0.7.54 closed feedback batch 30 (13 records from a content and social product
+running MaggieDash): core-first `maggie dash install`, the release privacy
+gate, feedback fallback to `feedback.cmo.so`, social `link-check` and
+`pictures`, `blog live-urls`, `design bulk`, `sheet-check`, `media generate`,
+`mobile ota-guard`, `preview-auth-check` and `product published`.
 
 0.7.53 closed feedback batch 29 (56 records from a booking marketplace and a
 social/assistant product): booking rules with shared test vectors, Stripe
@@ -815,8 +810,8 @@ artifact schemas.
 Recommended upgrade sequence for the current release:
 
 ```bash
-npx @topy-ai/maggie@0.7.54 update --scope project --project . --force
-npx @topy-ai/maggie@0.7.54 cleanup --scope project --project .
+npx @topy-ai/maggie@0.7.55 update --scope project --project . --force
+npx @topy-ai/maggie@0.7.55 cleanup --scope project --project .
 ```
 
 Maintainers should pass npm credentials through the repository helper, never

package/bin/maggie.js

@@ -105,6 +105,7 @@ Usage:
   maggie seo privacy-check --evidence FILE
   maggie seo origin-check --base-url URL [--project PATH] [--expect-host HOST]
   maggie seo fragment-check --url URL [--url URL2] [--cookie-env NAME]
+  maggie seo query-ideas ROWS.json [--coverage FILE] [--brand NAME] [--limit 5]
   maggie content FILE --source PROVIDER --project PATH --confirm
   maggie agent-content write --url URL --allowed-origin ORIGIN --token-env ENV --payload FILE
   maggie bootstrap phase <start|pass|fail|status> <phase> [project]
@@ -172,12 +173,16 @@ Usage:
   maggie deployment file-parity --host H [--host H2] --root /srv/app/current --path dist/x.mjs [--ref DEPLOYED_COMMIT]
   maggie deployment warm-check --url URL [--warm 3] [--samples 5] [--budget-ms 800]
   maggie deployment preview-auth-check --host preview.example.com [--repo PATH] [--live]
+  maggie deployment runtime-inventory --evidence FILE|--ssh USER@HOST|--print-collector [--advisory FILE] [--latest-tags FILE] [--image php:{version}-fpm]
+  maggie deployment host-lock acquire|status|release --host USER@HOST|local --session ID [--purpose TEXT] [--ttl 3600]
   maggie deployment vps-release --host deploy@HOST --release-root /srv/app --service app --env-file /etc/app.env [--health-url URL] [--confirm]
   maggie mobile preflight|plan --project PATH [--app-dir apps/app] [--profile production] [--platform ios|android|all] [--auto-submit] [--build-ref REF]
   maggie mobile ota --project PATH --build-ref REF --build-id ID --message TEXT [--confirm]
   maggie mobile ota-guard --project PATH --platform ios|android --runtimes FILE [--publish --message TEXT --confirm]
   maggie assistant registry-validate|annotations|capability-page|audit-check --registry FILE [--mcp-tools FILE] [--session FILE] [--output FILE]
   maggie assistant approval-selftest
+  maggie assistant list-check --registry FILE --tool NAME --result FILE
+  maggie assistant report-check --report FILE [--registry FILE]
   maggie product release-check --package DIR [--server-json FILE] [--changelog FILE] [--pack]
   maggie product smoke --package DIR | mcp-check --mcp-url URL | review-status --reviews FILE [--chatgpt-plugin FILE]
   maggie product published --package-name NAME --version X [--wait 600] [--publish-log FILE]
@@ -220,6 +225,8 @@ Usage:
   maggie ops google-ads-preflight|google-ads-keyword-ideas --customer-id ID [--login-customer-id ID]
   maggie ops notifications catalogue|templates|preflight|health|retention|alerts --project PATH ...
   maggie ops preflight --project PATH --write
+  maggie ops routines-check routines.json [--server-jobs FILE] [--plan pro|max|team|enterprise]
+  maggie ops routines-payload routines.json --repo OWNER/NAME [--commit SHA] [--output FILE]
 
 Examples:
   npx @topy-ai/maggie init
@@ -675,10 +682,10 @@ function docs(args) {
 
 function seo(args) {
   const command = args[0];
-  const scripts = { performance: "maggie_performance.py", images: "maggie_images.py", sitemap: "maggie_sitemap.py", indexnow: "maggie_indexnow.py", "social-cards": "maggie_social_cards.py", "head-tags": "maggie_head_tags.py" };
+  const scripts = { performance: "maggie_performance.py", images: "maggie_images.py", sitemap: "maggie_sitemap.py", indexnow: "maggie_indexnow.py", "social-cards": "maggie_social_cards.py", "head-tags": "maggie_head_tags.py", "query-ideas": "maggie_query_ideas.py" };
   if (command === "privacy-check") return workflowCli("maggie_contracts.py", ["privacy-check", ...args.slice(1)]);
   if (command === "origin-check" || command === "fragment-check") return workflowCli("maggie_seo_routes.py", args);
-  if (!scripts[command]) throw new Error("seo command must be performance, images, sitemap, indexnow, social-cards, head-tags, privacy-check, origin-check, or fragment-check");
+  if (!scripts[command]) throw new Error("seo command must be performance, images, sitemap, indexnow, social-cards, head-tags, query-ideas, privacy-check, origin-check, or fragment-check");
   workflowCli(scripts[command], args.slice(1));
 }
 
@@ -855,6 +862,7 @@ try {
   else if (command === "deployment" && args[0] === "collect") workflowCli("maggie_deployment_collect.py", args.slice(1));
   else if (command === "deployment" && args[0] === "parity") workflowCli("maggie_deployment_parity.py", args.slice(1));
   else if (command === "deployment" && args[0] === "release-manifest") workflowCli("maggie_release_manifest.py", args.slice(1));
+  else if (command === "deployment" && ["runtime-inventory", "host-lock"].includes(args[0])) workflowCli("maggie_host_runtime.py", args);
   else if (command === "deployment" && args[0] === "runtime-preflight") workflowCli("maggie_runtime_preflight.py", args.slice(1));
   else if (command === "deployment") workflowCli("maggie_deployment.py", args);
   else if (command === "migration") workflowCli("maggie_migration.py", args);

package/bundled-contracts/maggie-assistant-tools/booking-receptionist-example-v1.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": "maggie-assistant-tool-registry.v1",
-  "description": "Booking receptionist and public discovery MCP for a multi-business booking marketplace. The receptionist answers visitors on one business's page from that business's facts only; it never books, cancels or takes card details \u2014 it opens the normal booking sheet at a real free time.",
+  "description": "Booking receptionist and public discovery MCP for a multi-business booking marketplace. The receptionist answers visitors on one business's page from that business's facts only; it never books, cancels or takes card details — it opens the normal booking sheet at a real free time.",
   "visitorPolicy": {
     "enabledByDefault": false,
     "dailyCaps": {
@@ -157,5 +157,21 @@
       "text": "Give medical advice.",
       "instead": "Ask the business, or your doctor."
     }
-  ]
+  ],
+  "unattended": {
+    "enforcedBy": "server",
+    "agentKeys": {
+      "canConfirmPreviews": false,
+      "refusalReturnsReason": true,
+      "standingTools": {}
+    },
+    "oauth": {
+      "server": "owner",
+      "defaultTools": "role",
+      "dailyWriteLimit": 100,
+      "perToolPerDay": {
+        "booking_reschedule": 20
+      }
+    }
+  }
 }

package/bundled-contracts/maggie-assistant-tools/report-v1.schema.json

@@ -0,0 +1,43 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://github.com/TOPY-AI-LTD/ai-cmo-skills/blob/main/contracts/maggie-assistant-tools/report-v1.schema.json",
+  "title": "Maggie assistant report",
+  "description": "A report a scheduled agent (or the server's own job) leaves in a website's report inbox. Agents end every run by saving one. Checked before saving with `maggie assistant report-check`.",
+  "type": "object",
+  "required": [
+    "title",
+    "summary"
+  ],
+  "properties": {
+    "schemaVersion": {
+      "const": "maggie-assistant-report.v1"
+    },
+    "kind": {
+      "type": "string",
+      "description": "e.g. weekly, daily_ops, agent, post_health"
+    },
+    "title": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 120
+    },
+    "summary": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 500,
+      "description": "One or two sentences shown in the inbox and the push."
+    },
+    "body_md": {
+      "type": "string",
+      "maxLength": 50000
+    },
+    "data": {
+      "type": "object"
+    },
+    "source": {
+      "type": "string",
+      "description": "system:<job> or agent:<key or grant id>; set by the server, never by the caller."
+    }
+  },
+  "additionalProperties": false
+}