Repository navigation
RAL-201: a restart under a new nickname is told its predecessor through the ledger - #290
Merged
Merged
Conversation
…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
force-pushed
the
ral-201-succession-tie
branch
from
November 17, 2026 20:11
49f0bbf to
84357ea
Compare
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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_nameand cwd are both declared by the shim. Sosession-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), andlines()takes the succession. New tests:a_succession_is_only_what_the_rally_confirmedanda_new_nickname_is_told_its_predecessor_only_through_the_record.src/session.rs:RallyContext.sessionsfrom/v1/rallies.src/main.rs: session-start wiring.docs/session-hook.md,docs/roadmap.md.Evidence: at 49f0bbf,
cargo fmt, andcargo clippy --all-targets -- -D warningsare clean, andcargo test --no-fail-fastpasses 759 tests with 0 failures. I didn't run a live restart through the hook.🤖 Generated with Claude Code