create-majlis 0.8.0 → 0.8.2

package/dist/index.js

@@ -99,7 +99,7 @@ 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
+Do NOT read raw data files (fixtures/, ground truth, test data). The synthesis
 has the relevant facts. Reading raw data wastes turns re-deriving what the
 doubt/challenge/verify cycle already established.
 
@@ -138,7 +138,7 @@ Do NOT iterate. Do NOT "try one more thing." The adversary, critic, and verifier
 exist to diagnose what went wrong. The cycle comes back to you with their insights.
 
 ## Off-limits (DO NOT modify)
-- \`fixtures/\` \u2014 test data, ground truth, STL files. Read-only.
+- \`fixtures/\` \u2014 test data, ground truth, reference outputs. Read-only.
 - \`scripts/benchmark.py\` \u2014 the measurement tool. Never change how you're measured.
 - \`.majlis/\` \u2014 framework config. Not your concern.
 
@@ -403,15 +403,20 @@ the database export.
 2. Read docs/ files for narrative context, but trust the database when they conflict.
 3. Cross-reference: same question in different language? contradicting decisions?
    workaround masking root cause?
-4. Update fragility map: thin coverage, weak components, untested judgment
+4. **VERIFY before claiming code is live.** Dead-ended experiments are REVERTED \u2014
+   their code changes do NOT exist on the current branch. Before writing that code
+   is "live", "shipping", or "regressing", use Grep/Glob to confirm it actually
+   exists in the current codebase. If the code only existed on experiment branches,
+   say so explicitly and mark the issue as RESOLVED, not CRITICAL.
+5. Update fragility map: thin coverage, weak components, untested judgment
    decisions, broken provenance.
-5. Update dead-end registry: compress rejected experiments into structural constraints.
+6. Update dead-end registry: compress rejected experiments into structural constraints.
    Mark each dead-end as [structural] or [procedural].
-6. REWRITE synthesis using the Write tool \u2014 shorter and denser. If it's growing,
+7. REWRITE synthesis using the Write tool \u2014 shorter and denser. If it's growing,
    you're accumulating, not compressing. You MUST use the Write tool to update
    docs/synthesis/current.md, docs/synthesis/fragility.md, and docs/synthesis/dead-ends.md.
    The framework does NOT auto-save your output for these files.
-7. Review classification: new sub-types? resolved sub-types?
+8. Review classification: new sub-types? resolved sub-types?
 
 You may ONLY write to these three files:
 - docs/synthesis/current.md
@@ -716,9 +721,9 @@ falsifiable structural constraint that blocks future experiments from repeating
 ## Constraint Quality
 
 Good constraints are specific and block future repetition:
-- "L6 config space is null \u2014 13-eval Bayesian sweep found all 12 params insensitive (ls=1.27), score ceiling 0.67"
-- "Relaxing curvature split threshold in recursive_curvature_split causes false splits on pure-surface thin strips (seg_pct 95->72.5)"
-- "Torus topology prevents genus-0 assumption for manifold extraction"
+- "Binary search fallback in sortedMerge() is O(n log n) worst-case when input contains >40% duplicates \u2014 measured via 13-run sweep, ceiling 0.67x baseline"
+- "Relaxing the pruning threshold in recursiveSplit() causes false positives on sparse inputs (accuracy 95->72.5%)"
+- "Cyclic dependency in the module graph prevents topological sort \u2014 requires at least one back-edge cut"
 
 Bad constraints are vague and useless:
 - "Didn't work"

package/package.json

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