create-majlis 0.3.2 → 0.4.0

package/dist/index.js

@@ -121,8 +121,9 @@ You get ONE attempt per cycle. Your job is:
 2. Form ONE hypothesis about what to fix
 3. Implement ONE focused change (not a multi-step debug session)
 4. Run the benchmark ONCE to see the result
-5. Document what you did, what happened, and what you think the next step should be
-6. STOP
+5. Update the experiment doc in docs/experiments/ \u2014 fill in Approach, Results, and Metrics sections. This is NOT optional.
+6. Output the structured majlis-json block with your decisions
+7. STOP
 
 Do NOT iterate. Do NOT try multiple approaches. Do NOT debug your own fix.
 If your change doesn't work, document why and let the cycle continue \u2014
@@ -217,21 +218,28 @@ tools: [Read, Glob, Grep, Bash]
 ---
 You are the Verifier. Perform dual verification:
 
-PROVENANCE CHECK:
+## Scope Constraint (CRITICAL)
+
+You must produce your structured output (grades + doubt resolutions) within your turn budget.
+Do NOT exhaustively test every doubt and challenge \u2014 prioritize the critical ones.
+For each doubt/challenge: one targeted check is enough. Confirm, dismiss, or mark inconclusive.
+Reserve your final turns for writing the structured majlis-json output.
+
+The framework saves your output automatically. Do NOT attempt to write files.
+
+## PROVENANCE CHECK:
 - Can every piece of code trace to an experiment or decision?
 - Is the chain unbroken from requirement -> classification -> experiment -> code?
 - Flag any broken chains.
 
-CONTENT CHECK:
+## CONTENT CHECK:
 - Does the code do what the experiment log says?
-- Do tests demonstrate the hypothesis?
-- Write and run targeted tests against the critic's doubts AND the adversary's cases.
+- Run at most 3-5 targeted diagnostic scripts, focused on the critical doubts/challenges.
+- Do NOT run exhaustive diagnostics on every claim.
 
 Grade each component: sound / good / weak / rejected
 Grade each doubt/challenge: confirmed / dismissed (with evidence) / inconclusive
 
-Produce your verification report as output. The framework saves it automatically.
-
 ## Structured Output Format
 <!-- majlis-json
 {

package/package.json

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