obsidian-lean-coder 0.4.0 → 0.4.1

package/CHANGELOG.md

@@ -4,6 +4,18 @@ All notable changes to OLC (Obsidian Lean Coder) are recorded here.
 OLC is pre-release: versions are `0.x` until a controlled-testing release says otherwise.
 `package.json` shipped `"private": true` through 0.1.0; the flag was removed at publish time with explicit user approval, and 0.1.0 is live as [`obsidian-lean-coder`](https://www.npmjs.com/package/obsidian-lean-coder). Publishing a new version is still a separate explicitly approved action, never automatic.
 
+## [0.4.1] — 2026-10-14 — verification tooling rule for minimal harnesses
+
+`agents/olc-build.md` gains a verification rule from a real field report: prefer
+tools guaranteed by OLC's own prerequisites (node, npm, git) over extra
+shellutils (cat/grep/awk/sed) a minimal harness may lack, and classify a check
+failure caused by a missing environment binary as an **environment limitation**,
+separate from a task failure. This fixes the *reporting* of such incidents, not
+the environment itself — no instruction can conjure a missing binary.
+
+- **Verification:** typecheck/build clean; full suite green; `npm pack --dry-run` file check.
+- **Upgrade:** `npm install obsidian-lean-coder@0.4.1`, then
+
 ## [0.4.0] — 2026-10-14 — default-like agents + project rules
 
 Agents `olc-plan`/`olc-build` rewritten per user request to behave exactly like

package/README.md

@@ -1,6 +1,6 @@
 # OLC — Obsidian Lean Coder
 
-OpenCode extension for project-scoped planning, memory, and safe Git checkpoints. On npm as `obsidian-lean-coder` (v0.4.0: default-like agents + project rules — see CHANGELOG).
+OpenCode extension for project-scoped planning, memory, and safe Git checkpoints. On npm as `obsidian-lean-coder` (v0.4.1: verification tooling rule for minimal harnesses — see CHANGELOG).
 
 ## Three separate steps
 

package/agents/olc-build.md

@@ -32,6 +32,11 @@ checks. You never expand scope on your own.
   activation needs explicit user approval).
 - Checks: run the smallest meaningful tests/typecheck/lint/build, record exact
   results, never fabricate. Bounded retries, then stop with evidence + options.
+  Prefer tools guaranteed by OLC's own prerequisites (node, npm, git) over
+  extra shellutils (cat/grep/awk/sed) that a minimal harness may lack. If a
+  check fails because an environment binary/dependency is missing — not
+  because of the code — report it explicitly as an **environment limitation**,
+  separate from a task failure.
 - Git safety: no destructive ops (`reset --hard`, force checkout, `clean`,
   branch deletion, force-push) without explicit informed approval. Stage
   explicit paths only — never `git add .` / `-A`, never touch changes outside

package/dist/index.d.ts

@@ -10,5 +10,5 @@
  * `plugin.ts` tool `execute` (deferred to call time), so this re-export
  * cycle is safe under ESM live bindings.
  */
-export declare const OLC_VERSION = "0.4.0";
+export declare const OLC_VERSION = "0.4.1";
 export { default } from "./plugin.js";

package/dist/index.js

@@ -10,5 +10,5 @@
  * `plugin.ts` tool `execute` (deferred to call time), so this re-export
  * cycle is safe under ESM live bindings.
  */
-export const OLC_VERSION = "0.4.0";
+export const OLC_VERSION = "0.4.1";
 export { default } from "./plugin.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "obsidian-lean-coder",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Obsidian Lean Coder — OpenCode extension for project-scoped planning, memory, and safe Git checkpoints.",
   "type": "module",
   "main": "./dist/index.js",