@marktiderman/genesis 0.4.0 → 0.4.2

package/README.md

@@ -81,3 +81,42 @@ A child that runs `genesis-sync.sh` during that window stamps the new harness co
 with that previous version number. Nothing is silently lost: `GENESIS_SOURCE_SHA` (git
 HEAD) is always exact and is the precise pointer; only the human-readable coordinate can
 lag by one release until the "version packages" PR merges.
+
+## Installing the harness alongside the umbrella
+
+Installing `@marktiderman/genesis` gives you the DS packages over npm. The **agent harness**
+(hooks, skills, the belt CLI, the plugin) is a git-native surface that rides your repo's own
+history rather than `node_modules` — so it is *vendored*, not imported. Because the umbrella's
+version is the single coordinate, you bootstrap the matching harness in one command, keyed to the
+umbrella you just pinned:
+
+```bash
+npm i @marktiderman/genesis        # (or pnpm/bun/yarn add) — the version you pin is the coordinate
+
+# `@marktiderman/genesis`'s published tarball ships only `dist/` + this README (see `files` in
+# package.json) — the bootstrapper script itself is NOT vendored by npm yet, so
+# `node_modules/@marktiderman/genesis/scripts/harness/genesis-sync.sh` does not exist. Today, fetch
+# that one script straight from the source repo and run it against your repo (it only needs your
+# repo root + the installed umbrella manifest — where the script itself lives doesn't matter):
+git clone --depth 1 https://github.com/marktiderman/genesis.git /tmp/genesis-src
+bash /tmp/genesis-src/scripts/harness/genesis-sync.sh   # BOOTSTRAPS: reads the installed umbrella,
+                                                         # vendors the matching harness + scaffolds
+                                                         # the Git Data System trellis
+rm -rf /tmp/genesis-src
+
+bash tools/genesis-harness/scripts/harness/genesis roller validate --ci   # validate the trellis
+```
+
+The bootstrap reads the source repo + version straight out of the installed umbrella manifest,
+prefers the release tag matching that version (falling back to the branch tip), and writes a
+`.genesis/source` stamp recording the vendored version **and** the exact SHA. Re-running the same
+script later re-vendors (upgrades) the stamped tree — and once vendored, `tools/genesis-harness/
+scripts/harness/genesis sync` is the one-liner for that (see the `sync` skill). One pinned umbrella
+version therefore really does mean every sub-component **and** the harness land together, versioned
+by one coordinate.
+
+**Known gap.** The `git clone` step above is a stand-in for a real `npx`-invokable bootstrapper
+(e.g. a `bin` entry shipping `genesis-sync.sh` in the umbrella's own tarball, mirroring the
+`npx genesis-data init` pattern `@marktiderman/genesis-data` already ships). That packaging work is
+tracked as follow-up, not done in this change — don't let this doc drift back to claiming the script
+ships with the npm install until it actually does.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@marktiderman/genesis",
-  "version": "0.4.0",
+  "version": "0.4.2",
   "private": false,
   "type": "module",
   "sideEffects": false,
@@ -76,7 +76,7 @@
     "@marktiderman/genesis-ui": "1.2.0",
     "@marktiderman/genesis-design-system": "1.1.1",
     "@marktiderman/genesis-switchboard": "1.0.0",
-    "@marktiderman/genesis-data": "0.3.0",
+    "@marktiderman/genesis-data": "0.3.2",
     "@marktiderman/genesis-ui-native": "2.0.1"
   },
   "peerDependencies": {