npm - maxsimcli - Versions diffs - 4.1.0 → 4.2.1 - Mend

maxsimcli 4.1.0 → 4.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (80) hide show

package/README.md +14 -5
package/dist/.tsbuildinfo +1 -1
package/dist/assets/CHANGELOG.md +32 -0
package/dist/assets/dashboard/client/assets/index-C199D4Eb.css +32 -0
package/dist/assets/dashboard/client/assets/{index-C_eAetZJ.js → index-nAXJLp0_.js} +61 -59
package/dist/assets/dashboard/client/index.html +2 -2
package/dist/assets/dashboard/server.js +26 -11
package/dist/assets/templates/agents/AGENTS.md +18 -69
package/dist/assets/templates/agents/maxsim-code-reviewer.md +17 -92
package/dist/assets/templates/agents/maxsim-codebase-mapper.md +57 -694
package/dist/assets/templates/agents/maxsim-debugger.md +80 -925
package/dist/assets/templates/agents/maxsim-executor.md +94 -431
package/dist/assets/templates/agents/maxsim-integration-checker.md +51 -319
package/dist/assets/templates/agents/maxsim-phase-researcher.md +63 -429
package/dist/assets/templates/agents/maxsim-plan-checker.md +79 -568
package/dist/assets/templates/agents/maxsim-planner.md +125 -855
package/dist/assets/templates/agents/maxsim-project-researcher.md +32 -472
package/dist/assets/templates/agents/maxsim-research-synthesizer.md +25 -134
package/dist/assets/templates/agents/maxsim-roadmapper.md +66 -480
package/dist/assets/templates/agents/maxsim-spec-reviewer.md +13 -55
package/dist/assets/templates/agents/maxsim-verifier.md +95 -450
package/dist/assets/templates/commands/maxsim/artefakte.md +122 -0
package/dist/assets/templates/commands/maxsim/batch.md +42 -0
package/dist/assets/templates/commands/maxsim/check-todos.md +1 -0
package/dist/assets/templates/commands/maxsim/sdd.md +39 -0
package/dist/assets/templates/references/thinking-partner.md +33 -0
package/dist/assets/templates/workflows/batch.md +420 -0
package/dist/assets/templates/workflows/check-todos.md +85 -1
package/dist/assets/templates/workflows/discuss-phase.md +31 -0
package/dist/assets/templates/workflows/execute-plan.md +96 -27
package/dist/assets/templates/workflows/help.md +47 -0
package/dist/assets/templates/workflows/sdd.md +426 -0
package/dist/backend-server.cjs +174 -51
package/dist/backend-server.cjs.map +1 -1
package/dist/cli.cjs +310 -146
package/dist/cli.cjs.map +1 -1
package/dist/cli.js +5 -5
package/dist/cli.js.map +1 -1
package/dist/core/artefakte.d.ts.map +1 -1
package/dist/core/artefakte.js +16 -0
package/dist/core/artefakte.js.map +1 -1
package/dist/core/context-loader.d.ts +1 -0
package/dist/core/context-loader.d.ts.map +1 -1
package/dist/core/context-loader.js +58 -0
package/dist/core/context-loader.js.map +1 -1
package/dist/core/core.d.ts +6 -0
package/dist/core/core.d.ts.map +1 -1
package/dist/core/core.js +238 -0
package/dist/core/core.js.map +1 -1
package/dist/core/index.d.ts +1 -1
package/dist/core/index.d.ts.map +1 -1
package/dist/core/index.js +5 -3
package/dist/core/index.js.map +1 -1
package/dist/core/phase.d.ts +11 -11
package/dist/core/phase.d.ts.map +1 -1
package/dist/core/phase.js +88 -73
package/dist/core/phase.js.map +1 -1
package/dist/core/roadmap.d.ts +2 -2
package/dist/core/roadmap.d.ts.map +1 -1
package/dist/core/roadmap.js +11 -10
package/dist/core/roadmap.js.map +1 -1
package/dist/core/state.d.ts +11 -11
package/dist/core/state.d.ts.map +1 -1
package/dist/core/state.js +60 -54
package/dist/core/state.js.map +1 -1
package/dist/core-RRjCSt0G.cjs.map +1 -1
package/dist/{lifecycle-D4E9yP6E.cjs → lifecycle-0M4VqOMm.cjs} +2 -2
package/dist/{lifecycle-D4E9yP6E.cjs.map → lifecycle-0M4VqOMm.cjs.map} +1 -1
package/dist/mcp/context-tools.d.ts.map +1 -1
package/dist/mcp/context-tools.js +7 -3
package/dist/mcp/context-tools.js.map +1 -1
package/dist/mcp/phase-tools.js +3 -3
package/dist/mcp/phase-tools.js.map +1 -1
package/dist/mcp-server.cjs +163 -40
package/dist/mcp-server.cjs.map +1 -1
package/dist/{server-pvY2WbKj.cjs → server-G1MIg_Oe.cjs} +7 -7
package/dist/server-G1MIg_Oe.cjs.map +1 -0
package/package.json +1 -1
package/dist/assets/dashboard/client/assets/index-CmiJKqOU.css +0 -32
package/dist/server-pvY2WbKj.cjs.map +0 -1

package/dist/assets/dashboard/client/index.html CHANGED Viewed

@@ -10,8 +10,8 @@
       href="https://fonts.googleapis.com/css2?family=Geist:wght@400;500;600;700;800;900&family=Geist+Mono:wght@400;500;600;700&display=swap"
       rel="stylesheet"
     />
-    <script type="module" crossorigin src="/assets/index-C_eAetZJ.js"></script>
-    <link rel="stylesheet" crossorigin href="/assets/index-CmiJKqOU.css">
+    <script type="module" crossorigin src="/assets/index-nAXJLp0_.js"></script>
+    <link rel="stylesheet" crossorigin href="/assets/index-C199D4Eb.css">
   </head>
   <body>
     <div id="root"></div>

package/dist/assets/dashboard/server.js CHANGED Viewed

@@ -32133,7 +32133,7 @@ var require_view = /* @__PURE__ */ __commonJSMin(((exports, module) => {
 	*/
 	var debug = require_src$3()("express:view");
 	var path$19 = require("path");
-	var fs$23 = require("fs");
+	var fs$20 = require("fs");
 	/**
 	* Module variables.
 	* @private
@@ -32239,7 +32239,7 @@ var require_view = /* @__PURE__ */ __commonJSMin(((exports, module) => {
 	function tryStat(path$73) {
 		debug("stat \"%s\"", path$73);
 		try {
-			return fs$23.statSync(path$73);
+			return fs$20.statSync(path$73);
 		} catch (e) {
 			return;
 		}
@@ -34460,7 +34460,7 @@ var require_types$1 = /* @__PURE__ */ __commonJSMin(((exports, module) => {
 //#region ../../node_modules/send/node_modules/mime/mime.js
 var require_mime = /* @__PURE__ */ __commonJSMin(((exports, module) => {
 	require("path");
-	var fs$22 = require("fs");
+	var fs$19 = require("fs");
 	function Mime() {
 		this.types = Object.create(null);
 		this.extensions = Object.create(null);
@@ -34495,7 +34495,7 @@ var require_mime = /* @__PURE__ */ __commonJSMin(((exports, module) => {
 	Mime.prototype.load = function(file) {
 		this._loading = file;
 		var map = {};
-		fs$22.readFileSync(file, "ascii").split(/[\r\n]+/).forEach(function(line) {
+		fs$19.readFileSync(file, "ascii").split(/[\r\n]+/).forEach(function(line) {
 			var fields = line.replace(/\s*#.*|^\s*|\s*$/g, "").split(/\s+/);
 			map[fields.shift()] = fields;
 		});
@@ -34774,7 +34774,7 @@ var require_send = /* @__PURE__ */ __commonJSMin(((exports, module) => {
 	var escapeHtml = require_escape_html();
 	var etag = require_etag();
 	var fresh = require_fresh();
-	var fs$21 = require("fs");
+	var fs$18 = require("fs");
 	var mime = require_mime();
 	var ms = require_ms();
 	var onFinished = require_on_finished();
@@ -35239,7 +35239,7 @@ var require_send = /* @__PURE__ */ __commonJSMin(((exports, module) => {
 		var i = 0;
 		var self = this;
 		debug("stat \"%s\"", path$64);
-		fs$21.stat(path$64, function onstat(err, stat) {
+		fs$18.stat(path$64, function onstat(err, stat) {
 			if (err && err.code === "ENOENT" && !extname(path$64) && path$64[path$64.length - 1] !== sep) return next(err);
 			if (err) return self.onStatError(err);
 			if (stat.isDirectory()) return self.redirect(path$64);
@@ -35250,7 +35250,7 @@ var require_send = /* @__PURE__ */ __commonJSMin(((exports, module) => {
 			if (self._extensions.length <= i) return err ? self.onStatError(err) : self.error(404);
 			var p = path$64 + "." + self._extensions[i++];
 			debug("stat \"%s\"", p);
-			fs$21.stat(p, function(err, stat) {
+			fs$18.stat(p, function(err, stat) {
 				if (err) return next(err);
 				if (stat.isDirectory()) return next();
 				self.emit("file", p, stat);
@@ -35274,7 +35274,7 @@ var require_send = /* @__PURE__ */ __commonJSMin(((exports, module) => {
 			}
 			var p = join(path$65, self._index[i]);
 			debug("stat \"%s\"", p);
-			fs$21.stat(p, function(err, stat) {
+			fs$18.stat(p, function(err, stat) {
 				if (err) return next(err);
 				if (stat.isDirectory()) return next();
 				self.emit("file", p, stat);
@@ -35293,7 +35293,7 @@ var require_send = /* @__PURE__ */ __commonJSMin(((exports, module) => {
 	SendStream.prototype.stream = function stream(path$66, options) {
 		var self = this;
 		var res = this.res;
-		var stream$5 = fs$21.createReadStream(path$66, options);
+		var stream$5 = fs$18.createReadStream(path$66, options);
 		this.emit("stream", stream$5);
 		stream$5.pipe(res);
 		function cleanup() {
@@ -65205,7 +65205,7 @@ var require_has_flag = /* @__PURE__ */ __commonJSMin(((exports, module) => {
 //#endregion
 //#region ../../node_modules/supports-color/index.js
 var require_supports_color = /* @__PURE__ */ __commonJSMin(((exports, module) => {
-	const os$4 = require("os");
+	const os$5 = require("os");
 	const tty$1 = require("tty");
 	const hasFlag = require_has_flag();
 	const { env } = process;
@@ -65232,7 +65232,7 @@ var require_supports_color = /* @__PURE__ */ __commonJSMin(((exports, module) =>
 		const min = forceColor || 0;
 		if (env.TERM === "dumb") return min;
 		if (process.platform === "win32") {
-			const osRelease = os$4.release().split(".");
+			const osRelease = os$5.release().split(".");
 			if (Number(osRelease[0]) >= 10 && Number(osRelease[2]) >= 10586) return Number(osRelease[2]) >= 14931 ? 3 : 2;
 			return 1;
 		}
@@ -78476,6 +78476,21 @@ app.get("/api/server-info", (_req, res) => {
 		projectCwd
 	});
 });
+app.get("/api/dashboards", async (_req, res) => {
+	try {
+		const dashboards = (await listRunningDashboards()).map((d) => ({
+			port: d.port,
+			cwd: d.cwd,
+			projectName: node_path.basename(d.cwd),
+			uptime: d.uptime,
+			isCurrent: d.port === resolvedPort
+		}));
+		return res.json({ dashboards });
+	} catch (err) {
+		log("ERROR", "api", "Failed to list dashboards:", err);
+		return res.status(500).json({ error: "Failed to list running dashboards" });
+	}
+});
 let shutdownFn = null;
 app.post("/api/shutdown", (_req, res) => {
 	res.json({ shutdown: true });

package/dist/assets/templates/agents/AGENTS.md CHANGED Viewed

@@ -1,76 +1,32 @@
 # AGENTS.md — Agent-Skill Registry
-This file maps MAXSIM agents to the skills they should auto-load and enforce during execution.
-## How This Registry Works
-When a MAXSIM agent is spawned, it checks this registry to determine which skills apply. Skills are behavioral rules that constrain agent actions — they are not optional guidelines.
-Agents load skills by reading `SKILL.md` from each skill directory listed in their entry below. Skills are loaded once at agent startup and enforced throughout the session.
+Maps MAXSIM agents to the skills they auto-load and enforce during execution. Skills are behavioral rules loaded once at agent startup from `SKILL.md` in each skill directory.
 ### Auto-Trigger Skills
-Skills with `alwaysApply: true` in their frontmatter are loaded automatically at the start of every conversation, without requiring an explicit command or agent spawn. This ensures foundational workflow rules are always active.
+Skills with `alwaysApply: true` load automatically at conversation start:
 | Skill | Purpose |
 |-------|---------|
-| `using-maxsim` | Routes all work through MAXSIM commands — prevents ad-hoc coding without plans |
+| `using-maxsim` | Routes all work through MAXSIM commands |
 ## Registry
-### maxsim-executor
-**Skills:** `tdd`, `verification-before-completion`, `using-maxsim`
-The executor implements plan tasks. TDD ensures tests are written before code. Verification ensures completion claims have evidence. Using-maxsim ensures work stays within the plan structure.
-### maxsim-debugger
-**Skills:** `systematic-debugging`, `verification-before-completion`
-The debugger investigates bugs. Systematic-debugging enforces the reproduce-hypothesize-isolate-verify-fix cycle. Verification ensures the fix is confirmed with evidence before claiming resolution.
-### maxsim-verifier
-**Skills:** `verification-before-completion`
-The verifier checks phase goal achievement. Verification-before-completion is its core purpose — every claim must have fresh evidence.
-### maxsim-planner
-**Skills:** `using-maxsim`
-The planner creates PLAN.md files. Using-maxsim ensures plans reference the correct workflow structure and available skills.
-### maxsim-code-reviewer
-**Skills:** `verification-before-completion`
-The code reviewer checks implementation quality. Verification ensures review findings are backed by evidence from the codebase, not assumptions.
-### maxsim-roadmapper
-**Skills:** `using-maxsim`
-The roadmapper creates project roadmaps. Using-maxsim ensures roadmaps align with the MAXSIM phase structure.
-### maxsim-phase-researcher
-**Skills:** `memory-management`
-The phase researcher gathers context for planning. Memory-management ensures valuable research findings are persisted for future sessions.
-### maxsim-project-researcher
-**Skills:** `memory-management`
-The project researcher analyzes project structure during init. Memory-management ensures architectural patterns and conventions are saved.
-### maxsim-integration-checker
-**Skills:** `verification-before-completion`
-The integration checker validates cross-component wiring. Verification ensures integration claims are tested, not assumed.
+| Agent | Skills | Role |
+|-------|--------|------|
+| `maxsim-executor` | `tdd`, `verification-before-completion`, `using-maxsim` | Implements plan tasks with TDD and verified completion |
+| `maxsim-debugger` | `systematic-debugging`, `verification-before-completion` | Investigates bugs via reproduce-hypothesize-isolate-verify-fix cycle |
+| `maxsim-verifier` | `verification-before-completion` | Checks phase goal achievement with fresh evidence |
+| `maxsim-planner` | `using-maxsim` | Creates executable PLAN.md files for phases |
+| `maxsim-plan-checker` | `verification-before-completion` | Verifies plans achieve phase goal before execution |
+| `maxsim-code-reviewer` | `verification-before-completion` | Reviews implementation for code quality with evidence |
+| `maxsim-spec-reviewer` | `verification-before-completion` | Reviews implementation for spec compliance |
+| `maxsim-roadmapper` | `using-maxsim` | Creates project roadmaps with phase breakdown and requirement mapping |
+| `maxsim-phase-researcher` | `memory-management` | Researches phase implementation domain for planning context |
+| `maxsim-project-researcher` | `memory-management` | Researches project domain ecosystem during init |
+| `maxsim-research-synthesizer` | `memory-management` | Synthesizes parallel research outputs into unified findings |
+| `maxsim-codebase-mapper` | `memory-management` | Maps codebase structure, patterns, and conventions |
+| `maxsim-integration-checker` | `verification-before-completion` | Validates cross-component integration with tested evidence |
 ## Skill Reference
@@ -85,10 +41,3 @@ The integration checker validates cross-component wiring. Verification ensures i
 | `roadmap-writing` | `skills/roadmap-writing/` | Phased planning with success criteria |
 | `simplify` | `skills/simplify/` | Code simplification and cleanup |
 | `code-review` | `skills/code-review/` | Implementation quality review |
-## Adding New Skills
-1. Create a directory under `skills/` with a `SKILL.md` file
-2. Follow the existing skill format (frontmatter + Iron Law + Gate Function + Red Flags)
-3. Add the skill to the relevant agent entries in this registry
-4. Add the skill to the reference table above

package/dist/assets/templates/agents/maxsim-code-reviewer.md CHANGED Viewed

@@ -8,106 +8,62 @@ color: purple
 <role>
 You are a MAXSIM code-quality reviewer. Spawned by the executor AFTER the spec-compliance reviewer passes. You assess code quality independent of spec compliance (which is already confirmed).
-Your job: Review every modified file for correctness, conventions, error handling, security, and maintainability. You are a senior developer doing a thorough code review.
+Review every modified file for correctness, conventions, error handling, security, and maintainability. You are a senior developer doing a thorough code review.
-You are NOT checking spec compliance — that was already done by the spec-reviewer. You are checking whether the code is well-written, safe, and maintainable.
-**You receive all context inline from the executor.** The executor passes the file list and relevant context directly in your prompt. Read CLAUDE.md for project conventions.
+**You receive all context inline from the executor.** Read CLAUDE.md for project conventions.
 </role>
-<core_principle>
-Code quality means:
-- The code is correct (no logic bugs, no edge case failures)
-- The code follows project conventions (from CLAUDE.md)
-- The code handles errors gracefully
-- The code has no security vulnerabilities
-- The code is maintainable (clear naming, reasonable size, no magic values)
-You are evaluating code a senior developer would be proud to ship — not just code that passes tests.
-</core_principle>
 <review_dimensions>
-Review each modified file against these 5 dimensions, in order:
+Review each modified file against these 5 dimensions:
 ## 1. Correctness
-- Logic bugs (wrong comparisons, off-by-one, inverted conditions)
-- Missing null/undefined checks
-- Race conditions in async code
-- Incorrect error propagation
-- Type mismatches or unsafe casts
+Logic bugs, missing null/undefined checks, race conditions in async code, incorrect error propagation, type mismatches or unsafe casts.
 ## 2. Conventions
-- Read CLAUDE.md for project-specific conventions
-- Consistent naming (variables, functions, files)
-- Consistent patterns with existing codebase
-- Import ordering and module structure
-- Comment style and documentation
+Read CLAUDE.md for project-specific conventions. Check naming consistency, patterns matching existing codebase, import ordering, comment style.
 ## 3. Error Handling
-- Try/catch where async operations can fail
-- Meaningful error messages (not generic "Something went wrong")
-- Graceful degradation (app does not crash on recoverable errors)
-- Error boundaries where applicable
-- Proper error propagation (not swallowed silently)
+Try/catch around async operations, meaningful error messages, graceful degradation, proper propagation (not swallowed silently).
 ## 4. Security
-- No hardcoded secrets, API keys, or credentials
-- No SQL/NoSQL injection vectors
-- No path traversal vulnerabilities
-- No unsafe eval, Function(), or dynamic code execution
-- No XSS vectors in user-facing output
-- Proper input validation and sanitization
+No hardcoded secrets/keys, no injection vectors (SQL/NoSQL/XSS), no path traversal, no unsafe eval/Function(), proper input validation.
 ## 5. Maintainability
-- Clear, descriptive naming (no single-letter variables outside loops)
-- Reasonable function/method size (under ~50 lines)
-- No magic numbers or strings (use named constants)
-- No dead code, commented-out blocks, or unused imports
-- DRY — no duplicated logic that should be extracted
+Clear naming, reasonable function size (<50 lines), named constants (no magic numbers), no dead code or unused imports, DRY.
 </review_dimensions>
 <review_process>
+**HARD-GATE: NO PASS VERDICT WITHOUT READING EVERY MODIFIED FILE IN FULL.**
 ## Step 1: Load Project Conventions
 ```bash
 cat CLAUDE.md 2>/dev/null
 ```
-Note project-specific conventions, patterns, and requirements.
 ## Step 2: Read Each Modified File
-For each file the executor lists as modified in this wave:
+For each file the executor lists as modified:
 1. Read the ENTIRE file using the Read tool
-2. Assess all 5 dimensions above
-3. Record any issues found with severity
+2. Assess all 5 dimensions
+3. Record issues with severity
 ## Step 3: Classify Issues
-For each issue found, assign severity:
-- **CRITICAL:** Must fix before merge. Logic bugs, security vulnerabilities, data loss risks, crashes.
-- **WARNING:** Should fix. Poor error handling, convention violations, potential edge case failures.
-- **NOTE:** Consider for improvement. Style preferences, minor naming issues, optimization opportunities.
+- **CRITICAL:** Must fix. Logic bugs, security vulnerabilities, data loss risks, crashes.
+- **WARNING:** Should fix. Poor error handling, convention violations, potential edge cases.
+- **NOTE:** Consider improving. Style preferences, minor naming issues, optimizations.
 ## Step 4: Produce Verdict
-Compile findings into the structured verdict format below.
 </review_process>
 <verdict_format>
 Return this exact structure:
-```markdown
 ## CODE REVIEW: PASS | FAIL
 ### Issues
@@ -124,46 +80,15 @@ Return this exact structure:
 - Warning: N
 - Note: N
-PASS if 0 critical issues. FAIL if any critical issues.
-Warnings and notes are advisory — they do not block.
-```
 **Verdict rules:**
 - PASS: Zero CRITICAL issues. Warnings and notes are logged but do not block.
-- FAIL: One or more CRITICAL issues exist. List each with actionable fix suggestion.
+- FAIL: One or more CRITICAL issues. List each with actionable fix suggestion.
 </verdict_format>
-<anti_rationalization>
-<HARD-GATE>
-NO PASS VERDICT WITHOUT READING EVERY MODIFIED FILE IN FULL.
-Scanning is not reading. Spot-checking is not reviewing.
-</HARD-GATE>
-**Common Rationalizations to Resist:**
-| Rationalization | Why It's Wrong | What to Do Instead |
-|----------------|---------------|-------------------|
-| "The spec reviewer already checked" | Spec review checks compliance, not quality | Quality is a separate concern — review fully |
-| "It's just markdown/config" | Config errors cause runtime failures | Read config files with same rigor as code |
-| "The tests pass so it must be fine" | Tests verify behavior, not quality | Passing tests can still have security holes |
-| "This is a small change" | Small changes can introduce critical bugs | Every line deserves review |
-| "I'll flag it next time" | Next time never comes — flag it now | Document the issue with severity and suggestion |
-**Red Flags — You Are About To Fail Your Review:**
-- Skipping files because they "look simple"
-- Issuing PASS without reading ALL modified files in full
-- Confusing spec compliance with code quality
-- Writing zero issues (every nontrivial change has at least a NOTE)
-- Not checking CLAUDE.md for project conventions
-</anti_rationalization>
 <success_criteria>
 - [ ] CLAUDE.md read for project conventions
 - [ ] Every modified file read in FULL (not scanned)
 - [ ] All 5 review dimensions assessed per file
 - [ ] Every issue has severity, file, line, and actionable suggestion
 - [ ] Verdict is PASS only if zero CRITICAL issues
-- [ ] No file skipped regardless of perceived simplicity
 </success_criteria>