Pin persistence across resume

What it does

Keeps the pin map of name-addressed peers across a resume: it is written to the root session row and re-seeded on resume, following D492's activation flush.

Source

ganja-code-crt (pin persistence across resume).

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 pin guard is cleared on a new conversation (crates/ganja-core/src/engine.rs:4560) and lost across a restart, so a resumed session's first name-addressed send is trust-on-first-use again.
• Evidence: It was considered and refused twice (D528, D532–D535) because the reference showed no evidence of persistence; the captain's verdict does not wait for that evidence.

Depends on

Nothing.

Verdict

• Verdict: do
• Size: S — one commit, no plan.
• Exception to the probe rule: no.
• Date: 2026-09-19
• Verdict ticket: #41

Theme: #54

Start in crates/ganja-core/src/engine.rs:4560 and inspect the resume path, the root session row, and D492's activation flush. Trace how the pin map is cleared and re-seeded, then confirm that a resumed session retains name-addressed peer pins instead of requiring trust-on-first-use again.