Merge pull request #954 from makenotion/Iron-Ham/release-0.19.0

Release Lore 0.19.0

Author: Iron-Ham

CHANGELOG.md

@@ -11,6 +11,37 @@ log is the canonical source for those.
 
 ## [Unreleased]
 
+## [0.19.0] - 2026-06-08
+
+### Added
+
+- Added planned semantic search for `lore-query action='search'`, including
+  the `strategy: "planned" | "direct"` option, sanitized query variants,
+  query-plan metadata in tool output, and capability-oriented candidate context
+  for SkillRet agent/eval workflows. (#952)
+- Published the sanitized 500-query SkillRet read-only agent checkpoint for
+  planned search chunk 001, with corrected timeout-rerun provenance and report
+  synthesis. (#952)
+
+### Changed
+
+- Query planning now stays enabled by default and is configurable only through
+  `.lore.yaml` `features.queryPlanning`; the environment rollback path was
+  removed from feature-flag taxonomy and documentation. (#953)
+- Confidence no longer affects retrieval ranking. Confidence and trust remain
+  visible for display, auditing, and fact maintenance, while confidence audit
+  and help text now describe trust-score/display impact rather than ranking
+  impact. (#953)
+- Fresh vault schemas no longer create legacy Memories `Confidence` /
+  `Confidence Score` columns, while existing vaults retain compatibility for
+  reads and migrations. (#953)
+
+### Fixed
+
+- Guarded the autosave-learning-source backfill so fresh schemas without the
+  retired Memories `Confidence` column return zero candidates before issuing
+  legacy-property queries. (#953)
+
 ## [0.18.1] - 2026-06-05
 
 ### Added

docs/archive/mcp-tool-history.md

@@ -69,6 +69,20 @@ Historical bumps and what they signalled:
 
 Latest historical note:
 
+- `0.19.0` (2026-06-08) ships planned semantic search for
+  `lore-query action='search'`. Agents can opt between `strategy: "planned"`
+  and `"direct"` and can observe sanitized query variants, query-plan metadata,
+  and capability-oriented candidate context, while the SkillRet eval corpus
+  gains a sanitized 500-query planned-search checkpoint.
+  Query planning remains enabled by default and is configurable only through
+  `.lore.yaml` `features.queryPlanning`; the environment rollback surface is
+  removed. Confidence no longer affects retrieval ranking, but remains visible
+  for display, auditing, and fact maintenance. Fresh vault schemas stop
+  creating legacy Memories `Confidence` / `Confidence Score` columns while
+  existing vaults retain read and migration compatibility. This release changes
+  agent-observable MCP output, retrieval configuration behavior, and setup /
+  migration behavior; the package, lockfile, MCP handshake, CLI version, and
+  Notion `User-Agent` literals move together under the version-sync guard.
 - `0.18.1` (2026-06-05) ships production MCP result handles for memory
   recall/search. Title-tier `lore-query action='recall'` and
   `action='search'` rows now include scoped `rs_*:mN` handles, and

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@makenotion/lore",
-  "version": "0.18.1",
+  "version": "0.19.0",
   "description": "AI memory system backed by Notion",
   "type": "module",
   "bin": {

package.json

@@ -31,7 +31,7 @@ import { costsCommand } from "./commands/costs.js"
 
 const program = new Command()
 
-program.name("lore").description("AI memory system backed by Notion").version("0.18.1")
+program.name("lore").description("AI memory system backed by Notion").version("0.19.0")
 
 program.addCommand(initCommand)
 program.addCommand(authCommand)

src/cli/index.ts

@@ -75,7 +75,7 @@ export async function startServer(): Promise<void> {
   // so reconnecting clients always observe the same string the rest
   // of the build advertises.
   const server = new McpServer(
-    { name: "lore", version: "0.18.1" },
+    { name: "lore", version: "0.19.0" },
     {
       capabilities: {
         tools: {},

src/mcp/server.ts

@@ -9,7 +9,7 @@ import {
 import { redactDebugExtraInfo, redactDebugMessage } from "../debug-redact.js"
 import { normalizeNotionApiBaseUrl } from "../auth/oauth.js"
 
-const USER_AGENT = "lore/0.18.1"
+const USER_AGENT = "lore/0.19.0"
 
 export interface ClientAuthSnapshot {
   token: string