synapse-context 0.1.1

Shared bound-context store (base ⊕ TTL'd overlay), reused verbatim by synapse-proxy and synapse-mcp without a cyclic path dependency between them.
Documentation
  • Coverage
  • 70%
    7 out of 10 items documented0 out of 9 items with examples
  • Size
  • Source code size: 6.39 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 360.12 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 2s Average build duration of successful builds.
  • all releases: 2s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • sustentabilitas/synapse-gateway
    0 2 0
  • crates.io
  • Dependencies
    • —
  • Versions
  • Owners
  • sustentabilitas

Bound context: a generalized key→value bag the proxy injects into forwarded requests. A permanent base (static ⊕ env, built at startup with env winning) is overlaid by an optional pushed binding with a TTL; pushed keys win while live and the overlay reverts on expiry. Single active binding.

This is its own leaf crate (rather than living in synapse-proxy) so that synapse-mcp can depend on it directly: synapse-mcp already needs synapse-proxy's ContextStore verbatim (no forking) for its own identity-injection contract, and synapse-proxy's binary needs to depend on synapse-mcp to wire the MCP gateway listener — putting ContextStore in synapse-proxy itself would make that a cyclic package dependency, which Cargo rejects outright. synapse_proxy::context re-exports these same types so existing import paths are unaffected.