Rename grace (formerNames) for peers' pins
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 1h
- Merged PRs (30d)
- 17
Description
What it does
After a session is renamed, peers that pinned the old name are still delivered to for a grace period, through a formerNames field on the session's record.
Source
ganja-code-uul (a rename grace, formerNames).
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: After a rename, a peer's old pin becomes an honest refusal (NameMoved or Unknown), never a silent misdelivery, and D535's
list_sessionslets the peer look the new name up in one tool call. - Evidence:
formerNamesis omitted on purpose (crates/ganja-tool/src/registry.rs:100). It was considered and refused twice for lack of evidence in the reference; 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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read crates/ganja-tool/src/registry.rs around line 100 and the README guidance at lines 16-18; trace how session renames and peer pins are represented. Reconcile the issue's stated grace-period behavior with its requirement that old pins refuse honestly, then make the smallest registry change and verify the renamed-session lookup behavior described here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, distributed-systems
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100