jjhub 0.1.14 → 0.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jjhub",
-  "version": "0.1.14",
+  "version": "0.2.0",
   "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

@@ -51,7 +51,11 @@ repo delete                            hard-delete incl. op log (ops credential
 
 user list                              list known users (identity is GitHub-federated)
 
-change new <title> [--parent CHG-x] [--stack id]
+change new <title> [--parent CHG-x] [--stack id] [--route same-repo|unprojected|fork:<owner/name>]
+                                        --route (issue #277): same-repo is the default; unprojected
+                                        creates the change with no GitHub branch/PR ever; fork:<owner/name>
+                                        is recorded but refused at projection time until real fork-PR
+                                        projection ships
 change list
 change show <changeId>
 change describe <changeId> [--title t] [--description d]
@@ -59,33 +63,113 @@ change amend <changeId>
 change squash <changeId>
 change abandon <changeId>
 change restack <changeId>              rebase a needs-restack change onto its rewritten ancestor
-change commit <changeId> [<file...>] [-m msg] [--delete <path>]...
+change commit <changeId> [<file...>] [-m msg] [--delete <path>]... [--expect-head <sha>]
                                         commit working-tree files onto the change's branch;
-                                        --delete removes a path in the same commit (repeatable)
+                                        --delete removes a path in the same commit (repeatable);
+                                        --expect-head refuses (409) if the change moved since <sha>
+change propose <title> [<file...>] [--parent CHG-x] [--stack id] [-m msg]
+                        [--delete <path>]... [--expect-base <sha>]
+                                        issue #374: create + commit in one call, printing the diff
+                                        summary and PR link; --expect-base checks --parent's current
+                                        commit; on partial failure the error names the created change
+                                        id (still listed/abandon-able)
 change diff <changeId>                 per-file diffs of what the change contains
 change files <changeId>                list locally-stored files (contentMode "local" repos only)
-change land <changeId> [--force]       waits for real CI triggered by its own ready flip,
-                                        re-syncs a behind branch, then merges; --force bypasses
+change land <changeId> [--force] [--expect-head <sha>]
+                                        waits for real CI triggered by its own ready flip,
+                                        re-syncs a behind branch, then merges; --force bypasses;
+                                        --expect-head refuses (409) if the change moved since <sha>
+change enqueue <changeId>              add a review-ready pull request to GitHub's merge queue;
+                                        GitHub owns the merge from here, JJHub marks the change
+                                        landed once GitHub reports it merged
+change dequeue <changeId>              withdraw a JJHub-queued pull request back to explicit review
+change queue-status <changeId>         print the merge-queue receipt (position/state/merge-group
+                                        sha/checks/removed reason) plus whether GitHub auto-merge
+                                        is armed on the pull request
 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 actions cancel <changeId> <runId>
+                                        ask GitHub to cancel 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 recommend-reviewers <changeId>  advisory-only reviewer suggestions from CODEOWNERS, prior
+                                        review history, and recent file authorship — never requests
+                                        a reviewer; use "change reviewers" to see actual requests
+change review-health <changeId>        live GitHub review-collaboration summary: state, requested
+                                        reviewers, stale/dismissed approvals, unresolved threads,
+                                        CODEOWNERS evidence, and GitHub's effective merge requirement
+change landability <changeId>          show the effective GitHub landability policy report — every
+                                        gate's state and resolution, plus the overall verdict
+change projects <changeId>             show bounded GitHub Projects v2 evidence for linked issues
+change handoff <changeId>              durable task-handoff log (issue #373): findings, validation
+                                        evidence, outstanding work, or a verified commit SHA another
+                                        agent (or the same one later) can pick up without reconstructing
+                                        a chat transcript; works against a landed or abandoned change too
+change handoff <changeId> --add <kind> -m <body>
+                                        append one entry (never updates/deletes an existing one);
+                                        kind: note | status | question | decision | blocker | plan
+change deps <changeId>                 list a change's declared read-only external dependencies
+                                        (issue #277); with no flag, lists current state
+change deps <changeId> --set kind:owner/repo#ref [--set ...]
+                                        replace-all declaration of external dependency edges
+                                        (kind is issue|pull_request|release|bookmark); never itself
+                                        reads GitHub and never gates landing (advisory only)
+change deps <changeId> --refresh       best-effort live GitHub read of every declared dependency's
+                                        current state (open/closed, released/draft, exists/missing)
+change evolution <changeId>            auditable logical-change timeline (issue #275): kind, related
+                                        change ids, before/after evidence, remote recovery limits
+change recover <changeId> --keep left|right|both
+                                        resolve a recorded divergence (issue #275) between two live
+                                        changeIds that both claim the same underlying jj change id;
+                                        left/right abandons the other side, both marks it resolved
+                                        without abandoning either; refuses (409) if either is landed
 
 stack create <title> [--id x] [--changes CHG-1,CHG-2]
 stack list
 stack land <stackId> [--force]         same check-run gate as change land
+stack enqueue <stackId>                queue a LINEAR stack root->tip via change enqueue's own path;
+                                        refuses (409) before any GitHub call if the stack isn't linear
+                                        (a member with more than one parent, an unprojected member, or
+                                        a base that doesn't chain onto the previous member); prints each
+                                        member's own outcome (queued/skipped/failed) rather than an
+                                        all-or-nothing result
 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
+stack review-health <stackId>          per-member review-health summary, one batched round trip
+stack landability <stackId>            per-member effective GitHub landability policy report plus
+                                        the overall verdict, one batched round trip; a member blocked
+                                        behind an earlier, not-yet-landable member carries its own
+                                        "stack-order" requirement
+
+project rules list                     list this repo's Projects v2 lifecycle->field mapping rules
+project rules set --project <projectNodeId> --field <fieldNodeId> --option <optionId>
+                  --when <draft|in_review|queued|landed|abandoned|blocked> [--id <ruleId>] [--disabled]
+project rules delete <ruleId>
+project preview <changeId>             preview what "project apply" would do right now, without writing
+project apply <changeId>               evaluate and write matching rules now; automatic dispatch already
+                                        runs this on land
 
 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
+op diff <fromOpId> <toOpId>            structural diff between two operations' immutable snapshots
+                                        (which changes/stacks/bookmarks/conflicts were created,
+                                        modified, or removed); works for adjacent or far-apart ops
 undo [--force]                         refused when the head op is a "land" (real merge can't be unwound); --force reverts local state anyway
 redo
 
@@ -105,7 +189,18 @@ 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 (77 tools) for agent clients
+ai models --provider <p> [--api-key <key>] [--base-url <url>]
+                                        live model list for one AI provider (issue #472); the key
+                                        is used for this one request only and never saved. Without
+                                        --api-key, falls back to your already-saved AI connection's
+                                        key for that same provider, if any. Always succeeds — a
+                                        live-lookup failure shows source: static_fallback with a
+                                        detail message rather than an error, since a free-text model
+                                        id always works when configuring AI, listed or not
+ai status                               where AI is coming from for you: your own saved connection,
+                                        the server operator's default, or not configured at all
+
+mcp serve                              MCP server over stdio (125 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
@@ -124,13 +219,31 @@ topology <localRepoPath> [--engine subprocess]
 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
+revset <expression> --workspace <workspaceId> [--repo owner/name] [--limit N]
+    REMOTE form (issue #274): relays the query through the JJHub server to
+    that exact workspace's own "jjhub daemon" and polls for the result — use
+    when you're not on the machine with the workspace checked out. Slower
+    (bound by the daemon's sync interval) and needs that daemon healthy;
+    same result shape/error taxonomy as the local form above
 
 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
+    never implemented as a browser patch transform; records a durable receipt
+    on the JJHub server (best-effort — see "content receipts" below)
+content preview|apply --workspace <workspaceId> <split|absorb|squash|duplicate|restore>
+    --op <json> | (--source <jj-change-id> [--destination <jj-change-id>]
+    [--path <relative-path>]... [--title <title>]) [--expected-operation <id>]
+    REMOTE form (issue #276): relays the preview/apply through the JJHub server to
+    that exact workspace's own "jjhub daemon" and polls for the result — use
+    when you're not on the machine with the workspace checked out. jj's own
+    immutable-commits check and JJHub's landed-change guard both apply; a
+    successful apply also appends a durable content_op_receipts entry
+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`
@@ -200,6 +313,25 @@ npm run jjhub -- stack land "Fix bundle"
 
 A single change not part of a stack lands directly: `npm run jjhub -- change land CHG-1`.
 
+### Use GitHub's merge queue instead of a direct land
+
+When the target branch requires it, add a review-ready change to GitHub's
+merge queue rather than merging it directly — GitHub owns the merge from
+there, and JJHub only marks the change landed once GitHub reports it merged:
+
+```bash
+npm run jjhub -- change request-review CHG-1
+npm run jjhub -- change enqueue CHG-1
+npm run jjhub -- change queue-status CHG-1   # position/state/merge-group evidence,
+                                              # removal reason if GitHub removed it,
+                                              # and whether GitHub auto-merge is armed
+npm run jjhub -- change dequeue CHG-1        # withdraw back to explicit review
+```
+
+A change JJHub knows is queued cannot be rewritten (`describe`/`amend`/
+`restack`/...) or landed directly until it is dequeued — `change land`
+refuses with a message naming the queue.
+
 ### Sync a local jj working copy into JJHub
 
 ```bash
@@ -243,6 +375,15 @@ 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