Overview
dsh-plugin-branchpoint
README / EN
Package documentation
Registry summary
dsh.pub verifies the pinned bundle contract, runtime facts, and distribution semantics. The complete README remains in the source repository.
Read the full README on GitHubLIMITATIONS
Known limitations
- The digest is built from the **DSH session event log**. Reasoning and raw tool output are not summarized; only visible assistant text, tool errors, changed files and commands are used. - The digest framing is English. Quoted conclusions stay in the language of the chat, since they are extracted verbatim. - Section detection relies on Markdown headings (`## …`), bold headings (`**…**`), and numbered lists (`1. …`). A plain-prose chat may show no section rows; «Вся ветка» still works. - A task section needs at least two numbered items; a theory section needs at least 160 characters. - Formulas stay as LaTeX in the digest, so the branch renders them like the main chat after the message is sent. The composer itself is plain text: until you send, `$\log_2 32$` is visible as source. - Branch numbers count only branches created by 0.6.0 or later for that parent; older branches keep their titles and do not consume a number. - The **↩** button appears only for branches created by 0.5.0 or later, and only while the browser keeps the `localStorage` link. - The tree mark and pin are applied once to the root chat when you first split a branch from it. If the chat is unnamed (no visible title yet), the mark is retried on the next branch. - The return note replaces any unsent draft in the main composer. - History is paged at most six times per click, so extremely long sessions may still need a second click to reach the original prompt. - If a branch has no assistant text and no tool results, Branchpoint shows an alert and does not open an empty session.
