Mario Zechner 7670c8be43 feat(p2): stored, renamable /tree branch labels ... p2.main version 2 stores a label per branch: { conversation, label }. A new branch is labelled in the commit that forks it, with the start of the message the owner picked (the answer for "Branch from here", the edited user message for "Edit"). Conversation 1 keeps null, which every UI shows as the session title. Version 1 migrates to null labels; at start the worker fills the other branches once from their fork points. - SessionTree v2: rename (owner), Tree.branches, TreeNode.conversation - Sessions v5 / Catalog v4: a branch label may be null - the worker reports p2.main changes; the derived labels are gone - web: a pencil beside each sidebar branch row opens a rename sheet - TUI: /tree shows branch labels; Shift+L renames the selected branch		2026-11-04 15:38:43 +01:00
..
p2	feat(p2): stored, renamable /tree branch labels	2026-11-04 15:38:43 +01:00