jjhub 0.1.13 → 0.1.15

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jjhub",
-  "version": "0.1.13",
+  "version": "0.1.15",
   "description": "jjhub — GitHub CLI with Jujutsu-native superpowers: stable change IDs, stacks, platform-wide undo, and conflicts that wait, layered over plain GitHub repos by a JJHub server.",
   "bin": {
     "jjhub": "./dist/cli/jjhub.mjs"
@@ -10,7 +10,7 @@
     "node": ">=22.6.0"
   },
   "license": "UNLICENSED",
-  "homepage": "https://jjhub.johnhenry.me",
+  "homepage": "https://jjhub.erisera.com",
   "keywords": [
     "jujutsu",
     "jj",

package/skills/jjhub-cli/SKILL.md

@@ -68,6 +68,15 @@ change land <changeId> [--force]       waits for real CI triggered by its own re
                                         re-syncs a behind branch, then merges; --force bypasses
 change split <changeId> <newTitle>
 change checks <changeId>               list GitHub check runs for a change
+change actions <changeId>              show bounded GitHub Actions workflow and job evidence
+change actions rerun <changeId> <runId>
+                                        ask GitHub to re-run a workflow run shown by "change actions"
+change deployments <changeId>          show bounded GitHub deployment evidence
+change security <changeId>             show bounded GitHub code-scanning evidence
+change issues <changeId>               show linked GitHub issue context for a change
+change reviewers <changeId>            reviewer-routing audit trail: every request/remove that
+                                        actually succeeded against GitHub, who did it, and when
+change projects <changeId>             show bounded GitHub Projects v2 evidence for linked issues
 
 stack create <title> [--id x] [--changes CHG-1,CHG-2]
 stack list
@@ -75,11 +84,17 @@ stack land <stackId> [--force]         same check-run gate as change land
 stack delete <stackId>                 disband — members become loose changes (undoable)
 stack reorder <stackId> <changeId,changeId,...>
 stack checks <stackId>                 every member's GitHub check runs, one batched round trip
+stack issues <stackId>                 linked issue and external-blocker summary for a stack
 
 bookmark list
 bookmark delete <name> [--force]       --force required for the default (trunk) bookmark
 bookmark set <name> <tracked|view> [--target CHG-x]
 
+view save <name> <revsetExpression>    save a named jj revset expression for later reuse (storage
+                                        only — evaluate it with "jjhub revset")
+view list                              list saved views in this repo
+view delete <name>
+
 op log                                 "@" marks the current head operation
 undo [--force]                         refused when the head op is a "land" (real merge can't be unwound); --force reverts local state anyway
 redo
@@ -100,7 +115,7 @@ auth sessions                          list your live sessions; auth revoke <id>
 auth logout                            forget the saved connection/token
 auth status                            who the saved credential authenticates as
 
-mcp serve                              MCP server over stdio (59 tools) for agent clients
+mcp serve                              MCP server over stdio (86 tools) for agent clients
 mcp serve --http <port>                the same tools over Streamable HTTP (POST /)
 acp serve                              Agent Client Protocol agent over stdio (Zed's agent
                                        panel, ...) — every operation as a slash command
@@ -112,6 +127,24 @@ daemon <localRepoPath> [--once] [--interval 5] [--engine auto|subprocess|isomorp
 daemon start [alias|localRepoPath] [--interval 5] [--engine ...] [--two-way]
     spawn the same sync as a detached background process
 daemon stop [alias] | daemon status [alias]
+
+topology <localRepoPath> [--engine subprocess]
+    inspect explicit local remote/bookmark topology; never selects or rewrites a push route
+
+revset <localRepoPath> <expression> [--engine subprocess]
+    evaluate the installed jj binary's revset in exactly the named workspace;
+    this is local, read-only discovery rather than a server-side approximation
+
+content preview <localRepoPath> <split|absorb|squash|duplicate|restore>
+    --source <jj-change-id> [--destination <jj-change-id>] [--path <relative-path>]...
+content apply <localRepoPath> <split|absorb|squash|duplicate|restore>
+    same selection plus --expected-operation <jj-operation-id> returned by preview
+    local-only jj content curation; checked against jj's immutable policy and
+    never implemented as a browser patch transform; records a durable receipt
+    on the JJHub server (best-effort — see "content receipts" below)
+content receipts [--repo owner/name|repoId]
+    list this repo's content-op receipt trail: every content apply invocation,
+    successful or rejected, with its kind, revisions, and outcome
 ```
 
 Anything else (`pr`, `issue`, ...) is passed through to `gh` — e.g. `jjhub pr view 7`. `jjhub auth`
@@ -126,12 +159,12 @@ vars needed. `jjhub auth status` confirms what's currently in effect.
 
 ### Identity & permissions (issue #43: GitHub-federated)
 
-A JJHub user IS a GitHub account. `jjhub auth login` runs an OAuth device flow against the
+A JJHub user is a GitHub account. `jjhub auth login` runs an OAuth device flow against the
 JJHub server's own authorization server: open the printed URL, sign in with GitHub, confirm
 the code, and the CLI saves a JJHub-issued OAuth token. Every mutation is attributed to that
 identity (visible in `jjhub op log`).
 
-What you can do on a repo is asked of GitHub LIVE at request time (cached ~60s):
+What you can do on a repo is asked of GitHub live at request time (cached ~60s):
 GitHub `admin` → owner, `maintain`/`write` → writer, `triage`/`read` → reader. There is no
 internal membership table and nothing to manage in JJHub — manage collaborators on GitHub.
 
@@ -195,11 +228,49 @@ npm run jjhub -- daemon . --once      # one-shot sync; omit --once to loop every
 npm run jjhub -- op log               # verify the sync landed as a new operation
 ```
 
+### Discover local jj changes with a revset
+
+```bash
+npm run jjhub -- revset . 'mutable() & descendants(@-)'
+npm run jjhub -- revset . 'bookmarks() | remote_bookmarks()' --json
+```
+
+The expression is passed to the installed `jj` binary as one argument, never
+through a shell. The workspace path is explicit because `@`, aliases, and
+immutable boundaries are facts about that specific local workspace. This first
+read-only form does not send local commits or filesystem paths to JJHub.
+
+### Curate local change content
+
+```bash
+npm run jjhub -- content preview . split \
+  --source <jj-change-id> --title "Extract validation" --path src/checkout.ts
+npm run jjhub -- content apply . split \
+  --source <jj-change-id> --title "Extract validation" --path src/checkout.ts \
+  --expected-operation <operation-id-from-preview>
+```
+
+The non-interactive local surface delegates `split`, `absorb`, `squash`,
+`duplicate`, and `restore` to the installed jj binary with structured argument
+arrays. A preview's jj operation id is mandatory for apply, and immutable
+targets are refused without `--ignore-immutable`. `--path` selects complete
+relative paths; interactive hunk selection remains jj's configured diff editor.
+Run `jjhub daemon . --once` afterwards to reconcile the local graph.
+
+Each `content apply` invocation — successful or rejected (e.g. a stale
+`--expected-operation`) — records a durable receipt on the JJHub server
+(best-effort: a missing repo context or unreachable server only produces a
+warning, never blocks the local jj mutation). Review the trail with:
+
+```bash
+npm run jjhub -- content receipts
+```
+
 ### Resolve a conflict
 
 ```bash
 npm run jjhub -- conflict list                              # note the conflict id
-npm run jjhub -- conflict resolve CONFLICT-abc123 left       # or: right | edited | preserve_unresolved
+npm run jjhub -- conflict resolve <conflict-id> left         # or: right | edited | preserve_unresolved
 npm run jjhub -- conflict list                               # confirm it now reads Resolved
 ```