@goodfoot/git-mesh 1.0.77 → 1.0.80

package/bin/git-mesh.exe

@@ -0,0 +1,6 @@
+@goodfoot/git-mesh placeholder. scripts/postinstall.js replaces this file
+with the native binary for your platform. The name ends in .exe and the
+first line intentionally has NO "#!" shebang so npm/yarn/pnpm cmd-shim
+generates a direct-exec wrapper that runs on Windows; Unix ignores the
+.exe suffix and execs by mode bit. If you are seeing this text, the
+postinstall step did not run.

package/man/git-mesh.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH git-mesh 1  "git-mesh 1.0.77" 
+.TH git-mesh 1  "git-mesh 1.0.80" 
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
 .SH NAME
@@ -8,7 +8,7 @@ git\-mesh \- Track implicit semantic dependencies in a git repo.
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
 .SH SYNOPSIS
-\fBgit\-mesh\fR [\fB\-\-perf\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] [\fIsubcommands\fR]
+\fBgit\-mesh\fR [\fB\-\-perf\fR] [\fB\-\-mesh\-dir\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] [\fIsubcommands\fR]
 .SH DESCRIPTION
 .B git mesh
 tracks implicit semantic dependencies in a Git repository: couplings between
@@ -45,18 +45,18 @@ If the relationship has changed, update the why with
 .B git mesh why
 before re-anchoring.
 .PP
-Meshes are stored in a catalog tree at
-.IR refs/meshes/v1/catalog
-as individual entries using a zero-copy archive format,
-so they travel with
-.B git fetch
-and
-.B git push
-like branches and tags.
-.B git mesh fetch
-and
-.B git mesh push
-keep remote mirrors in sync.
+Each mesh is an ordinary tracked file under the mesh root (default
+.IR .mesh ,
+overridable with
+.BR \-\-mesh\-dir ,
+the
+.I GIT_MESH_DIR
+environment variable, or
+.IR "git config git-mesh.dir" ).
+Meshes are versioned, fetched, and pushed exactly like any other
+tracked file \[em] stage and commit edits with
+.B git add .mesh && git commit
+\&.
 .PP
 Bare invocations:
 .RS 4
@@ -76,6 +76,9 @@ Emit performance timings for major git\-mesh operation groups to stderr.
 
 Can also be enabled with `GIT_MESH_PERF=1`.
 .TP
+\fB\-\-mesh\-dir\fR \fI<MESH_DIR>\fR
+Mesh root directory (default: .mesh). Overrides GIT_MESH_DIR and git config git\-mesh.dir
+.TP
 \fB\-h\fR, \fB\-\-help\fR
 Print help (see a summary with \*(Aq\-h\*(Aq)
 .TP
@@ -85,6 +88,9 @@ Print version
 .el .ds Aq '
 .SH SUBCOMMANDS
 .TP
+git\-mesh\-show(1)
+Show the named mesh — its anchors, why, and config. Equivalent to the bare `git mesh <name>` positional form
+.TP
 git\-mesh\-list(1)
 List files and anchors currently tracked by a mesh
 .TP
@@ -92,56 +98,32 @@ git\-mesh\-stale(1)
 Report anchors whose content has drifted from their anchored state
 .TP
 git\-mesh\-add(1)
-Stage anchors to add on the next mesh commit
+Add anchors to a mesh, writing the mesh file under the mesh root. Stage and commit the change with `git add .mesh && git commit`
 .TP
 git\-mesh\-remove(1)
-Stage anchors to remove on the next mesh commit
+Remove anchors from a mesh, editing the mesh file under the mesh root. Stage and commit the change with `git add .mesh && git commit`
 .TP
 git\-mesh\-why(1)
 Read or stage the mesh\*(Aqs why — a one\-sentence definition of the subsystem, flow, or concern the anchors collectively form
 .TP
-git\-mesh\-commit(1)
-Resolve staged operations and write a mesh commit
-.TP
-git\-mesh\-restore(1)
-Clear the staging area
-.TP
-git\-mesh\-revert(1)
-Fast\-forward a mesh to a past state
-.TP
 git\-mesh\-delete(1)
 Delete a mesh
 .TP
 git\-mesh\-move(1)
 Rename a mesh
 .TP
-git\-mesh\-config(1)
-Read or stage mesh\-level resolver options
-.TP
-git\-mesh\-fetch(1)
-Fetch mesh and anchor refs from a remote
-.TP
-git\-mesh\-push(1)
-Push mesh and anchor refs to a remote
-.TP
 git\-mesh\-doctor(1)
 Audit the local mesh setup
 .TP
-git\-mesh\-hooks(1)
-Git hook shortcuts (post\-commit, post\-rewrite)
-.TP
 git\-mesh\-advice(1)
 Append events and flush session\-scoped advice
 .TP
-git\-mesh\-rewrite(1)
-Advance anchor SHAs after a history rewrite (post\-rewrite hook)
-.TP
 git\-mesh\-help(1)
 Print this message or the help of the given subcommand(s)
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
 .SH VERSION
-v1.0.77
+v1.0.80
 .SH EXAMPLES
 Anchor a new mesh alongside a code change:
 .PP
@@ -152,8 +134,8 @@ git mesh add billing/charge-request-contract \e
 git mesh why billing/charge-request-contract \e
     -m "The doc states the request body shape the parser honors; \e
 the doc is the source of truth when they disagree."
+git add .mesh
 git commit -m "Wire checkout to charge API"
-# post-commit hook runs: git mesh commit
 .fi
 .RE
 .PP
@@ -166,7 +148,7 @@ git mesh add auth/token-contract --at HEAD \e
     packages/auth/crypto.ts#L12-L40
 git mesh why auth/token-contract \e
     -m "Token verification depends on signature verification."
-git mesh commit auth/token-contract
+git add .mesh && git commit -m "Document token/crypto coupling"
 .fi
 .RE
 .PP
@@ -176,7 +158,7 @@ Check for drift and inspect a mesh:
 .nf
 git mesh stale
 git mesh billing/charge-request-contract
-git mesh billing/charge-request-contract --log
+git mesh show billing/charge-request-contract
 .fi
 .RE
 .SH SEE ALSO

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@goodfoot/git-mesh",
-  "version": "1.0.77",
-  "bin": "bin/git-mesh",
+  "version": "1.0.80",
+  "bin": "bin/git-mesh.exe",
   "man": [
     "man/git-mesh.1"
   ],
@@ -18,16 +18,16 @@
     "udeps": "bash scripts/cleanup-stale-target.sh && env CARGO_TARGET_DIR=\"${GIT_MESH_CARGO_TARGET_ROOT:-./target-cache}/udeps\" cargo +nightly udeps"
   },
   "files": [
-    "bin/",
+    "bin/git-mesh.exe",
     "man/",
     "scripts/postinstall.js"
   ],
   "optionalDependencies": {
-    "@goodfoot/git-mesh-darwin-arm64": "1.0.77",
-    "@goodfoot/git-mesh-darwin-x64": "1.0.77",
-    "@goodfoot/git-mesh-linux-arm64": "1.0.77",
-    "@goodfoot/git-mesh-linux-x64": "1.0.77",
-    "@goodfoot/git-mesh-win32-x64": "1.0.77"
+    "@goodfoot/git-mesh-darwin-arm64": "1.0.80",
+    "@goodfoot/git-mesh-darwin-x64": "1.0.80",
+    "@goodfoot/git-mesh-linux-arm64": "1.0.80",
+    "@goodfoot/git-mesh-linux-x64": "1.0.80",
+    "@goodfoot/git-mesh-win32-x64": "1.0.80"
   },
   "repository": {
     "type": "git",

package/scripts/postinstall.js

@@ -99,35 +99,44 @@ function main() {
     buildFromSource(sourceBinary, sourceBinaryName);
   }
 
-  // Install the native binary at the single `bin` path npm wrapped. The
-  // committed placeholder has no shebang, so npm/yarn/pnpm generated
-  // direct-exec wrappers pointing here; replacing it in place makes them run
-  // the real binary. Extensionless on every platform — Windows CreateProcess
-  // executes a valid PE by explicit path regardless of extension.
-  const binGitMesh = path.join(__dirname, '..', 'bin', 'git-mesh');
-
+  // Always write to bin/git-mesh.exe — the package.json `bin` field points
+  // here on every platform. The `.exe` extension plus a no-shebang stub makes
+  // npm's cmd-shim (generated at install time, before this postinstall) emit
+  // a direct exec on Windows; Unix executes by mode bit + ELF/Mach-O header
+  // and ignores the `.exe` suffix entirely. No resident Node process — the
+  // `git-mesh` command execs the native binary directly. Same pattern as
+  // Bun's and Claude Code's npm packages.
+  const binGitMesh = path.join(__dirname, '..', 'bin', 'git-mesh.exe');
+
+  // Hardlink first (instant, zero extra disk for the ~16MB binary; src and
+  // dest are both under node_modules so same-filesystem is the common case),
+  // then fall back to copy across devices / on link-permission errors.
   try {
-    fs.unlinkSync(binGitMesh);
-  } catch (error) {
-    if (error.code !== 'ENOENT') {
-      fail(`@goodfoot/git-mesh: Could not remove existing binary at ${binGitMesh}.`, error);
-    }
-  }
-
-  // Try symlink first, fall back to copy
-  try {
-    fs.symlinkSync(sourceBinary, binGitMesh);
-  } catch (symlinkError) {
-    try {
+    fs.linkSync(sourceBinary, binGitMesh);
+  } catch (linkError) {
+    if (linkError.code === 'EEXIST') {
+      try {
+        fs.unlinkSync(binGitMesh);
+        fs.linkSync(sourceBinary, binGitMesh);
+      } catch {
+        fs.copyFileSync(sourceBinary, binGitMesh);
+      }
+    } else if (linkError.code === 'EXDEV' || linkError.code === 'EPERM') {
       fs.copyFileSync(sourceBinary, binGitMesh);
-      fs.chmodSync(binGitMesh, 0o755);
-    } catch (copyError) {
-      fail(
-        `@goodfoot/git-mesh: Could not install binary from ${sourceBinary} to ${binGitMesh}.`,
-        new Error(`symlink failed: ${symlinkError.message}\ncopy failed: ${copyError.message}`)
-      );
+    } else {
+      try {
+        fs.copyFileSync(sourceBinary, binGitMesh);
+      } catch (copyError) {
+        fail(
+          `@goodfoot/git-mesh: Could not install binary from ${sourceBinary} to ${binGitMesh}.`,
+          new Error(`link failed: ${linkError.message}\ncopy failed: ${copyError.message}`)
+        );
+      }
     }
   }
+  if (process.platform !== 'win32') {
+    fs.chmodSync(binGitMesh, 0o755);
+  }
 
   console.log(`@goodfoot/git-mesh: Installed git-mesh from ${packageName}`);
 }

package/bin/git-mesh

@@ -1,5 +0,0 @@
-@goodfoot/git-mesh placeholder. This file is replaced by scripts/postinstall.js
-with the native binary for your platform. Its first line intentionally has NO
-"#!" shebang so npm/yarn/pnpm cmd-shim generates direct-exec .cmd/.ps1/sh
-wrappers (no /bin/sh, no node) that run the native binary installed here.
-If you are seeing this text executed, the postinstall step did not run.