genesis-compiler 1.8.3 → 1.8.4

package/README.md

@@ -1108,3 +1108,40 @@ need no map change. Existing maps must declare their source roots. Program modul
 map and one owner even when the old map was missing or empty. If the map is missing, empty or invalid, Program inspection reports the
 required authoring work instead of assigning operations from folder names.
 Initialization creates an empty map without replacing one.
+
+## Publishing this repository
+
+The release command uses `NPM_TOKEN` in the command's environment on a local
+computer, CI runner, or hosted development environment. Supply a token with
+publishing access to the selected package. In Vibe64, save it in the project's
+**Env → Development**, enable **Secret**, and choose **Add**. Managed shell
+commands receive the saved value; credentials do not belong in source or chat.
+
+Update the selected package's version and lockfile, run the relevant checks,
+then commit and push the release source to `main`. Publish from a clean checkout
+whose `HEAD` matches `origin`'s actual `main`, with development dependencies
+installed through `npm ci`:
+
+```bash
+npm run release:npm:publish -- compiler --dry-run
+# When the catalog also changed, publish it before the compiler:
+npm run release:npm:publish -- stack
+npm run release:npm:publish -- compiler
+```
+
+Select `compiler` for `genesis-compiler` or `stack` for `genesis-stack`.
+Dry runs pack the selected source and check the registry without uploading,
+requiring a token, or requiring a clean published checkout. Real publishing
+checks npm authentication and the exact version before uploading. Matching
+releases are skipped; different contents under an existing version fail with
+the first differing file. Registry errors stop the operation. Tarball hashes
+are compared first; a different hash triggers a comparison of verified archive
+files and permissions, ignoring container timestamps and compression.
+The checked candidate tarball is the uploaded tarball. Temporary tarballs and
+private npm configuration are removed on success or failure. The command does
+not change versions or run tests. Published versions are immutable; after an
+interrupted upload, rerun the same committed release to skip matching versions.
+
+Hosted working sessions normally use a session branch. After saving or merging
+the work to `main`, publish from a separate clean clone of that published branch
+using the project's managed shell. Keep the working session on its own branch.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "genesis-compiler",
-  "version": "1.8.3",
+  "version": "1.8.4",
   "type": "module",
   "description": "An agent-independent prompt, multi-language code-index, cleanup, and verification companion with project agent guidance.",
   "repository": {
@@ -47,6 +47,7 @@
     "docs/parsers.md"
   ],
   "scripts": {
+    "release:npm:publish": "node scripts/release-npm.mjs",
     "test": "node --test --test-concurrency=1 test/*.test.js"
   },
   "dependencies": {
@@ -57,6 +58,7 @@
   },
   "devDependencies": {
     "@ast-grep/lang-python": "0.0.6",
-    "genesis-stack": "file:packages/genesis-stack"
+    "genesis-stack": "file:packages/genesis-stack",
+    "tar": "7.5.22"
   }
 }