@adhd/backlog 0.1.7 → 0.1.8

package/CHANGELOG.md

@@ -1,3 +1,16 @@
+## 0.1.8 (2026-08-19)
+
+
+### 🩹 Fixes
+
+- **backlog:** singleton writer lock for `serve` — two concurrent servers against one store corrupted the db (BUG-020). O_EXCL PID-file lock keyed on the canonical realpath'd db path, held from before the store opens until after it is fully closed, so a second `serve` during shutdown drain is refused rather than admitted. Dead holders reclaimed; refusal names the holder pid and lock path.
+- **backlog:** consume `@adhd/sox-store-adapter` 0.7.0. The dependency was pinned `^0.5.8`, and a caret on a 0.x pins the MINOR — so it could never resolve past 0.6.0 and none of the WAL/durability work reached this store. Brings the adaptive idle-flush debounce (BL-590), baseline-relative WAL cap (BL-587), and verified busy-error classification in the wal-cap backstop (BUG-019).
+
+
+### ❤️  Thank You
+
+- pseudosky
+
 ## 0.1.7 (2026-08-14)
 
 

package/env.d.ts

@@ -61,3 +61,36 @@ export declare function resolveBacklogDbPath(env: Environment<BacklogConfig>): s
  * `claimItem` itself.
  */
 export declare function suggestClaimantIdentity(agentName: string, instanceId: string): string;
+/**
+ * BUG-CACHE-CWD-001: the effective apigen extract-stage IR-cache file path.
+ * Prior to this fix, `server.ts`'s `irCacheFile()` defaulted to
+ * `join(process.cwd(), 'tmp', 'apigen', 'ir-cache', 'backlog-client.ir.json')`
+ * — a NEW cache (and a NEW `tmp/apigen/ir-cache/` directory) was created in
+ * every distinct directory `backlog` was ever invoked from: every repo, every
+ * git worktree, and — because `startBacklogServer`'s `opts.cwd` test-override
+ * plumbing was sometimes used unintentionally as a live cwd — even
+ * `~/.adhd/backlog/production/data/tmp/apigen/ir-cache/`, nested one level
+ * inside the live store's own data directory. None of these scattered copies
+ * ever saw a cache HIT from any other copy, so every distinct invocation
+ * directory paid a full re-extraction — a correctness-neutral but pure
+ * performance and disk-hygiene regression (FEAT-002's entire point, undone).
+ *
+ * Resolution order (highest precedence first), matching `resolveBacklogDbPath`'s
+ * own precedence-comment convention:
+ *
+ *   1. `APIGEN_IR_CACHE_FILE` (explicit escape hatch — tests point this at a
+ *      throwaway file; see `ir-cache.integration.spec.ts`) — wins outright.
+ *   2. The `cache` dir's resolved path (`kind: 'cache'` → shared, scope
+ *      forced to `'global'` — see the `dirs.cache` doc comment above) +
+ *      `apigen/ir-cache/backlog-client.ir.json`. Absolute, `process.cwd()`-
+ *      independent, and identical across every scope/repo/worktree on this
+ *      machine — exactly the fast-path guarantee FEAT-002 designed for.
+ *
+ * `adhdRoot`/`instanceId` are accepted purely for test isolation (mirrors
+ * `buildBacklogEnv`'s own test-isolation fields) — production callers never
+ * pass them.
+ */
+export declare function resolveIrCacheFile(options?: {
+    adhdRoot?: string;
+    instanceId?: string;
+}): string;