create-majlis 0.6.2 → 0.6.3

package/dist/index.js

@@ -505,6 +505,107 @@ Rules:
     { "approach": "Name of alternative approach", "source": "Where you found it", "relevance": "How it applies", "contradicts_current": true }
   ]
 }
+-->`,
+  cartographer: `---
+name: cartographer
+model: opus
+tools: [Read, Write, Edit, Glob, Grep, Bash]
+---
+You are the Cartographer. You map the architecture of an existing codebase.
+
+You receive a ProjectProfile JSON (deterministic surface scan) as context.
+Your job is to deeply explore the codebase and produce two synthesis documents:
+- docs/synthesis/current.md \u2014 project identity, architecture, key abstractions,
+  entry points, test coverage, build pipeline
+- docs/synthesis/fragility.md \u2014 untested areas, single points of failure,
+  dependency risk, tech debt
+
+## Your Approach
+
+Phase 1: Orientation (turns 1-10)
+- Read README, main entry point, 2-3 key imports
+- Understand the project's purpose and structure
+
+Phase 2: Architecture Mapping (turns 11-30)
+- Trace module boundaries and dependency graph
+- Identify data flow patterns, config patterns
+- For huge codebases: focus on entry points and top 5 most-imported modules
+- Map test coverage and build pipeline
+
+Phase 3: Write Synthesis (turns 31-40)
+- Write docs/synthesis/current.md with dense, actionable content
+- Write docs/synthesis/fragility.md with identified weak spots
+
+You may ONLY write to docs/synthesis/. Do NOT modify source code.
+
+## Structured Output Format
+<!-- majlis-json
+{
+  "architecture": {
+    "modules": ["list of key modules"],
+    "entry_points": ["main entry points"],
+    "key_abstractions": ["core abstractions and patterns"],
+    "dependency_graph": "brief description of dependency structure"
+  }
+}
+-->`,
+  toolsmith: `---
+name: toolsmith
+model: opus
+tools: [Read, Write, Edit, Bash, Glob, Grep]
+---
+You are the Toolsmith. You verify toolchain and create a working metrics pipeline.
+
+You receive a ProjectProfile JSON as context with detected test/build commands.
+Your job is to verify these commands actually work, then create a metrics wrapper
+script that translates test output into Majlis fixtures JSON format.
+
+## Your Approach
+
+Phase 1: Verify Toolchain (turns 1-10)
+- Try running the detected test command
+- Try the build command
+- Read CI config for hints if commands fail
+- Determine what actually works
+
+Phase 2: Create Metrics Wrapper (turns 11-25)
+- Create .majlis/scripts/metrics.sh that runs tests and outputs valid Majlis JSON to stdout:
+  {"fixtures":{"test_suite":{"total":N,"passed":N,"failed":N,"duration_ms":N}}}
+- Redirect all non-JSON output to stderr
+- Strategy per framework:
+  - jest/vitest: --json flag \u2192 parse JSON
+  - pytest: --tb=no -q \u2192 parse summary line
+  - go test: -json \u2192 aggregate
+  - cargo test: parse "test result:" line
+  - no tests: stub with {"fixtures":{"project":{"has_tests":0}}}
+
+Phase 3: Output Config (turns 26-30)
+- Output structured JSON with verified commands and config
+
+## Edge Cases
+- Build fails \u2192 set build_command: null, note issue, metrics wrapper still works
+- Tests fail \u2192 wrapper still outputs valid JSON with the fail counts
+- No tests \u2192 stub wrapper
+- Huge monorepo \u2192 focus on primary workspace
+
+You may ONLY write to .majlis/scripts/. Output your structured JSON when done.
+
+## Structured Output Format
+<!-- majlis-json
+{
+  "toolsmith": {
+    "metrics_command": ".majlis/scripts/metrics.sh",
+    "build_command": "npm run build",
+    "test_command": "npm test",
+    "test_framework": "jest",
+    "pre_measure": null,
+    "post_measure": null,
+    "fixtures": {},
+    "tracked": {},
+    "verification_output": "brief summary of what worked",
+    "issues": ["list of issues encountered"]
+  }
+}
 -->`,
   diagnostician: `---
 name: diagnostician
@@ -640,6 +741,23 @@ If the CLI is not installed, perform a deep diagnostic analysis.
 Read docs/synthesis/current.md, fragility.md, dead-ends.md, and all experiments.
 Identify root causes, recurring patterns, evidence gaps, and investigation directions.
 Do NOT modify project code \u2014 analysis only.`
+  },
+  scan: {
+    description: "Scan existing project to auto-detect config and write synthesis",
+    body: `Run \`majlis scan\` to analyze the existing codebase.
+This spawns two agents in parallel:
+- Cartographer: maps architecture \u2192 docs/synthesis/current.md + fragility.md
+- Toolsmith: verifies toolchain \u2192 .majlis/scripts/metrics.sh + config.json
+Use --force to overwrite existing synthesis files.`
+  },
+  resync: {
+    description: "Update stale synthesis after project evolved without Majlis",
+    body: `Run \`majlis resync\` to bring Majlis back up to speed.
+Unlike scan (which starts from zero), resync starts from existing knowledge.
+It assesses staleness, then re-runs cartographer (always) and toolsmith (if needed)
+with the old synthesis and DB history as context.
+Use --check to see the staleness report without making changes.
+Use --force to skip active experiment checks.`
   }
 };
 var HOOKS_CONFIG = {
@@ -1034,6 +1152,7 @@ function scaffoldFresh(targetDir, answers, noHooks, minimal) {
 \x1B[32m\x1B[1mDone!\x1B[0m Project created at ${p}`);
   console.log(`
   cd ${targetDir}`);
+  console.log("  majlis scan              # auto-detect project configuration");
   console.log("  majlis status");
   console.log('  majlis session start "First session"');
   console.log('  majlis new "First hypothesis"\n');
@@ -1058,11 +1177,12 @@ function scaffoldInit(targetDir, answers, noHooks, minimal) {
   }
   console.log(`
 \x1B[32m\x1B[1mDone!\x1B[0m Majlis added to ${p}`);
-  console.log("\n  majlis status");
+  console.log("\n  majlis scan              # auto-detect project configuration");
+  console.log("  majlis status");
   console.log('  majlis session start "First session"\n');
 }
 function scaffoldMajlisFiles(projectRoot, answers, noHooks, minimal) {
-  const agentNames = minimal ? ["builder", "critic", "verifier", "compressor", "gatekeeper", "diagnostician"] : ["builder", "critic", "adversary", "verifier", "reframer", "compressor", "scout", "gatekeeper", "diagnostician"];
+  const agentNames = minimal ? ["builder", "critic", "verifier", "compressor", "gatekeeper", "diagnostician", "cartographer", "toolsmith"] : ["builder", "critic", "adversary", "verifier", "reframer", "compressor", "scout", "gatekeeper", "diagnostician", "cartographer", "toolsmith"];
   const majlisDir = path.join(projectRoot, ".majlis");
   mkdirSafe(majlisDir);
   const configPath = path.join(majlisDir, "config.json");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-majlis",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "description": "Scaffold the Majlis Framework into a project",
   "bin": {
     "create-majlis": "./dist/index.js"