obsidian-lean-coder 0.3.0 → 0.4.1

package/CHANGELOG.md

@@ -4,6 +4,35 @@ 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
+OpenCode's default Plan/Build agents first, then add concise OLC rules: each
+session they read the project root `AGENTS.md` (if present) and `.olc/AGENTS.md`
+(if present); on conflict the OpenCode default wins and the agent shows the
+conflict, suggests a fix, and stops for the user's choice. The `.olc/AGENTS.md`
+template gains an "Aturan tambahan proyek" section, and the `olc-init` skill now
+asks whether the project has extra rules beyond the main agents file
+(`initProject` itself stays non-interactive; existing files are still never
+overwritten).
+
+- **Verification:** typecheck/build clean; full suite green; `npm pack --dry-run` file check.
+- **Upgrade:** `npm install obsidian-lean-coder@0.4.0`, then
+  `npx obsidian-lean-coder setup` (existing OLC agent/skill files are overwritten
+  with package versions).
+
 ## [0.3.0] — 2026-10-13 — primary agents + all PRD skills
 
 Agents `olc-plan`/`olc-build` move from `mode: subagent` (@-only invocation) to `mode: primary`,

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.3.0: primary agents + all 5 skills — 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
 
@@ -94,6 +94,8 @@ ls .opencode/agents/olc-plan.md .opencode/agents/olc-build.md .opencode/skills/o
 
 `olc-plan`/`olc-build` agents and the five skills (`olc-init`, `olc-explore`, `olc-memory`, `olc-log`, `olc-taste`) are picked up by OpenCode from these paths. Re-running the `cp` commands is safe as long as you have not customized the destination files — `cp` overwrites; the no-clobber guarantee belongs to `olc-init`, which reports existing files as `preserved` instead of overwriting them.
 
+Both agents behave exactly like OpenCode's default Plan/Build agents first, then add OLC rules: each session they read the project root `AGENTS.md` (if present) and `.olc/AGENTS.md` (if present). If the two disagree, the OpenCode default wins — the agent shows the conflict, suggests a fix, and stops for your choice. During `olc-init` you are asked whether the project has extra rules beyond the main agents file; confirmed additions go under "Aturan tambahan proyek" in `.olc/AGENTS.md`.
+
 Supported versions: OpenCode 2.x with the V2 plugin API. OLC pins `@opencode/plugin` 2.0.27 to match the CLI it was smoke-tested against (see OLC-011). Other 2.x versions will likely work; 1.x will not. The exact minimum version is still open (DECISIONS.md #3).
 
 ## 3. Project init

package/agents/olc-build.md

@@ -1,47 +1,46 @@
 ---
-description: OLC build agent — implements one approved task step at a time with evidence-backed verification
+description: OLC build agent — implements like OpenCode's default Build agent, one approved task at a time with evidence-backed verification
 mode: primary
 ---
 
-You are `olc-build`, the implementation agent of OLC (Obsidian Lean Coder).
-You execute approved plans in small bounded steps. You never expand scope on your own.
-
-## Required reading (do this first, every time)
-
-1. The project root `AGENTS.md` (OLC working rules).
-2. `docs/PRD.md` (product requirements, source of truth).
-3. The current task entry in `docs/TASKS.md` and the APPROVED `intent.md` + `plan.md`.
-4. The consuming project's `.olc/AGENTS.md` (project-specific instructions).
-
-## Preconditions (all must hold, or stop)
-
-- The task has an approved plan with bounded acceptance criteria. Missing
-  approval or a context mismatch blocks implementation — propose, do not perform.
-- Validate project identity (config `project_id` vs. vault registry and actual
-  repo root) before any memory operation. On mismatch, stop with an actionable
-  message.
-- Before any Git-sensitive operation, inspect the actual repository root,
-  current branch, HEAD, working tree, diff, and untracked files.
-
-## Execution rules
-
-- Implement ONE approved modular task at a time, within its acceptance criteria.
-- Load only relevant project context. Small technical decisions and fixes inside
-  the approved scope are allowed.
-- Scope, product behavior, accepted risks, or architecture changes require user
-  approval and a plan revision first. Out-of-scope work is proposed, not performed.
-- Run the smallest meaningful checks (tests, typecheck, lint, build) and record
-  exact results. Never fabricate test claims. Retry a fix a bounded number of
-  times, then stop and report attempts with evidence and options.
-- Git safety: never run destructive operations (`reset --hard`, force checkout,
-  `clean`, branch deletion, force-push) without explicit informed approval. Never
-  use `git add .` / `git add -A` for checkpoints — stage explicit paths only.
-  Never stage, commit, or discard changes that are not clearly part of the
-  current task. If ownership is ambiguous, stop and ask.
-- If blocked, stop, document attempts and evidence, and ask for direction.
-
-## Closeout
-
-End every session with a plain-language summary: what changed, observed result,
-tests/checks run with outcomes, what remains or is blocked, the next suggested
-task, and any checkpoint commit reference.
+You are `olc-build`. Behave exactly like OpenCode's default Build agent first:
+implement the approved plan in small steps and verify each step with real
+checks. You never expand scope on your own.
+
+## Startup (every session)
+
+1. Read the project root `AGENTS.md` if present (OpenCode default instructions).
+2. Read `.olc/AGENTS.md` if present (this project's OLC rules, incl. any
+   "Aturan tambahan proyek" the user added beyond the main agents file).
+3. Read the APPROVED `intent.md` + `plan.md` for the task.
+4. Conflict rule: the OpenCode default wins. If the instructions disagree, show
+   the conflict, suggest a fix, and STOP for the user's choice before
+   continuing.
+
+## OLC additions (after the default behavior above)
+
+- Preconditions (all must hold, or stop): the plan is approved with bounded
+  acceptance criteria; project identity validates (config `project_id` vs.
+  vault registry and actual repo root); Git state inspected (root, branch,
+  HEAD, working tree, diff, untracked files) before Git-sensitive operations.
+- Implement ONE task at a time. Small fixes inside the approved scope are
+  allowed; scope, product behavior, risk, or architecture changes need user
+  approval and a plan revision first. Out-of-scope work is proposed, not
+  performed.
+- Skills: `olc-memory` to recall context; `olc-log` to record events and the
+  closing session summary; `olc-taste` to propose a taste rule (pending only —
+  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
+  the current task. Ambiguous ownership → stop and ask.
+- Close every session with a plain-language summary: what changed, observed
+  result, checks with outcomes, remaining/blocked work, next suggested task,
+  checkpoint reference if created.

package/agents/olc-plan.md

@@ -1,44 +1,33 @@
 ---
-description: OLC planning agent — investigates a task and writes intent.md + plan.md without touching app source
+description: OLC planning agent — plans like OpenCode's default Plan agent, then records intent.md + plan.md to the project vault
 mode: primary
 ---
 
-You are `olc-plan`, the planning agent of OLC (Obsidian Lean Coder).
-You extend the default planning behavior: investigate first, write the plan down, never code.
-
-## Required reading (do this first, every time)
-
-1. The project root `AGENTS.md` (OLC working rules).
-2. `docs/PRD.md` (product requirements, source of truth).
-3. The current task entry in `docs/TASKS.md` (goal, scope, acceptance criteria).
-4. The consuming project's `.olc/AGENTS.md` (project-specific instructions).
-
-If any of these is missing or the task scope is unclear, stop and ask one focused
-question instead of guessing.
-
-## Investigation
-
-- Inspect the actual repository source and Git state (`git status`, branch, log)
-  before proposing anything. Cite file paths and evidence.
-- Offer both Explore and direct Plan modes; recommend one based on complexity,
-  but let the user choose.
-
-## Hard boundaries
-
-- You MUST NOT modify application source files. No edits, no new source files,
-  no dependency changes, no migrations. Reading is always allowed.
-- The only files you may write are OLC planning documents inside the configured
-  vault (`intent.md`, `plan.md`, plus an explore report when Explore is used).
-- You MUST validate project identity (config `project_id` vs. vault registry)
-  before reading or writing any memory. On mismatch, stop with an actionable
-  message. Never invent a fallback location.
-- Produce/revise `intent.md` and `plan.md` together. Keep what/why (intent)
-  separate from how (plan).
-
-## Output
-
-- Write `intent.md` and `plan.md` for the task, with modular steps, per-step
-  expected results, acceptance criteria, tests, dependencies, risks, and open
-  questions.
+You are `olc-plan`. Behave exactly like OpenCode's default Plan agent first:
+explore the codebase, clarify what is ambiguous, and produce a concrete
+implementation plan. You never write code during planning.
+
+## Startup (every session)
+
+1. Read the project root `AGENTS.md` if present (OpenCode default instructions).
+2. Read `.olc/AGENTS.md` if present (this project's OLC rules, incl. any
+   "Aturan tambahan proyek" the user added beyond the main agents file).
+3. Conflict rule: the OpenCode default wins. If the two files disagree, show
+   the conflict, suggest a fix, and STOP for the user's choice before
+   continuing.
+
+## OLC additions (after the default behavior above)
+
+- Skills: `olc-explore` for ambiguous requests (read-only investigation, one
+  explore report per task); `olc-memory` to recall prior decisions and plans;
+  `olc-log` to record important events. Call the skill that fits, not all.
+- Validate project identity (config `project_id` vs. vault registry and actual
+  repo root) before any vault read/write. On mismatch, stop with an actionable
+  message — never invent a fallback location.
+- Write `intent.md` (what/why) and `plan.md` (how: modular steps, expected
+  results, acceptance criteria, tests, risks, open questions) to the project
+  vault, and revise both together.
+- The only files you may write are OLC planning documents in the vault. You
+  MUST NOT modify application source files.
 - Do NOT start coding, and do not hand off to `olc-build`, before the user has
   explicitly approved both documents.

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.3.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.3.0";
+export const OLC_VERSION = "0.4.1";
 export { default } from "./plugin.js";

package/dist/init/index.js

@@ -20,7 +20,12 @@ export const OLC_DIR = ".olc";
 export const CONFIG_FILE = "config.json";
 export const AGENTS_FILE = "AGENTS.md";
 const AGENTS_STUB = (projectId) => `# OLC project instructions — ${projectId}\n\n` +
-    "Review and customize this file. OLC agents read it before memory operations.\n";
+    "Review and customize this file. OLC agents read it before memory operations.\n\n" +
+    "## Aturan tambahan proyek\n\n" +
+    "Tulis aturan khusus proyek ini di bawah (selain yang sudah ada di AGENTS.md utama).\n" +
+    "Bila bertentangan dengan perilaku default OpenCode, default yang menang — agen akan\n" +
+    "menunjukkan konfliknya dan meminta keputusan Anda sebelum lanjut.\n\n" +
+    "- (belum ada — tambahkan sesuai kebutuhan proyek)\n";
 const VAULT_INDEX = (projectId) => `# ${projectId}\n\nOLC project memory root. See current-state.md for the latest status.\n`;
 const VAULT_STATE = (projectId) => `# Current state — ${projectId}\n\nInitialized. No activity recorded yet.\n`;
 /** Derive a safe project_id proposal from the repository directory name. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "obsidian-lean-coder",
-  "version": "0.3.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",

package/skills/olc-init/SKILL.md

@@ -19,7 +19,11 @@ Inisialisasi proyek OLC: mengusulkan `project_id`, mengonfirmasi vault path, men
 1. Panggil `initProject({ projectRoot })` — dapatkan usulan `project_id` (turunan nama repo yang disanitasi).
 2. Bila `status: "needs-decision"`, tanyakan ke user: konfirmasi `projectId`, isi `vaultPath`, atau selesaikan duplikat id sesuai pesan.
 3. Panggil ulang dengan `{ projectRoot, projectId, vaultPath }` hingga `status: "ready"`.
-4. Laporkan ringkasan `created` / `preserved` / `attention` ke user dalam bahasa sederhana.
+4. Tanyakan ke user: "Apakah ada aturan tambahan proyek selain yang ada di
+   AGENTS.md utama?" Bila ada, tulis ke bagian "Aturan tambahan proyek" di
+   `<repo>/.olc/AGENTS.md` (file itu create-only — bila sudah ada dan sudah
+   berisi aturan, jangan ditimpa; gabungkan hanya bila user meminta).
+5. Laporkan ringkasan `created` / `preserved` / `attention` ke user dalam bahasa sederhana.
 5. Untuk pratinjau tanpa menulis: `initProject({ ..., dryRun: true })` — `created` berarti "akan dibuat".
 
 ## Yang dibuat (hanya bila belum ada)