@norman-else/dsh-claude 0.1.32 → 0.1.34

package/INSTALL.md

@@ -16,7 +16,7 @@ Stop if Doctor cannot find an authenticated local Claude Code installation. Do n
 
 ## 2. Link the bundle into the current Web profile
 
-The bundle retains its package-contained system preset and installs a protected compatibility copy at `$DSH_HOME/.agent-presets/claude` during Host activation. This works around supported DSH release-candidate builds replacing third-party preset roots. Existing user-modified files are preserved rather than overwritten.
+The bundle keeps a protected compatibility preset at `$DSH_HOME/.agent-presets/claude`, because DSH Desktop 2.0.4 does not retain third-party preset roots from bundle patches. Its route uses the active profile package source to avoid duplicate client-module Loaders. User-modified preset files are preserved.
 
 ```sh
 dsh plugin --profile web add "link:$(pwd)"

package/README.md

@@ -66,17 +66,126 @@ Preset cleanup removes only installer-managed content and refuses to delete user
 
 ## 3. Features
 
+### 3.1 Conversation
+
 - **Native Claude Code conversations** — Runs Claude Code as the main agent in a normal DSH conversation instead of wrapping it as a tool or secondary chat.
 - **Claude preset and model selection** — Adds a `Claude` Agent Preset and exposes Claude Code's `default`, `opus[1m]`, `fable`, `sonnet`, and `haiku` model choices.
 - **Local Claude environment compatibility** — Preserves the user's existing Claude Code authentication, settings, `CLAUDE.md`, Skills, Hooks, Plugins, tools, and MCP configuration.
 - **Real-time streaming and conversation continuity** — Streams Claude responses and tool activity into DSH while retaining multi-turn context and persisted Claude session resume.
 - **DSH permissions and questions** — Routes Claude tool permission requests through DSH approvals and Claude clarification prompts through DSH's native question forms.
-- **Managed process lifecycle** — Keeps one live Claude process per active session, serializes turns, evicts idle processes, and handles Stop, cancellation, restart, and process-tree cleanup.
+- **Claude command bridge** — Publishes Claude Code's own command catalog into the DSH command palette, retrying with backoff while a fresh CLI finishes loading Skills and Plugins.
+- **Message queue and steering** — Accepts further messages while a turn is running, and lets a queued message be edited, removed, or steered into the turn already in flight.
+- **Rewind** — Drops a message and everything after it: Claude resumes from the kept turn's transcript anchor and genuinely forgets the discarded turns, the discarded rows are hidden from the append-only DSH log, and the original text returns to the composer for editing and resending.
+- **Ask about a selection** — Answers a question about any selected text through a read-only side query limited to `Read`, `Grep`, and `Glob`, reusing the session's model and thinking mode, with the answer copyable or sendable into the main conversation.
 - **Redacted activity timeline** — Displays thinking summaries, tool calls and results, permission events, questions, status changes, usage, errors, and subagent activity without persisting credentials.
 - **Background task tracking** — Shows running and completed Claude subagents or background tasks with task status, recent tools, and expandable activity.
+- **Context usage** — Tracks how much of the context window a session has consumed and surfaces it as a percentage in the conversation and on the session board.
+- **Managed process lifecycle** — Keeps one live Claude process per active session, serializes turns, evicts idle processes, and handles Stop, cancellation, restart, and process-tree cleanup.
+- **Bilingual interface** — Ships every user-facing string in both English and Chinese.
+
+### 3.2 Repository, worktrees, and pull requests
+
 - **Repository and worktree preparation** — Lets a user choose a branch before submitting, switch an eligible local branch, or create a dedicated Git worktree and DSH workspace while transferring the current draft and attachments, and removes a worktree's directory automatically once its workspace is deleted and the tree is clean.
+- **Jira-driven sessions** — Connects to Jira Cloud and starts work from a ticket: the branch is named after the ticket key, the composer is seeded with the ticket brief, the ticket is assigned to the user once the worktree exists, and several tickets can be kicked off at once, each in its own worktree session.
 - **Repository and pull request status** — Shows the current repository, branch, worktree state, changed-line counts, unpushed commits, GitHub pull request, checks, review state, merge state, and blocking Claude rate limits near the composer.
-- **Diff viewer and review comments** — Provides an expandable or maximized branch diff, including file statistics and line-level review comments that are attached to the next Claude message.
-- **Commit, push, and pull request actions** — Supports Commit, Commit & Push, Push, and draft pull request creation, with repository snapshot validation and optional Claude-generated commit messages.
-- **Claude Code settings and Doctor** — Adds a Settings panel for runtime diagnostics, supported Claude settings, worktree branch prefix, process limits, authentication and handshake status, and safe npm update checks.
-- **Managed preset compatibility** — Installs an idempotent compatibility copy of the Claude preset for supported DSH builds without overwriting user-modified preset content.
+- **Session board** — Summarizes every Claude session in one place with its run state, branch, pull request, context usage, auto-fix state, and whether it is waiting on an approval or an answer.
+- **Branch diff viewer** — Provides an expandable or maximized branch diff with file statistics, expand-all and collapse-all, on-demand unmodified context, and comment-to-comment navigation.
+- **Line-level review comments** — Records the user's own line or range comments against the diff and attaches them to the next Claude message.
+- **GitHub review threads** — Reads, replies to, resolves, and unresolves pull request review threads inline, with `@` completion for repository members, bot authors marked as such, and a link back to the thread on GitHub.
+- **Commit, push, merge, and pull request actions** — Supports Commit, Commit & Push, Push, draft pull request creation, and merging a pull request as a merge commit, squash, or rebase, with repository snapshot validation and optional Claude-generated commit messages.
+- **Branch updates** — Updates the current branch from its base by rebase (pushed with `--force-with-lease`) or merge, and hands any resulting conflicts to Claude to resolve.
+- **Pull request feedback handoff** — Expands failing check details and GitHub pull request comments and hands either of them to Claude as a fix request.
+- **Auto fix** — Watches an open pull request for new review comments and failing checks, hands each new batch to Claude to fix, commit, and push, and keeps going until everything passes or the watcher is switched off.
+- **Merged branch cleanup** — Removes the worktree and local branch, archives the workspace's sessions, and deletes the workspace; a plain checkout instead returns to the base branch and deletes the merged branch.
+- **Open in an editor** — Opens the session's working directory in Cursor or IntelliJ IDEA from the session menu, trying each platform's launchers in turn and refusing paths the shell would re-interpret.
+
+### 3.3 Diagnostics, settings, and updates
+
+- **Claude Code settings and Doctor** — Adds a Settings panel for runtime diagnostics, supported Claude settings, output style, worktree branch prefix, process limits, and authentication and handshake status.
+- **Plan usage** — Reports the signed-in subscription's utilization windows — five-hour, weekly across all models, and weekly per model — with reset countdowns, degrading to unavailable rather than failing on API-key, Bedrock, and Vertex sessions.
+- **Plugin updates** — Checks npm for new releases and updates in place, only when the installation is uniquely identified; local development links are never replaced.
+- **Managed preset compatibility** — Installs a guarded Claude preset whose route reuses the active profile package source, preserving discovery on DSH Desktop 2.0.4 without duplicate client-module Loaders or overwriting user changes.
+
+## 4. Contributing
+
+### 4.1 The two contribution types
+
+Every contribution to this repository is exactly one of two types. There is no third type.
+
+| Type | Means | Examples |
+| --- | --- | --- |
+| `feature` | Behavior that does not exist yet | A new composer action, a new Settings field, support for a new Claude Code capability, a documented behavior that was never written down |
+| `fix` | Behavior that already exists but is wrong | A crashing slot entry, a wrong token count, a preset that stops being discovered after a Desktop upgrade, a README statement that no longer matches the code |
+
+Refactors, dependency bumps, test-only changes, and documentation edits are not separate types. File them as the type that matches their purpose: something that is wrong today is a `fix`, something that does not exist today is a `feature`. If you cannot decide which one applies, that is a signal the issue is not scoped yet — open it as a question first and let the maintainer classify it.
+
+### 4.2 Required flow
+
+An issue always comes first. Pull requests that arrive without one are closed unreviewed, regardless of the quality of the code.
+
+1. **Search existing issues.** If your problem or idea is already filed, comment there instead of opening a duplicate.
+2. **Open an issue** at https://github.com/Norman-else/dsh-claude/issues/new/choose and pick the **Feature** or **Fix** form. Choosing the form is how you declare the type: it sets the `[feature]` / `[fix]` title prefix and the matching label for you. Every field listed in §4.3 is required by the form, so an issue that does not explain why it is needed or in what environment it happens cannot be submitted. Blank issues are disabled — if you genuinely cannot tell which type applies, use the "Not sure whether it is a feature or a fix" link on that page and let the maintainer classify it rather than guessing a type to get past the form.
+3. **Wait for the issue to be accepted.** The maintainer confirms the type, the scope, and whether the change belongs in this plugin at all — several things that look like plugin bugs are DSH Host or Claude Code CLI behavior. Do not start implementation before this. Work done on a rejected issue cannot be merged.
+4. **Branch from `master`** using `feature/<issue-number>-<short-slug>` or `fix/<issue-number>-<short-slug>`.
+5. **Implement and verify** against the rules in §4.4.
+6. **Open a pull request** that declares its type and links its issue (§4.5).
+7. **Address review.** The maintainer reviews and approves; the maintainer merges. Contributors do not merge their own pull requests.
+
+`master` is protected: direct pushes, force pushes, and branch deletion are blocked, and a pull request needs one approving review before it can merge. Pushing new commits to a pull request dismisses any existing approval, so expect to request review again after changes.
+
+### 4.3 What the issue must contain
+
+Both types require enough detail for someone else to reproduce your situation without asking you follow-up questions.
+
+**A `feature` issue must state:**
+
+- **Motivation** — what a DSH user cannot do today, and why the current workaround is not good enough.
+- **Proposed behavior** — what should happen, described from the user's side, naming the surface it belongs to (composer, hero repository controls, diff panel, activity timeline, Settings panel, Agent Preset picker, …).
+- **Scope and non-goals** — what this explicitly does not cover, so the pull request can be reviewed against a fixed boundary.
+- **Affected layer** — plugin server (`src/`), client (`src/client/`), managed preset (`preset/`), or a combination.
+- **Compatibility** — the DSH Desktop and DSH package line it targets, and the Claude Code CLI version it relies on. Say so if it depends on a Claude Code capability that older CLI versions do not have.
+- **Alternatives considered** — including "do nothing", and why they were rejected.
+- **Whether you intend to implement it** — so the maintainer knows whether to assign it to you or to schedule it.
+
+**A `fix` issue must state:**
+
+- **Expected behavior vs. actual behavior** — two separate sentences, not one combined complaint.
+- **Reproduction steps** — numbered, minimal, and starting from a clean state. Say whether it reproduces every time or intermittently.
+- **Environment** — plugin version (the `version` field in `package.json`, or the version DSH shows), DSH Desktop version, Claude Code CLI version, operating system, and Node.js version if you installed from source.
+- **Evidence** — the relevant redacted log lines, activity-timeline excerpt, or screenshot. Boot and slot failures surface in the DSH log as `dsh-claude client [boot-check]` and `[slot-entry-crashed]`; include those lines when the plugin fails to load.
+- **Regression range** — the last plugin or DSH Desktop version where it worked, if you know it.
+
+**Redact before you post.** Never paste Claude credentials, API keys, session tokens, private repository contents, or customer data into an issue, a pull request, a test fixture, or a log excerpt. This applies to attachments and screenshots as well. The plugin never asks for or stores Claude credentials, and neither should its issue tracker.
+
+### 4.4 Rules for the change itself
+
+- **Stay out-of-tree.** Use only public DSH exports. Never patch the installed DSH checkout, and never depend on DSH internals that are not exported.
+- **Respect the ownership split.** Claude Code owns its agent loop and tools; this plugin owns presentation, approval and question surfaces, and managed process lifetime. Changes that re-implement Claude Code behavior inside the plugin will be rejected.
+- **Read the spec first** when you change runtime behavior: `docs/aegis/spec/2026-08-15-dsh-claude-spec.md` and the current plan under `docs/aegis/plan/` and `docs/aegis/plans/`. If you are reacting to a DSH Desktop upgrade, follow `docs/upgrading-dsh-desktop.md` — the Host ships no type declarations, so `pnpm typecheck` cannot see its API drift.
+- **Never log, persist, render, or test with real credentials.** Redact before any durable event append.
+- **Run `pnpm check`** — typecheck for both tsconfigs, the Vitest suite, and the build — and make sure it passes before you open the pull request. Do not claim a change works without it.
+- **Cover behavior with tests** where the change is testable. A `fix` should come with a test that fails before the change and passes after it.
+- **Keep one type per branch.** Do not mix a feature and a fix in the same pull request, even if you found them together — open two issues and two pull requests.
+- **Leave releases alone.** Do not bump `version` in `package.json`, edit `scripts/publish.mjs`, or publish. Releases are maintainer-only via `pnpm release`.
+- **Write commit subjects in the repository's existing style**: imperative mood, describing the intent rather than the mechanics, no `feat:` / `fix:` prefixes. See `git log` for the established pattern — for example, `Report the whole turn's output tokens, not the last call's`.
+
+### 4.5 Pull request requirements
+
+Open the pull request against `master` and include all of the following:
+
+- **A `Type:` line as the first line of the description** — either `Type: feature` or `Type: fix`. This is how the contribution type is declared; a pull request without it is not reviewed.
+- **A closing reference to its issue** — `Closes #<issue-number>`. A pull request that closes no issue does not get merged.
+- **The matching label** — `feature` or `fix`, the same one carried by the issue.
+- **What changed and how you verified it** — including the `pnpm check` result, and the manual verification you performed in DSH Desktop for anything that touches the UI or the process lifecycle.
+- **A README update** when the change adds or alters user-visible behavior. New features belong in the Features list in §3.
+
+The type is declared through the label and the `Type:` line rather than a title prefix so that squashed commit subjects stay in the repository's plain imperative style.
+
+### 4.6 What gets rejected
+
+- A pull request with no accepted issue behind it, or with no declared type.
+- A feature and a fix bundled into one pull request.
+- Changes that patch DSH, reach into non-public DSH APIs, or re-implement Claude Code's agent loop.
+- A failing or unrun `pnpm check`.
+- Anything that logs, persists, or renders credentials, including in tests and fixtures.
+- Version bumps, release script edits, or publish attempts from a contribution branch.

package/lib/bin.mjs

@@ -1,10 +1,10 @@
 #!/usr/bin/env node
-import { i as parseClaudeVersion, n as ensureManagedPreset, r as removeManagedPreset } from "./preset-installer-CVdbU87E.mjs";
+import { i as parseClaudeVersion, n as ensureManagedPreset, r as removeManagedPreset } from "./preset-installer-BY4846KK.mjs";
 import { access } from "node:fs/promises";
 import { delimiter, isAbsolute, join } from "node:path";
+import { constants } from "node:fs";
 import { homedir } from "node:os";
 import { scrubbedParentEnv } from "@deepseek-ai/dsh-subprocess";
-import { constants } from "node:fs";
 import { spawnSync } from "node:child_process";
 //#region src/bin.ts
 function option(name) {

package/lib/client.d.ts

@@ -18,6 +18,9 @@ declare const en: {
   readonly toolInput: "Input";
   readonly toolOutput: "Output";
   readonly toolError: "Error";
+  readonly markdownCopy: "Copy";
+  readonly markdownCopied: "Copied";
+  readonly markdownFootnotes: "Footnotes";
   readonly tokens: "{count} tokens";
   readonly doctor: "Run Doctor";
   readonly refreshing: "Running Doctor…";
@@ -190,6 +193,12 @@ declare const en: {
   readonly diffTruncated: "The diff exceeds the safe display limit. Use the terminal to inspect the complete content.";
   readonly diffEmpty: "No tracked file changes to display";
   readonly diffMaximize: "Maximize diff panel";
+  readonly diffCommentPrevious: "Previous comment";
+  readonly diffCommentNext: "Next comment";
+  readonly diffCommentPosition: "Comment {index} of {total}";
+  readonly diffCommentCounter: "{index}/{total}";
+  readonly diffExpandAll: "Expand all files";
+  readonly diffCollapseAll: "Collapse all files";
   readonly diffRestore: "Restore diff panel";
   readonly diffCommit: "Commit";
   readonly diffCommitMenu: "Open commit actions";
@@ -200,7 +209,7 @@ declare const en: {
   readonly diffPushDescription: "Push local commits to the remote branch.";
   readonly diffPushAhead: "{count} unpushed commit(s)";
   readonly diffPushCompleted: "Pushed commit {commit}";
-  readonly diffGeneratingMessage: "Reading the repository and generating a commit message…";
+  readonly diffGeneratingMessage: "Suggesting a commit message. It only fills the fields you leave empty.";
   readonly diffActionFailed: "Repository action failed.";
   readonly diffIncludeUnstaged: "Include unstaged and untracked changes";
   readonly diffCommitMessage: "Commit message";
@@ -218,8 +227,8 @@ declare const en: {
   readonly diffSubmitting: "Working…";
   readonly diffDone: "Done";
   readonly diffCommitCompleted: "Created commit {commit}";
+  readonly diffPrCompleted: "Created the pull request — open it from the repository bar.";
   readonly diffCommitPreserved: "Local commit {commit} was preserved.";
-  readonly diffOpenPr: "Open pull request";
   readonly diffMergePr: "Merge";
   readonly repositoryMergeMenu: "Open merge options";
   readonly diffMerge_merge: "Create a merge commit";
@@ -314,6 +323,20 @@ declare const en: {
   readonly reviewCommentSubmit: "Comment";
   readonly reviewCommentCancel: "Cancel";
   readonly reviewCommentRemove: "Remove comment";
+  readonly reviewThreadReply: "Reply";
+  readonly reviewThreadBot: "Bot";
+  readonly reviewThreadAgo: "{age} ago";
+  readonly reviewThreadReplyTo: "Reply to @{author}";
+  readonly reviewThreadOpenOnGitHub: "Open on GitHub";
+  readonly reviewThreadSend: "Send reply";
+  readonly reviewThreadResolve: "Resolve";
+  readonly reviewThreadUnresolve: "Unresolve";
+  readonly reviewThreadResolved: "Resolved";
+  readonly reviewThreadOutdated: "Outdated";
+  readonly reviewThreadReplyPlaceholder: "Reply to this comment; type @ to mention someone";
+  readonly reviewThreadMention: "Mention a repository member";
+  readonly reviewThreadReplyFailed: "The reply could not be posted.";
+  readonly reviewThreadResolveFailed: "The thread could not be updated.";
   readonly reviewCommentFailed: "The comment could not be saved.";
   readonly reviewCommentsClear: "Clear all comments";
   readonly reviewCommentsSend: "Send comments";