Skip to content

RAL-201: a restart under a new nickname is told its predecessor through the ledger - #290

Merged
Castor-o7 merged 3 commits into
mainfrom
ral-201-succession-tie
Nov 17, 2026
Merged

Castor-o7 merged 3 commits into
mainfrom
ral-201-succession-tie

Conversation

@Castor-o7

Copy link
Copy Markdown
Owner

RAL-201 (record 5463), the follow-up from RAL-200, as the watchman approved it.

Marshal gives a restarted session a new nickname and records no succession: marshal-entities 0.60.2 has no predecessor field or succession entity, and session_name and cwd are both declared by the shim. So session-start --hook's same-tag transcript search rarely found the earlier session.

Now, when there's no earlier transcript under this session's own nickname, it looks for the open rally's newest rally-session add <new> --succeeds <earlier>. If one exists, it shows the earlier nickname's transcript and ledger record, labelled with the record's number and who declared it. With no confirmed succession, it says it can't tell and how one is confirmed. It never ties nicknames by session name or folder, not even as a hint.

  • src/resume.rs: succession() (pure), and lines() takes the succession. New tests: a_succession_is_only_what_the_rally_confirmed and a_new_nickname_is_told_its_predecessor_only_through_the_record.
  • src/session.rs: RallyContext.sessions from /v1/rallies.
  • src/main.rs: session-start wiring.
  • docs/session-hook.md, docs/roadmap.md.

Evidence: at 49f0bbf, cargo fmt, and cargo clippy --all-targets -- -D warnings are clean, and cargo test --no-fail-fast passes 759 tests with 0 failures. I didn't run a live restart through the hook.

🤖 Generated with Claude Code

…gh the ledger

Marshal gives a restarted session a new nickname and records no
succession, so session-start's same-tag transcript search rarely found
the earlier session. Now, with no earlier transcript of its own
nickname, a session is shown the earlier nickname named by the open
rally's newest `rally-session add <new> --succeeds <earlier>`: that
nickname's transcript and ledger record, labelled with the record's
number and who declared it.

- resume::succession: pure over the open rally's sessions entries. A
  removal, a blank or a self-succession confirms nothing.
- resume::lines takes the succession and shows the earlier nickname's
  work; without one, its "can't tell" line says how one is confirmed.
- session::RallyContext carries the open rally's sessions.
- Never tied by session name or folder, not even as a hint (watchman's
  call): a wrong tie would tell a stranger another session's work.
- docs/session-hook.md and the roadmap entry.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Castor-o7
Castor-o7 force-pushed the ral-201-succession-tie branch from 49f0bbf to 84357ea Compare November 17, 2026 20:11
Castor-o7 and others added 2 commits November 17, 2026 15:24
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Castor-o7
Castor-o7 merged commit 1938205 into main Nov 17, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant