Gregory SchierandClaude Opus 5.5 1b0a196c50 Merge main into feat/request-versioning ...

Conflicts were all at registration points; both sides are kept.

Main now routes every write through one connection (#642): ClientDb only
reads and writes go through `with_tx` on a WriteDb. Versioning follows:
snapshot, restore, prune and the cascade delete move to WriteDb, while the
lookups and the "has it changed" check stay on ClientDb. Callers take a
write transaction the way their neighbours do:

- The HTTP send snapshots in its own transaction from
  `resolve_send_inputs`, and a failure there (including not getting the
  writer) is still logged and swallowed, so the response just has no
  version.
- gRPC and WebSocket connect snapshot inside the transaction that upserts
  the connection.
- The snapshot and restore RPCs, on the desktop and in the browser host,
  each run in a transaction.
- The request and workspace cascades live on main's WriteDb deletes.

The Request Changed dropdown moves into the response pane's
`statusLineRight` slot, since main moved the status line into the shared
pane view.

The plugin runtime's copy of the model bindings picks up `versionId`, and
`gen_rpc.ts` is regenerated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-06 09:23:32 -07:00

..

serde_json

Decouple core Yaak logic from Tauri (#354)

2026-01-08 20:44:25 -08:00

gen_api.ts

Decouple core Yaak logic from Tauri (#354)

2026-01-08 20:44:25 -08:00

gen_events.ts

Move response filters into Rust (#755)

2026-10-15 06:22:23 -07:00

gen_models.ts

Merge main into feat/request-versioning

2026-11-06 09:23:32 -07:00

gen_search.ts

Agents pane: CLI-only MCP, yaak mcp --http, and plugin deprecation (#761)

2026-10-25 23:14:45 -07:00