@adhd/backlog 0.0.2 → 0.1.0

package/{dist/model.d.ts → model.d.ts}

@@ -155,6 +155,19 @@ export interface BacklogFilter {
      * duplicated into root.
      */
     rootLevel?: boolean;
+    /**
+     * Drops items with `metadata.archivedAt` set (BACKLOG-adoption's
+     * `archiveResolved` — SPEC.md §5.4). `renderToMarkdown` always applies
+     * this internally (a markdown projection never shows archived rows), but
+     * `listItems`/`queryItemNodes` do NOT default to it — auditing/reporting
+     * consumers legitimately need to see archived items too. A caller that
+     * needs to reproduce `renderToMarkdown`'s exact item set through
+     * `listItems` (e.g. `render-projections.mjs`/`parity-check.mjs` verifying
+     * a rendered projection against the graph's own view of the same filter —
+     * BUG-BACKLOG-RENDER-VERIFY-ARCHIVED-MISMATCH-001) must set this
+     * explicitly; otherwise the two queries diverge on every archived row.
+     */
+    excludeArchived?: boolean;
     limit?: number;
     offset?: number;
 }

package/package.json

@@ -1,34 +1,28 @@
 {
   "name": "@adhd/backlog",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "bin": {
-    "backlog": "./dist/index.js"
+    "backlog": "index.js"
   },
   "dependencies": {
     "@adhd/sox-graph-store": "^0.3.0",
     "better-sqlite3": "^12.10.0",
-    "@adhd/environment": "0.0.2",
-    "@adhd/environment-base-spec": "0.0.3",
-    "@adhd/apigen-core-client": "^0.1.1",
-    "@adhd/apigen-plugin-api-fastify": "^0.1.2",
-    "@adhd/apigen-plugin-openapi": "^0.1.3",
-    "@adhd/apigen-plugin-mcp": "^0.1.2",
-    "@adhd/apigen-plugin-cli-output": "^0.1.3",
-    "@adhd/apigen-engine-naming": "^0.1.3",
-    "yaml": "1.10.3"
+    "@adhd/environment": "^0.1.0",
+    "@adhd/environment-base-spec": "^0.1.0",
+    "@adhd/apigen-core-client": "^0.2.0",
+    "@adhd/apigen-plugin-api-fastify": "^0.2.0",
+    "@adhd/apigen-plugin-openapi": "^0.2.0",
+    "@adhd/apigen-plugin-mcp": "^0.2.0",
+    "@adhd/apigen-plugin-cli-output": "^0.2.0",
+    "@adhd/apigen-engine-naming": "^0.2.0",
+    "yaml": "1.10.3",
+    "pino": "10.3.1",
+    "pino-pretty": "13.1.3"
   },
-  "devDependencies": {
-    "@types/better-sqlite3": "^7.6.13"
-  },
-  "main": "./dist/index.js",
-  "module": "./dist/index.mjs",
-  "typings": "./dist/index.d.ts",
+  "main": "./index.js",
+  "module": "./index.mjs",
+  "typings": "./index.d.ts",
   "publishConfig": {
     "access": "public"
-  },
-  "files": [
-    "dist",
-    "CHANGELOG.md",
-    "skill"
-  ]
+  }
 }

package/{dist/server.d.ts → server.d.ts}

@@ -1,5 +1,5 @@
 import { BacklogCtx } from './client.js';
-import { composeSchemas, Operation, OutputPlugin, RunInput } from '@adhd/apigen-core-client';
+import { composeSchemas, Operation, Logger, OutputPlugin, RunInput } from '@adhd/apigen-core-client';
 import { Scope } from '@adhd/environment-base-spec';
 
 /**
@@ -13,6 +13,30 @@ import { Scope } from '@adhd/environment-base-spec';
  * plain re-export instead.
  */
 export declare function requireRun(plugin: OutputPlugin): (input: RunInput) => Promise<void>;
+/**
+ * Test-only `RunInput.logger` override (exported for `cli.ts`'s identical
+ * third-transport mount). Every one of the three apigen output plugins
+ * (`apigen-plugin-api-fastify`, `-mcp`, `-cli-output`) falls back to its own
+ * `createLogger()` — real pino, level `info`, writing jsonl to stderr —
+ * whenever `input.logger` is absent, which floods the console on every test
+ * run that actually mounts a transport (`server.spec.ts`, `server.mcp.spec.ts`,
+ * `serve.spec.ts`, and `cli.spec.ts`'s spawned-binary cases, since
+ * `spawnSync`'s `env: { ...process.env }` inherits vitest's own
+ * `VITEST=true`). None of those specs assert on log content — they assert
+ * status codes and response bodies — so under vitest this swaps in a no-op
+ * logger. `mcpPlugin`/`cliPlugin` only ever call `.info`/`.error` on it, but
+ * `apiFastifyPlugin` hands it straight to `Fastify({ logger })`, whose own
+ * `validateLogger` (`fastify/lib/logger.js`) REQUIRES the full pino surface
+ * (`info,error,debug,fatal,warn,trace,child`) or throws
+ * `FST_ERR_LOG_INVALID_LOGGER` — confirmed empirically, not guessed, by a
+ * first cut here that only stubbed `info`/`error` and blew up every
+ * `server.spec.ts` HTTP test with exactly that error. `child()` returns the
+ * same no-op instance (fastify calls it per-request to derive a child
+ * logger; a self-referencing no-op keeps every descendant silent too).
+ * Outside vitest (a real `backlog serve` or CLI invocation) this returns
+ * `undefined` and the real pino default logger is used, unchanged.
+ */
+export declare function testSilentLogger(): Logger | undefined;
 export interface StartOpts {
     transport: 'http' | 'mcp' | 'both';
     port?: number;