@tpsdev-ai/flair 0.28.0 → 0.30.0

package/README.md

@@ -67,7 +67,7 @@ If you need any of those specifically, use them. If you need crypto-pinned ident
 
 Anthropic shipped [Claude Dreams](https://platform.claude.com/docs/en/managed-agents/dreams) (research preview, April 2026) — async pipeline that reads a memory store + session transcripts and produces a curated output store: duplicates merged, stale entries replaced, insights surfaced. Validates the category: agent memory accumulates drift and needs cleanup.
 
-Flair ships both the on-demand curation surface (`flair rem rapid`) AND the scheduled nightly cycle, per the [FLAIR-NIGHTLY-REM spec](specs/FLAIR-NIGHTLY-REM.md) and its [in-process distillation slice](specs/FLAIR-NIGHTLY-REM-SLICE-2-DISTILLATION.md). Config recipe (Ollama zero-key default, hosted-provider egress warning, clustered-deploy rules): [`docs/rem.md`](docs/rem.md).
+Flair ships both the on-demand curation surface (`flair rem rapid`) AND the scheduled nightly cycle, per [`docs/rem.md`](docs/rem.md) and its [distillation UX design note](docs/notes/rem-ux.md). **REM requires a configured generative backend** (Ollama, OpenAI, Anthropic, etc.) — without one, `flair rem rapid` fails with `Reflection error: No generative backend configured`. Config recipe (Ollama zero-key default, hosted-provider egress warning, clustered-deploy rules): [`docs/rem.md`](docs/rem.md).
 
 - **`flair rem rapid`** — reflects and distills server-side by default, staging candidates in one bounded call. `--focus {lessons_learned, patterns, decisions, errors}` mirrors Dreams' `instructions` parameter. `--prompt-only` falls back to the bring-your-own-model handoff. Outputs *candidates*, not a wholesale store swap.
 - **`flair rem candidates` / `flair rem promote <id> --rationale "<why>"` / `flair rem reject <id>`** — review and promote distilled candidates with required rationale.

package/dist/bridges/builtins/index.js

@@ -10,7 +10,7 @@
  * To add a new built-in:
  *   - YAML: write `src/bridges/builtins/<name>.ts` exporting a `YamlBridgeDescriptor`
  *   - Code plugin: write `src/bridges/builtins/<name>.ts` exporting a `MemoryBridge`
- *   Then register it here. See specs/FLAIR-BRIDGES.md §2 for shapes A/B.
+ *   Then register it here. See docs/bridges.md § Two shapes for shapes A/B.
  */
 import { agenticStackDescriptor } from "./agentic-stack.js";
 import { claudeProjectMemoryBridge } from "./claude-project.js";

package/dist/bridges/discover.js

@@ -1,6 +1,6 @@
 /**
  * Bridge discovery — scans the four conventional sources defined in
- * FLAIR-BRIDGES.md §7:
+ * docs/bridges.md § Discovery:
  *
  *   1. Project YAML:   <cwd>/.flair-bridge/*.yaml
  *   2. User YAML:      ~/.flair/bridges/*.yaml

package/dist/bridges/runtime/load-plugin.js

@@ -53,7 +53,7 @@ export async function loadCodePlugin(discovered, opts = {}) {
             field: "exports",
             expected: "named `bridge` export or default export implementing MemoryBridge",
             got: typeof mod === "object" && mod !== null ? `exports=${Object.keys(mod).join(",") || "(empty)"}` : typeof mod,
-            hint: `flair-bridge-<name> packages must export \`bridge\` (or default-export) a MemoryBridge. See specs/FLAIR-BRIDGES.md §6`,
+            hint: `flair-bridge-<name> packages must export \`bridge\` (or default-export) a MemoryBridge. See docs/bridges.md § Shape B`,
         });
     }
     // Validate the shape. Keep this minimal — we trust the plugin author

package/dist/bridges/scaffold.js

@@ -1,7 +1,7 @@
 /**
  * Bridge scaffolding — emits a working starter for a new bridge.
  *
- * From FLAIR-BRIDGES.md §2: "Scaffold & test in-tree. `flair bridge
+ * From docs/bridges.md § Two shapes: "Scaffold & test in-tree. `flair bridge
  * scaffold <name>` emits a working starter; `flair bridge test <name>`
  * runs a round-trip diff." This file handles the `scaffold` half.
  *
@@ -34,7 +34,7 @@ function fileDescriptorTemplate(name) {
 # Generated by \`flair bridge scaffold ${name} --file\`.
 # Edit to match your foreign system, then run \`flair bridge test ${name}\`.
 #
-# Spec: see FLAIR-BRIDGES.md §4 (memory schema) and §5 (YAML shape).
+# Spec: see docs/bridges.md § The memory record and § Shape A.
 name: ${name}
 version: 1
 kind: file
@@ -90,7 +90,7 @@ function apiIndexTemplate(name) {
  * flair-bridge-${name}
  *
  * Generated by \`flair bridge scaffold ${name} --api\`.
- * Spec: see FLAIR-BRIDGES.md §4 (memory schema) and §6 (code plugin shape).
+ * Spec: see docs/bridges.md § The memory record and § Shape B.
  *
  * After editing, run:
  *   flair bridge test ${name}

package/dist/bridges/types.js

@@ -1,7 +1,7 @@
 /**
  * Types for the Flair memory bridge plugin system.
  *
- * Mirrors the contract in specs/FLAIR-BRIDGES.md. These types are the
+ * Mirrors the contract in docs/bridges.md. These types are the
  * public surface a bridge author (human or agent) targets.
  *
  * IMPORTANT: the YAML bridge format (shape A) also conforms to these types

package/dist/cli-shim.cjs

@@ -9,7 +9,7 @@
  *   The real CLI (dist/cli.js) is an ES module. In ESM, every top-level
  *   `import` is HOISTED and the whole module graph is LINKED + EVALUATED before
  *   the first statement in the file body runs. Flair's deps (harper-fabric-
- *   embeddings requires Node >=22, @harperfast/harper / commander require >=20)
+ *   embeddings requires Node >=22, harper / commander require >=20)
  *   fail to load on an older engine — so a Node-version check placed even at the
  *   very top of cli.ts never executes: the import graph crashes first. That is
  *   exactly the silent-onboarding-failure bug (a Harper dev got zero output and