@topy-ai/maggie 0.7.19 → 0.7.20

package/README.md

@@ -305,8 +305,8 @@ artifact schemas.
 Recommended upgrade sequence for the current release:
 
 ```bash
-npx @topy-ai/maggie@0.7.19 update --project . --force
-npx @topy-ai/maggie@0.7.19 cleanup --project .
+npx @topy-ai/maggie@0.7.20 update --project . --force
+npx @topy-ai/maggie@0.7.20 cleanup --project .
 ```
 
 Maintainers should pass npm credentials through the repository helper, never
@@ -316,7 +316,9 @@ as a command-line argument:
 node scripts/publish-npm.mjs --maggie-env-file ../.env
 ```
 
-The 0.7.19 workflow adds documentation hygiene audits, live URL API contract
+The 0.7.20 workflow completes the MaggieDash Activity and Navigation
+workspaces and dashboard UI v3 contract. The 0.7.19 workflow adds
+documentation hygiene audits, live URL API contract
 validation, host-supplied schema reader audits, dashboard runtime evidence,
 and provider-neutral activity-log and managed-navigation contracts. The 0.7.18
 workflow adds staged/untracked changed-surface detection, scenario

package/README.zh-TW.md

@@ -8,7 +8,7 @@ Codex、Claude Code 與相容的 coding agents。
 ## 安裝
 
 ```bash
-npx @topy-ai/maggie@0.7.19 init --agent all
+npx @topy-ai/maggie@0.7.20 init --agent all
 npx @topy-ai/maggie doctor --project .
 ```
 
@@ -25,7 +25,8 @@ maggie doctor --project . --require-bootstrap --strict
 deployment、memory、feedback 和 MaggieDash。內容先 draft/review，外部寫入、
 publish 與 production deployment 需要明確確認。
 
-0.7.19 加入文件 hygiene audit、live URL API contract、schema reader audit、
+0.7.20 完成 MaggieDash Activity 與 Navigation workspace，以及 dashboard UI v3
+contract。0.7.19 加入文件 hygiene audit、live URL API contract、schema reader audit、
 dashboard runtime evidence，以及 activity-log 和 managed-navigation contracts。
 0.7.18 加入 staged/untracked changed-surface release gate、QA run 與 release
 整合、market/locale-aware service variant route、provider capability matrix

package/bundled-contracts/maggiedash/README.md

@@ -61,6 +61,12 @@ Dashboard browser checks must emit runtime evidence; a static component scan
 or JSON declaration is not proof that a screen mounted or that its data calls
 ran.
 
+The first-party MaggieDash 0.2.4 distribution exposes these adapters through
+its dashboard UI v3 contract: a read-only Activity workspace and an atomic,
+locale-aware Navigation workspace. The reusable UI accepts the standard
+`events`/`occurredAt` and `items`/`destination` shapes, while also reading the
+legacy host response aliases used by existing adapters during migration.
+
 ## Status model
 
 Content transitions are explicit:

package/bundled-skills/maggie-dash/SKILL.md

@@ -46,6 +46,15 @@ owns the framework route, email/password session middleware, database, media
 storage, provider credentials, and `/api/maggie/*` adapter endpoints. Read the
 MaggieDash host adapter contract before adding a new framework adapter.
 
+MaggieDash 0.2.4 adds two reusable operator workspaces. Activity is a read-only
+view backed by `/api/maggie/activity.json`; it supports actor/action filters,
+refresh, and a safe unavailable state. Navigation is an ordered,
+locale/location-aware editor backed by `/api/maggie/navigation.json`; it saves
+the full menu atomically and requires the host to keep published markup as its
+fallback. The host owns authentication, event writes, menu persistence,
+translation behavior, and validation. Use the dashboard UI v3 contract for the
+required route and capability declarations.
+
 For a built/deployed host, an agent must use the host's validated content
 bridge rather than editing release files or receiving database credentials:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@topy-ai/maggie",
-  "version": "0.7.19",
+  "version": "0.7.20",
   "description": "Install and manage Maggie Skills for AI coding agents",
   "license": "MIT",
   "type": "module",