@1agh/maude 0.44.0 → 0.45.1

package/cli/commands/init.mjs

@@ -6,7 +6,13 @@ import { copyTree } from '../lib/copy-tree.mjs';
 const PLACEHOLDER = 'PROJECT_NAME';
 // Files in the skeleton that contain the project-name placeholder and should
 // be templated on copy.
-const TEMPLATED = ['workflows.config.json', 'README.md', 'INDEX.md', 'release-guide.md'];
+const TEMPLATED = [
+  'workflows.config.json',
+  'README.md',
+  'INDEX.md',
+  'release-guide.md',
+  'scenario-guide.md',
+];
 
 // Per-provider command substitutions for release-guide.md. Keys map to the
 // `# CHANGELOG_PROVIDER_*_CMD` placeholders inside the skeleton's bash blocks.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@1agh/maude",
-  "version": "0.44.0",
+  "version": "0.45.1",
   "description": "Marketplace of Claude Code plugins by Michal Dovrtěl: `design` (canvas-first design iteration) + `flow` (generic agentic workflow loop with .ai second brain). Ships the `maude` CLI (with `mdcc` legacy alias) to scaffold workspace, run the design dev server, and manage configs.",
   "type": "module",
   "engines": {
@@ -51,13 +51,13 @@
     "test:e2e:desktop:acp-cold-start": "pnpm --filter @maude/desktop-e2e e2e:acp-cold-start"
   },
   "optionalDependencies": {
-    "@1agh/maude-darwin-arm64": "0.44.0",
-    "@1agh/maude-darwin-x64": "0.44.0",
-    "@1agh/maude-linux-arm64": "0.44.0",
-    "@1agh/maude-linux-arm64-musl": "0.44.0",
-    "@1agh/maude-linux-x64": "0.44.0",
-    "@1agh/maude-linux-x64-musl": "0.44.0",
-    "@1agh/maude-win32-x64": "0.44.0"
+    "@1agh/maude-darwin-arm64": "0.45.1",
+    "@1agh/maude-darwin-x64": "0.45.1",
+    "@1agh/maude-linux-arm64": "0.45.1",
+    "@1agh/maude-linux-arm64-musl": "0.45.1",
+    "@1agh/maude-linux-x64": "0.45.1",
+    "@1agh/maude-linux-x64-musl": "0.45.1",
+    "@1agh/maude-win32-x64": "0.45.1"
   },
   "files": [
     "cli",

package/plugins/flow/.claude-plugin/config.schema.json

@@ -47,6 +47,11 @@
           "type": "string",
           "description": "Root of the design plugin's canvas workspace, relative to repo root. Where flow looks for `.meta.json` sidecars + canvases when bridging to design (`/flow:plan` canvas detection, `/flow:done` handoff sweep, `codebase-intelligence` design-artifacts section). Mirrors the design plugin's own default. Flow reads this directory read-only — it never writes into the design root except the `/flow:done` handoff sweep's meta status update. Default: `.design`.",
           "default": ".design"
+        },
+        "scenarioGuide": {
+          "type": "string",
+          "description": "Repo-owned scenario-testing knowledge/deltas file that flow:scenario reads for overrides — device/platform lifecycle, selector conventions, infra-error classification, platform-specific gotchas. Mirrors `integrations.changelog.releaseGuide`'s generic-skill-plus-repo-knowledge-file shape, but optional: unlike the release guide, flow:scenario runs its documented defaults when this file is absent — no project is required to author one. Scaffolded by `maude init`. Default: `.ai/scenario-guide.md`.",
+          "default": ".ai/scenario-guide.md"
         }
       }
     },

package/plugins/flow/templates/ai-skeleton/scenario-guide.md

@@ -0,0 +1,39 @@
+# Scenario Guide — PROJECT_NAME
+
+> Read by `flow:scenario` (skill + `scenario-runner` agent) before running or authoring a scenario. This file documents ONLY where this project's scenario testing diverges from `flow:scenario`'s generic protocol — device/platform matrix, selector strategy, report shape, speed levers. An absent or empty file is valid: `flow:scenario` runs its documented defaults with no changes. Delete any section below that doesn't apply to this project; don't fill a section with a generic restatement of the default behavior.
+
+## Device / platform lifecycle
+
+> Does this project need something other than the generic default (native platforms run in parallel where the host allows it)? State the constraint and why — e.g. a RAM- or CPU-constrained CI/dev box that can only hold one simulator/emulator alive at a time forces a sequential lifecycle instead.
+
+_Not yet documented — using the generic default._
+
+## Test account & reset strategy
+
+> How does a scenario run get the app into a known state before asserting anything? If this project has a seeded test account, a fixture/profile system, or an in-app reset affordance, describe (or link to) it here. If this lives in its own skill (e.g. a dedicated test-account skill), reference it — don't duplicate its contents.
+
+_Not yet documented — using the generic default (no project-specific reset step)._
+
+## Selector strategy overrides
+
+> `flow:scenario`'s default selector reach-order is: stable locator (testID / `data-testid`) → accessible name/text → vision-based check (advisory only, never gates a pass/fail). Document here only if this project's locator convention deviates — e.g. a different testID naming scheme, a platform where accessible-name lookup is unreliable, or an additional locator tier.
+
+_Not yet documented — using the generic default._
+
+## Infra-error classification overrides
+
+> `flow:scenario`'s default treats environment/flake failures (device boot timeout, network blip, stale simulator state) as distinct from real product regressions, so they don't count as blockers. If this project binds that convention to a specific exit code or detection rule, document it here.
+
+_Not yet documented — using the generic default._
+
+## Platform-specific gotchas
+
+> A running log of harness quirks specific to this project's stack (framework cold-start races, platform dialog chains, overlay/devtools collisions, coordinate math for custom pickers, etc.). Add an entry whenever a scenario run fails for a reason that isn't a product bug — future runs (and future contributors) benefit from not re-discovering it.
+
+_None recorded yet._
+
+## Scenario-authoring notes
+
+> Anything specific to how new scenarios should be authored for this project beyond `flow:scenario`'s default collaborative loop (announce → act → screenshot → co-design asserts with the user → stop, one step at a time). E.g. project-specific `--save-script` conventions, or app areas that need special care when picking assertions.
+
+_Not yet documented — using the generic default._

package/plugins/flow/templates/ai-skeleton/scenarios/README.md

@@ -2,6 +2,8 @@
 
 Cross-platform UI scenarios. One folder per scenario; per-run reports inside.
 
+> This file documents the **directory layout** convention for individual scenarios. For *behavioral* deltas from `flow:scenario`'s generic protocol (device lifecycle, selector conventions, infra-error classification, platform gotchas), see `../scenario-guide.md` instead — the two files have distinct scopes and shouldn't be merged.
+
 ## Layout
 
 ```