create-majlis 0.4.4 → 0.4.5

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 (2) hide show
  1. package/dist/index.js +19 -0
  2. package/package.json +1 -1
package/dist/index.js CHANGED
@@ -150,6 +150,11 @@ exist to diagnose what went wrong. The cycle comes back to you with their insigh
150
150
  - \`scripts/benchmark.py\` \u2014 the measurement tool. Never change how you're measured.
151
151
  - \`.majlis/\` \u2014 framework config. Not your concern.
152
152
 
153
+ ## Git Safety
154
+ NEVER use \`git stash\`, \`git checkout\`, \`git reset\`, or any git command that modifies
155
+ the working tree or index. The \`.majlis/majlis.db\` database is in the working tree \u2014
156
+ these commands will corrupt framework state. Use \`git diff\` and \`git show\` for read-only comparison.
157
+
153
158
  ## During building:
154
159
  - Tag EVERY decision: proof / test / strong-consensus / consensus / analogy / judgment
155
160
  - When making judgment-level decisions, state: "This is judgment \u2014 reasoning without precedent"
@@ -256,6 +261,20 @@ Reserve your final turns for writing the structured majlis-json output.
256
261
 
257
262
  The framework saves your output automatically. Do NOT attempt to write files.
258
263
 
264
+ ## Git Safety (CRITICAL)
265
+
266
+ NEVER use \`git stash\`, \`git checkout\`, \`git reset\`, or any git command that modifies
267
+ the working tree or index. The \`.majlis/majlis.db\` SQLite database is in the working tree \u2014
268
+ stashing or checking out files will corrupt it and silently break the framework's state.
269
+
270
+ To compare against baseline code, use read-only git commands:
271
+ - \`git show main:path/to/file\` \u2014 read a file as it was on main
272
+ - \`git diff main -- path/to/file\` \u2014 see what changed
273
+ - \`git log --oneline main..HEAD\` \u2014 see commits on the branch
274
+
275
+ To verify baseline metrics, run the benchmark on the CURRENT code and compare with the
276
+ documented baseline in docs/synthesis/current.md. Do NOT stash changes to re-run baseline.
277
+
259
278
  ## PROVENANCE CHECK:
260
279
  - Can every piece of code trace to an experiment or decision?
261
280
  - Is the chain unbroken from requirement -> classification -> experiment -> code?
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-majlis",
3
- "version": "0.4.4",
3
+ "version": "0.4.5",
4
4
  "description": "Scaffold the Majlis Framework into a project",
5
5
  "bin": {
6
6
  "create-majlis": "./dist/index.js"