@devwithdavid/ledger 0.1.3 → 0.1.4

package/LEDGER.md

@@ -100,7 +100,13 @@ the code.
   code; all code change goes through dispatched agents. Sole exception: a
   concrete, in-the-moment, user-approved operation — executed exactly as
   approved, never inferred or generalized, conferring no standing
-  authority.
+  authority. This exception never covers committing straight to a
+  project's default branch (`main`, `master`, or whatever it's configured
+  as): a branch + PR stays the default delivery path even for your own
+  explicit-exception edit, unless the user's in-the-moment instruction
+  specifically names the default branch itself. You do not commit to a
+  project's default branch — including this project's own — on your own
+  initiative, ever.
 - **C2 — you never merge a branch or PR, force-push, or close a PR without an
   explicit user word naming the specific merge/pull request.** One explicit
   word at a time, in the moment, for that specific PR; there is no standing

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devwithdavid/ledger",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Personal agent-orchestration ledger: SQLite state store, CLI, and herdr watcher plugin.",
   "license": "MIT",
   "repository": "https://yggdrasil.thekartiks.com/chewbakartik/ledger.git",

package/skills/ledger/SKILL.md

@@ -12,6 +12,9 @@ it can't drift out of sync with the real CLI, and carries no machine-
 specific path — `ledger docs` resolves its own reference doc relative to
 wherever the `ledger` package is actually installed on this machine.
 
-If `ledger` isn't found on PATH, it isn't installed here yet: find the
-`ledger` project's own repo (or ask the user where it's cloned) and follow
-its `README.md` install steps first.
+If `ledger` isn't found on PATH, either it isn't installed here yet
+(`npm install -g @devwithdavid/ledger`, then `ledger init` — see the
+project's README for prerequisites), or it's installed but npm's global
+bin directory isn't on PATH (`npm config get prefix`, then confirm
+`<that prefix>/bin` is in `$PATH` — common after switching Node
+versions/managers).