A bind opt-out that actually unbinds

What it does

Adds a setting with which a session does not bind its cross-session socket at all, for a user whose concern is the bound socket rather than what is delivered.

Source

ganja-code-hie (a bind opt-out that actually unbinds).

The bead is closed when this issue is published, with its external reference pointing here (#38).

File and line references in this issue are to main as of 75a7a92.

Against the three criteria

• Direction (README): The README says nothing about addressing between sessions (README.md:16-18 is the nearest direction).
• Today's terminal users: cross_session_inbound takes accept, hold or refuse (crates/ganja-core/src/config.rs:1884-1897). Refuse drops after admission, so the socket stays bound and the session stays listed; a user whose worry is the bound socket has no switch.
• Evidence: Built carelessly it rolls back D527–D529 for whoever sets it. A plan would have to say what other sessions are told when a name stops resolving, whether an unbound session still writes a record, and whether the key is per-project or global.

Depends on

Nothing.

Verdict

• Verdict: park
• Reopens: at the next landing that touches cross-session behaviour.
• Exception to the probe rule: no.
• Date: 2026-09-19
• Verdict ticket: #41

Theme: #54

Start with README.md:16-18 and cross_session_inbound in crates/ganja-core/src/config.rs:1884-1897. Before implementation, establish the behavior for other sessions when a name stops resolving, whether an unbound session writes a record, and whether the setting is per-project or global; done requires those semantics to be decided and the bind opt-out to actually remove the socket binding.