create-majlis 0.5.1 → 0.6.0

package/dist/index.js

@@ -124,6 +124,10 @@ Read source code at the specific locations relevant to your change. Do NOT
 read the entire codebase or run diagnostic Python scripts. If the synthesis
 says "lines 1921-22" then read those lines and their context. That's it.
 
+Do NOT read raw data files (fixtures/, ground truth JSON/STL). The synthesis
+has the relevant facts. Reading raw data wastes turns re-deriving what the
+doubt/challenge/verify cycle already established.
+
 ## The Rule: ONE Change, Then Document
 
 You make ONE code change per cycle. Not two, not "one more quick fix." ONE.
@@ -320,6 +324,9 @@ documented baseline in docs/synthesis/current.md. Do NOT stash changes to re-run
 - Run at most 3-5 targeted diagnostic scripts, focused on the critical doubts/challenges.
 - Do NOT run exhaustive diagnostics on every claim.
 
+Framework-captured metrics are ground truth \u2014 if they show regression, that
+alone justifies a "rejected" grade. Do not re-derive from raw fixture data.
+
 Grade each component: sound / good / weak / rejected
 Grade each doubt/challenge: confirmed / dismissed (with evidence) / inconclusive
 
@@ -399,6 +406,13 @@ the database export.
    The framework does NOT auto-save your output for these files.
 7. Review classification: new sub-types? resolved sub-types?
 
+You may ONLY write to these three files:
+- docs/synthesis/current.md
+- docs/synthesis/fragility.md
+- docs/synthesis/dead-ends.md
+
+Do NOT modify MEMORY.md, .claude/, classification/, experiments/, or any other paths.
+
 You may NOT write code, make decisions, or run experiments.
 
 ## Structured Output Format
@@ -491,7 +505,74 @@ Rules:
     { "approach": "Name of alternative approach", "source": "Where you found it", "relevance": "How it applies", "contradicts_current": true }
   ]
 }
--->`
+-->`,
+  diagnostician: `---
+name: diagnostician
+model: opus
+tools: [Read, Write, Bash, Glob, Grep, WebSearch]
+---
+You are the Diagnostician. You perform deep project-wide analysis.
+
+You have the highest turn budget of any agent. Use it for depth, not breadth.
+Your job is pure insight \u2014 you do NOT fix code, you do NOT build, you do NOT
+make decisions. You diagnose.
+
+## What You Receive
+- Full database export: every experiment, decision, doubt, challenge, verification,
+  dead-end, metric, and compression across the entire project history
+- Current synthesis, fragility map, and dead-end registry
+- Full read access to the entire project codebase
+- Bash access to run tests, profiling, git archaeology, and analysis scripts
+
+## What You Can Do
+1. **Read everything** \u2014 source code, docs, git history, test output
+2. **Run analysis** \u2014 execute tests, profilers, git log/blame/bisect, custom scripts
+3. **Write analysis scripts** \u2014 you may write scripts ONLY to \`.majlis/scripts/\`
+4. **Search externally** \u2014 WebSearch for patterns, known issues, relevant techniques
+
+## What You CANNOT Do
+- Modify any project files outside \`.majlis/scripts/\`
+- Make code changes, fixes, or patches
+- Create experiments or make decisions
+- Write to docs/, src/, or any other project directory
+
+## Your Approach
+
+Phase 1: Orientation (turns 1-10)
+- Read the full database export in your context
+- Read synthesis, fragility, dead-ends
+- Identify patterns: recurring failures, unresolved doubts, evidence gaps
+
+Phase 2: Deep Investigation (turns 11-40)
+- Read source code at critical points identified in Phase 1
+- Run targeted tests, profiling, git archaeology
+- Write and execute analysis scripts in .majlis/scripts/
+- Cross-reference findings across experiments
+
+Phase 3: Synthesis (turns 41-60)
+- Compile findings into a diagnostic report
+- Identify root causes, not symptoms
+- Rank issues by structural impact
+- Suggest investigation directions (not fixes)
+
+## Output Format
+Produce a diagnostic report as markdown. At the end, include:
+
+<!-- majlis-json
+{
+  "diagnosis": {
+    "root_causes": ["List of identified root causes"],
+    "patterns": ["Recurring patterns across experiments"],
+    "evidence_gaps": ["What we don't know but should"],
+    "investigation_directions": ["Suggested directions for next experiments"]
+  }
+}
+-->
+
+## Safety Reminders
+- You are READ-ONLY for project code. Write ONLY to .majlis/scripts/.
+- Focus on diagnosis, not fixing. Your value is insight, not implementation.
+- Trust the database export over docs/ files when they conflict.`
 };
 var COMMANDS = {
   classify: {
@@ -551,6 +632,14 @@ Produce a rihla document at docs/rihla/.`
 If the CLI is not installed, review: original objective, current classification,
 recent failures, dead-ends. Ask: is the classification serving the objective?
 Would we decompose differently with what we now know?`
+  },
+  diagnose: {
+    description: "Deep project-wide diagnostic analysis",
+    body: `Run \`majlis diagnose $ARGUMENTS\` for deep diagnosis.
+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.`
   }
 };
 var HOOKS_CONFIG = {
@@ -973,7 +1062,7 @@ function scaffoldInit(targetDir, answers, noHooks, minimal) {
   console.log('  majlis session start "First session"\n');
 }
 function scaffoldMajlisFiles(projectRoot, answers, noHooks, minimal) {
-  const agentNames = minimal ? ["builder", "critic", "verifier", "compressor", "gatekeeper"] : ["builder", "critic", "adversary", "verifier", "reframer", "compressor", "scout", "gatekeeper"];
+  const agentNames = minimal ? ["builder", "critic", "verifier", "compressor", "gatekeeper", "diagnostician"] : ["builder", "critic", "adversary", "verifier", "reframer", "compressor", "scout", "gatekeeper", "diagnostician"];
   const majlisDir = path.join(projectRoot, ".majlis");
   mkdirSafe(majlisDir);
   const configPath = path.join(majlisDir, "config.json");
@@ -1030,7 +1119,8 @@ ${cmd.body}
     "verification",
     "reframes",
     "rihla",
-    "synthesis"
+    "synthesis",
+    "diagnosis"
   ];
   for (const dir of docDirs) {
     mkdirSafe(path.join(docsDir, dir));

package/package.json

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