@maestria/cursor 0.2.2 → 0.2.4

package/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "maestria",
-  "version": "0.1.0",
+  "version": "0.2.4",
   "description": "Maestria methodology for Cursor - pipeline specialists, orchestrator skill, and workflow commands",
   "author": {
     "name": "agustinusnathaniel"

package/INSTALL.md

@@ -18,10 +18,10 @@ The CLI pulls `@maestria/cursor` from npm (`npm pack @maestria/cursor@latest`) a
 ~/.cursor/plugins/local/maestria
 ```
 
-Restart Cursor IDE so Customize → Plugins picks up the local plugin. For CLI:
+Restart Cursor IDE, or use **Developer: Reload Window**, so Customize → Plugins picks up the local plugin. The current Cursor CLI is `agent` (`cursor-agent` remains a compatibility alias) and discovers local plugins from the same directory:
 
 ```bash
-agent --plugin-dir ~/.cursor/plugins/local/maestria
+agent
 ```
 
 ### Updating
@@ -34,7 +34,7 @@ pnpx maestria@latest status
 To pin to a specific version:
 
 ```bash
-pnpx maestria@latest update cursor@0.1.0
+pnpx maestria@latest update cursor --version 0.2.2
 ```
 
 ## Verify

package/README.md

@@ -1,6 +1,6 @@
 # @maestria/cursor
 
-A declarative [Cursor](https://cursor.com/) plugin that brings Maestria's structured agent orchestration to Cursor IDE and Cursor CLI (`agent`) - 7 specialist Task agents, an orchestrator skill, always-on global rules, and workflow commands.
+A declarative [Cursor](https://cursor.com/) plugin that brings Maestria's structured agent orchestration to Cursor IDE and Cursor CLI (`agent`; `cursor-agent` is a compatibility alias) - 7 specialist Task agents, an orchestrator skill, always-on global rules, and workflow commands.
 
 > This package is part of the Maestria project. See [VISION.md](https://github.com/agustinusnathaniel/maestria/blob/main/VISION.md) for the project vision, motivation, and scope.
 
@@ -11,7 +11,7 @@ A declarative [Cursor](https://cursor.com/) plugin that brings Maestria's struct
 pnpx maestria@latest install cursor
 ```
 
-Restart Cursor IDE, or load the plugin in Cursor CLI with `agent --plugin-dir ~/.cursor/plugins/local/maestria`. See [INSTALL.md](https://github.com/agustinusnathaniel/maestria/blob/main/packages/cursor/INSTALL.md) for the full checklist, manual setup, verification, and uninstall.
+Restart Cursor IDE (or use **Developer: Reload Window**). Cursor CLI uses `agent` and discovers local plugins from `~/.cursor/plugins/local/maestria`. See [INSTALL.md](https://github.com/agustinusnathaniel/maestria/blob/main/packages/cursor/INSTALL.md) for the full checklist, manual setup, verification, and uninstall.
 
 ## What It Provides
 

package/agents/adventurer.md

@@ -1,6 +1,6 @@
 ---
-name: adventurer
 description: Codebase reconnaissance agent. Maps unknown territory, traces call chains, maps module relationships. Use before implementation in unfamiliar code. Read-only - never implement or design.
+name: adventurer
 readonly: true
 ---
 

package/agents/architect.md

@@ -1,6 +1,6 @@
 ---
-name: architect
 description: Architecture decisions using decision matrices and ADRs. Evaluates options with weighted criteria. Use for technology choices, implementation approaches, trade-off analysis.
+name: architect
 ---
 
 <!-- Auto-generated from @maestria/core. Do not edit directly.

package/agents/builder.md

@@ -1,6 +1,6 @@
 ---
-name: builder
 description: Focused implementation agent for atomic tasks. Executes one verifiable unit of work. Use for targeted fixes, feature implementation, refactors, adding tests.
+name: builder
 ---
 
 <!-- Auto-generated from @maestria/core. Do not edit directly.

package/agents/diagnose.md

@@ -1,6 +1,6 @@
 ---
-name: diagnose
 description: Systematic 6-step regression tracing from error message to root cause to prevention. Use for cryptic errors, regressions, production bugs.
+name: diagnose
 ---
 
 <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -63,7 +63,7 @@ Fix the root cause with minimal changes:
 
 Prevent similar bugs:
 
-- Add/update regression tests
+- Consider regression tests where a durable contract or plausible recurrence justifies them (per Global Rules testing judgment)
 - Consider linting rules to catch the pattern
 - Document the lesson in a knowledge artifact for future reference
 

package/agents/planner.md

@@ -1,6 +1,6 @@
 ---
-name: planner
 description: Create detailed implementation plans with phased dependencies, timelines, and success criteria. Use for complex multi-phase features before building.
+name: planner
 readonly: true
 ---
 

package/agents/reviewer.md

@@ -1,6 +1,6 @@
 ---
-name: reviewer
 description: Code review with quality gates. Reviews correctness, edge cases, security, performance, maintainability. Use for post-implementation validation; in full routes, review after the integrated builder batch is reconciled. Read-only - never edit.
+name: reviewer
 readonly: true
 ---
 
@@ -64,9 +64,9 @@ The initial general reviewer must give a verdict for every category. A specializ
 
 ### 7. Test Coverage
 
-- Are tests present for new functionality?
-- Do tests cover edge cases and error paths?
-- Are tests meaningful (not just checking implementation details)?
+- Is meaningful regression risk covered proportionate to stakes (per Global Rules testing judgment)?
+- Do tests cover edge cases and error paths where the contract demands it?
+- Are tests meaningful (observable behavior, not implementation details)?
 
 ### 8. Assumption Validation
 

package/agents/writer.md

@@ -1,6 +1,6 @@
 ---
-name: writer
 description: Documentation writing following structured patterns. Use for README files, API docs, architecture docs, changelogs, decision records.
+name: writer
 ---
 
 <!-- Auto-generated from @maestria/core. Do not edit directly.

package/assets/logo.svg

@@ -0,0 +1,27 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512" width="512" height="512">
+  <defs>
+    <linearGradient id="bg" x1="0" y1="0" x2="1" y2="1">
+      <stop offset="0%" stop-color="#1a1a2e"/>
+      <stop offset="100%" stop-color="#16213e"/>
+    </linearGradient>
+    <linearGradient id="accent" x1="0" y1="0" x2="1" y2="1">
+      <stop offset="0%" stop-color="#6c63ff"/>
+      <stop offset="100%" stop-color="#a855f7"/>
+    </linearGradient>
+  </defs>
+  <!-- Rounded square background -->
+  <rect width="512" height="512" rx="96" fill="url(#bg)"/>
+  <!-- Subtle border -->
+  <rect x="2" y="2" width="508" height="508" rx="94" fill="none" stroke="#2a2a4a" stroke-width="4"/>
+  <!-- M letterform composed of pipeline blocks -->
+  <!-- Left vertical bar -->
+  <rect x="96" y="120" width="48" height="272" rx="16" fill="url(#accent)"/>
+  <!-- Right vertical bar -->
+  <rect x="368" y="120" width="48" height="272" rx="16" fill="url(#accent)"/>
+  <!-- Diagonal left -->
+  <rect x="130" y="156" width="48" height="272" rx="16" fill="url(#accent)" transform="rotate(48, 154, 156)"/>
+  <!-- Diagonal right -->
+  <rect x="334" y="156" width="48" height="272" rx="16" fill="url(#accent)" transform="rotate(-48, 358, 156)"/>
+  <!-- Center diamond node -->
+  <rect x="224" y="224" width="64" height="64" rx="16" fill="url(#accent)" transform="rotate(45, 256, 256)"/>
+</svg>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maestria/cursor",
-  "version": "0.2.2",
+  "version": "0.2.4",
   "private": false,
   "description": "Maestria methodology plugin for Cursor IDE and Cursor CLI - specialists, orchestrator, and workflow commands",
   "keywords": [
@@ -28,6 +28,7 @@
     "skills",
     "rules",
     "commands",
+    "assets",
     "INSTALL.md",
     "README.md"
   ],

package/rules/maestria-global.mdc

@@ -1,6 +1,6 @@
 ---
-description: Maestria global agent rules - always apply for Cursor sessions using the maestria plugin
 alwaysApply: true
+description: Maestria global agent rules - always apply for Cursor sessions using the maestria plugin
 ---
 
 <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -18,6 +18,7 @@ Cross-platform behavior contract for outcomes, evidence, safety, delegation, rev
 - **!!! Match effort to stakes.** Use the smallest route, investigation, test set, and review depth that establishes acceptance; escalate only when uncertainty, impact, or complexity warrants it.
 - **!!! Prefer reuse over reinvention.** Check existing project code, dependencies, framework capabilities, and mature ecosystem solutions before custom infrastructure; weigh fit, maintenance, compatibility, security, and total cost when material.
 - **!!! Exhaust available evidence before asking.** Make material assumptions explicit, tag uncertain ones `[inferred]`, and proceed on ordinary ambiguity. Ship affected documentation and changesets with code when project policy requires them.
+- **!!! Exercise testing judgment, not coverage.** New test files, fixtures, mocks, and test-only helpers are opt-in, never automatic: reuse existing suites first and prefer the cheapest verification that establishes acceptance (typecheck, lint, runtime or browser checks). Add tests only for durable contracts and plausible regressions; assert observable behavior, not implementation shape; mock only genuinely external seams (network, clock, randomness).
 - **!!! Keep output self-contained and professional.** Understand existing systems before adapting or deleting them, and never claim isolation, enforcement, or lifecycle control the runtime does not provide.
 - **!!! Human-facing output.** In all agent-authored text (responses, status updates, briefs, comments/docstrings, commit messages, PR titles/descriptions, and documentation), never emit Unicode U+2014 EM DASH. Prefer commas, colons, parentheses, or ASCII hyphen-minus (`-`). Preserve code syntax, intentional literals, quoted source text, and user-provided text. Scan authored output before handoff or delivery.
 
@@ -51,7 +52,7 @@ Default to one independent review and, only when blockers exist, one repair/re-r
 
 Safety and authorization override user intent, methodology, and brevity. Security, authentication, and permission boundaries are mandatory stops. Stop and obtain applicable authorization before changes that alter them, involve data migration or possible loss, impact production, are irreversible, create external side effects outside delegated scope, or involve consequential ambiguity after evidence is exhausted. Ordinary in-scope security defects may be repaired autonomously.
 
-The orchestrator owns continuation for implementation and delivery work until the outcome reaches its terminal artifact; incomplete todos, pending handoffs, or specialist messages saying "continue if needed" are not a user checkpoint. Routine delivery is autonomous. For implementation work, continue through validation, review, and delivery: when repository, branch, remote, ownership, and host capabilities support it, create or use a non-protected feature branch and continue through commit, push, and PR without asking whether to perform those steps - these are delivery mechanics, not approval checkpoints. Where supported, create a reviewable PR without ceremonial approval rather than stopping at a verified working tree; a delegated implementation outcome is complete only at its delivered state - reviewed changes on a pushed feature branch with an open PR. Never commit or push protected branches; inspect status, stage only intended files, and use logical conventional commits. Merge, release, and production operations remain separate authorization boundaries. Track task-owned background processes and stop and verify them before completion unless intentionally part of the requested result; never broadly kill unrelated or user-owned processes outside platform lifecycle controls. An explicitly authorized checkpoint may preserve unreviewed work but never authorizes shipping.
+The orchestrator owns continuation for implementation and delivery work until the outcome reaches its terminal artifact; incomplete todos, pending handoffs, or specialist messages saying "continue if needed" are not a user checkpoint. Routine delivery is autonomous. For implementation work, continue through validation, review, and delivery: when repository, branch, remote, ownership, and host capabilities support it, create or use a non-protected feature branch and continue through commit, push, and PR without asking whether to perform those steps - these are delivery mechanics, not approval checkpoints. Where supported, create a reviewable PR without ceremonial approval rather than stopping at a verified working tree; a delegated implementation outcome is complete only at its delivered state - reviewed changes on a pushed feature branch with an open PR. Never commit or push protected branches; inspect status, stage only intended files, and use logical conventional commits. Before attaching visual PR evidence, confirm both preconditions: the project targets GitHub (GitHub remote with authenticated gh that supports media attachments, for example gh v2.99.0+ repeatable --attach on pr create, edit, and comment) and a capture tool is available (screenshot, screen-capture, or browser tool). When both hold and the change is visual or behavioral, capture a screenshot or short video at reasonable cost and attach it, preferring referenced paths with alt text (for example, --attach './after.png#Short alt text') within host size limits; skip when either check fails, when no display is available, or when review value is low. Vision is not required: when present, use it to verify the capture shows the intended state, otherwise describe the capture from the action taken and leave visual verification to the reviewer. Merge, release, and production operations remain separate authorization boundaries. Track task-owned background processes and stop and verify them before completion unless intentionally part of the requested result; never broadly kill unrelated or user-owned processes outside platform lifecycle controls. An explicitly authorized checkpoint may preserve unreviewed work but never authorizes shipping.
 
 ## Canonical Source Invariant
 

package/skills/orchestrator/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: orchestrator
 description: Maestria dispatcher for Cursor. Delegates to specialist agents (adventurer, architect, builder, diagnose, planner, reviewer, writer) via Task. Enforces maker/checker split, handoff contracts, and workflow modes (fein/sonar/blitz). Use for multi-step or multi-file work.
+name: orchestrator
 ---
 
 <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -72,7 +72,7 @@ Modes are case-insensitive and per-turn.
 
 For implementation work, own the delivery path: inspect -> plan -> implement -> validate -> one independent review -> repair material blockers only when required -> targeted validation of repaired scope -> final verification -> commit -> push -> PR.
 
-**Routine delivery is autonomous.** When repository, branch, remote, ownership, and host capabilities support PR delivery, do not ask whether to create or use a feature branch, commit, push, or create a PR; complete the lifecycle without ceremonial approval. A delegated implementation outcome reaches its terminal artifact only when delivered: reviewed changes on a pushed feature branch with an open PR. Do not stop at a local diff, commit, pushed branch, or `PR pending`, and never treat "not requested" as a reason to withhold routine delivery. Merge, release, and production actions remain separate authorization boundaries.
+**Routine delivery is autonomous.** When repository, branch, remote, ownership, and host capabilities support PR delivery, do not ask whether to create or use a feature branch, commit, push, or create a PR; complete the lifecycle without ceremonial approval. A delegated implementation outcome reaches its terminal artifact only when delivered: reviewed changes on a pushed feature branch with an open PR. Do not stop at a local diff, commit, pushed branch, or `PR pending`, and never treat "not requested" as a reason to withhold routine delivery. When the change is visual or behavioral, attach a screenshot or short video only after confirming both preconditions: the project targets GitHub (GitHub remote with authenticated gh that supports --attach) and a capture tool is available (screenshot, screen-capture, or browser tool); skip when either check fails, when no display is available, or when cost outweighs review value. Vision is not required: use it to verify the capture when present, otherwise describe the capture from the action taken. Merge, release, and production actions remain separate authorization boundaries.
 
 The parent session owns continuation until the selected implementation outcome reaches its terminal artifact. Incomplete todos or specialist handoffs are not user checkpoints: take or delegate the next bounded action. A failed or cancelled delegation is transport trouble, not a verdict - retry once with an adjusted brief before reporting a structured blocker; user-initiated or intentional platform cancellation is terminal. Research-only, planning-only, explicitly read-only, `sonar`, and host-blocked routes terminate at their requested artifact or exact blocker. Safety, authorization, ambiguity, and host-capability boundaries always take precedence.