Skip to content

Commit 96e7aa6

Browse files
Narrow the search delta to what is still unproven
Both surfaces now return results from their own store. What remains is that the production sync path has never run successfully — the production store was populated by hand — and that a failing sync still surfaces nowhere, which is why the original bug survived three months. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> agent-session-id: 05bdf052-d9c2-4930-bfef-1fd90b43680b agent-tool: Claude Code agent-tool-version: 2.1.220 agent-model: claude-opus-5 agent-runtime-profile: /nix/store/57hz15fbcg9c3hasm0ny3axd5pg33rh3-coding-agent-runtime-profile/share/coding-agents/profile.json agent-skills-manifest: /nix/store/d9hvhhg1k9n3j20dgcch7sz3sg98l377-agent-skills-corpus/share/agent-skills/manifest.json tooling-profile: dotfiles@b785b9f
1 parent 3d00be2 commit 96e7aa6

1 file changed

Lines changed: 20 additions & 13 deletions

File tree

context/04-docs/02-search/.delta/DELTA-001-index-stale-and-surfaces-crossed.md

Lines changed: 20 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -46,12 +46,10 @@ Related: the underlying provider configuration is undeclared, tracked as
4646

4747
Applied 2026-07-27:
4848

49-
1. `sync-docs.yml` is rebuilt to generate from `sync-docs.yml.genie.ts` on the
50-
shared devenv/nix setup, removing the pnpm pin that broke it, and to select
51-
its target with two gated jobs so a missing store id fails loudly instead of
52-
silently falling back to a legacy store. That repair is livestorejs/livestore#1507
53-
and is not part of the change that introduces this delta; until it merges,
54-
`main` still passes the legacy store id to the production sync.
49+
1. `sync-docs.yml` now generates from `sync-docs.yml.genie.ts` on the shared
50+
devenv/nix setup, removing the pnpm pin that broke it, and selects its target
51+
with two gated jobs so a missing store id fails loudly instead of silently
52+
falling back to a legacy store. Merged as livestorejs/livestore#1507.
5553
2. Two stores now exist — `livestore-docs-prod` (released docs, populated from
5654
`v0.4.0`) and `livestore-docs-dev` (refreshed from `main`) — and the
5755
`MXBAI_VECTOR_STORE_ID_DEV` / `_PROD` secrets that the workflow had always
@@ -61,11 +59,20 @@ Applied 2026-07-27:
6159
now stored using Netlify's secret mechanism (`LS.DEL.INFRA-R06`) rather than
6260
as plain configuration.
6361

64-
Outstanding: the development surface still returns HTTP 500. Netlify injects
65-
environment variables into the function bundle at build time, so the corrected
66-
credential takes effect on that site's next deploy rather than immediately; a
67-
re-publish of the existing deploy is not sufficient. The production surface
68-
serves results from the production store and is correct.
62+
Both surfaces now return results: production from the production store,
63+
development from the development store.
6964

70-
Close this delta once `dev.docs.livestore.dev/api/search` returns results, which
71-
confirms a docs push is reflected in the surface that push targets.
65+
Outstanding, and why this delta stays open:
66+
67+
- **The production sync path has never run successfully.** The production store
68+
was populated by hand so the surface would not serve a stale index; the
69+
release pipeline that is supposed to maintain it is now wired correctly but
70+
unproven. `LS.DOCS.SEARCH-R01` promises the index updates on every stable
71+
release, and that promise is still untested.
72+
- **Silent failure remains possible.** The proximate bug was a stale pnpm pin,
73+
but the reason it survived three months is that a failing sync surfaced
74+
nowhere. Detection belongs with the disabled alignment-notification job
75+
(livestorejs/livestore#1183) rather than a mechanism invented here.
76+
77+
Close this delta once a stable release has refreshed the production index
78+
without manual intervention.

0 commit comments

Comments
 (0)