Settings can block cloud sessions from using this machine's MCP servers, and "not now" is remembered

What

MCP servers are add-on tools Claude can call. The device bridge lets cloud sessions use the MCP servers set up on this machine. It changed in these ways:

• Settings denial: a servingDenied check can now block serving. When it does, tools already served are withdrawn and a policy_denied event is recorded.
• Config loading: configs are worked out through resolveOffer, and the device bridge config loader now returns both the configs and deniedBySettings instead of only the configs.
• "Not now" memory: answering "not now" to the consent prompt is now remembered (readNotNow). The consent dialog writes this record when consent is still unset, and the consent_unset event carries putOff.

Before, only consent states (declined, unset, accepted) were checked. The readings for tengu_device_mcp_serving and tengu_device_mcp_consent_prompt have not been read.

Why

A settings policy can now stop cloud sessions from reaching a person's local MCP servers and be reported as the reason. The consent prompt may ask less often after a "not now".