selfSent through the socket peer pid and an ancestry walk

What it does

Makes the self_sent input real: the accepted peer's process id is carried from the socket to the engine, and an ancestry walk decides whether the sender is this session's own child.

Source

ganja-code-umz (selfSent through the kernel peer pid at the socket and an ancestry walk).

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; the nearest direction it states is ganja as the control plane (README.md:16-18).
• Today's terminal users: The listener checks the peer's uid at accept and drops the rest (crates/ganja-serve/src/socket.rs:244-263), so self_sent is an always-false input at every production call site (crates/ganja-core/src/teammate/inbound.rs:59).
• Evidence: The reference's ancestry walk is macOS-gated and its Linux side is untraced. The macOS and Linux probe is part of the work.

Depends on

No other idea.

Verdict

• Verdict: do
• Size: M — one plan and one decision number.
• Exception to the probe rule: yes. #36 says an idea that needs a measurement or a probe first is not do; this one is an explicit exception: the macOS and Linux probe is part of the work.
• Date: 2026-09-19
• Verdict ticket: #41

Theme: #54

Start with crates/ganja-serve/src/socket.rs:244-263 and crates/ganja-core/src/teammate/inbound.rs:59 to trace the accepted peer identity and current self_sent input. Run or inspect the macOS and Linux process probes, then verify that the peer pid reaches the engine and the ancestry walk identifies whether the sender is this session's child.