Pin persistence across resume

Open
#76 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
cli

Research direction

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.

Written by the indexing model from the issue text.

Description

idea size:S verdict:do

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

Dominant language
Rust
Stars
2
Forks
0
Avg merge
1h
Merged PRs (30d)
17

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from zchee/ganja-code

All issues in zchee/ganja-code

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.