1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
//! Instance-level policy the bridge enforces on managed client installations.
//!
//! Configured as a top-level `bridge_policy:` section in a services YAML and
//! carried to clients inside the signed bridge manifest. Two knobs today:
//! whether Claude Code's managed-MCP policy re-allows claude.ai first-party
//! connectors (`allowAllClaudeAiMcps`) alongside the managed server set —
//! without it, writing `managed-mcp.json` suppresses every connector the user
//! linked on claude.ai — and whether bridges keep themselves current.
//!
//! Copyright (c) systemprompt.io — Business Source License 1.1.
//! See <https://systemprompt.io> for licensing details.
use ;
/// Whether a bridge updates itself, and how far it is allowed to go on its own.
///
/// `Staged` downloads, verifies and swaps the on-disk binary but never restarts
/// the running process: the next natural launch runs the new version. There is
/// deliberately no variant that restarts unattended — the fleet-wide brake for
/// a bad release is `pinned_version` on the release feed, not a client toggle.