docs(releases): the 10.4.0 entry catches up to the late trains — repair routing, the vector ledger and open-gate leg, the loud config guard, the JSON-safe crossing
This commit is contained in:
parent
d3aacfaf24
commit
834149ed90
1 changed files with 19 additions and 0 deletions
19
RELEASES.md
19
RELEASES.md
|
|
@ -105,6 +105,25 @@ the flag has no effect on timing. Full manual control still lives in
|
|||
writes to both, swaps atomically, and persists once after the swap. Reads
|
||||
never observe a partial index. `repairIndex({ rebuild: ['metadata'] })` uses
|
||||
it automatically.
|
||||
- **Incremental heal is routed.** A provider invariant that asks for the
|
||||
incremental heal (`heal: 'repair'`) now routes to the provider's own
|
||||
`repair()` when it exposes one — re-posting exactly what its ledger names,
|
||||
never a store-sized rebuild — and the post-heal re-read of the report decides
|
||||
success; a repair that doesn't converge is recorded with the escalation named.
|
||||
- **The vector family joins the count ledger.** `getCanonicalCounts()` gains
|
||||
`vectors: { all }` — the count of canonical entities holding a real vector
|
||||
(deferred-embed entities count when their vector lands). And the open gate
|
||||
closes the vector leg: a store whose canonical rows hold vectors but whose
|
||||
derived vector index is empty now builds at `open()` (or refuses with the
|
||||
typed error) instead of silently serving empty vector-search results.
|
||||
- **An unknown storage config shape fails loudly.** A nested `config` object
|
||||
carrying a path-shaped key (a shape that was never supported) used to fall
|
||||
through silently to the default shared directory — every instance writing one
|
||||
store while callers believed each had its own. It now throws, naming the
|
||||
canonical `path` key.
|
||||
- **Relation index rows are JSON-safe.** Internal endpoint identifiers can no
|
||||
longer ride the metadata-index crossing (a native provider serializes it);
|
||||
they stay on the graph operations where they belong.
|
||||
- **A broken accelerator install can never read as "not installed."** The
|
||||
auto-detection free pass now requires the resolution error to name the
|
||||
accelerator package itself, exactly — a missing platform-binary sibling
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue