@bumpyclock/tasque-linux-x64-gnu 0.4.1 → 0.5.1

package/SKILLS/tasque/references/command-reference.md

@@ -5,8 +5,14 @@ Read when: you need exact command syntax or available options.
 ## Core workflow
 
 - `tsq` (no args, TTY): open read-only TUI
-- `tsq init [--wizard|--no-wizard] [--yes] [--preset <name>] [--sync-branch <branch>]`
+- `tsq init [--wizard|--no-wizard] [--yes] [--preset <name>] [--sync-branch|--worktree-name <name>]`
 - `tsq init --install-skill|--uninstall-skill [--skill-targets ...] [--skill-name <name>] [--force-skill-overwrite]`
+
+In git repos, `tsq init` defaults to sync-worktree mode using `tsq-sync`.
+Use `--sync-branch <name>` or `--worktree-name <name>` to choose another branch/worktree. Existing main-tree
+`.tasque` data migrates automatically. Fresh clones fetch the configured sync branch
+and create the worktree on first use. Non-git directories use local `.tasque/` storage.
+
 - `tsq create [<title>] [--child <title> ...] [--kind ...] [-p ...] [--parent <id>] [--description <text>] [--external-ref <ref>] [--discovered-from <id>] [--planning <needs_planning|planned>] [--needs-planning] [--ensure] [--id <tsq-xxxxxxxx>] [--body-file <path|->]`
 - `tsq show <id>`
 - `tsq list [--status ...] [--assignee ...] [--unassigned] [--external-ref <ref>] [--discovered-from <id>] [--kind ...] [--label ...] [--label-any ...] [--created-after <iso>] [--updated-after <iso>] [--closed-after <iso>] [--id <id,...>] [--planning <needs_planning|planned>] [--dep-type <blocks|starts_after>] [--dep-direction <in|out|any>] [--tree] [--full]`
@@ -51,7 +57,7 @@ Read when: you need exact command syntax or available options.
 - `tsq sync [--no-push]`
 - `tsq hooks install [--force]`
 - `tsq hooks uninstall`
-- `tsq migrate --sync-branch <branch>`
+- `tsq migrate [--sync-branch|--worktree-name <name>]`
 - `tsq merge-driver <ancestor> <ours> <theirs>`
 
 ## Global options and status alias

package/SKILLS/tasque/references/machine-output-and-durability.md

@@ -33,6 +33,11 @@ Error envelope:
 
 ## Storage model
 
+- Git repos default to sync-worktree mode on `tsq init`: the main worktree keeps
+  `.tasque/config.json`, while task data lives in `tsq-sync` unless
+  `--sync-branch` or `--worktree-name` names another branch/worktree. Existing main-tree `.tasque` data
+  migrates automatically when no `sync_branch` is configured. Fresh clones fetch
+  the configured sync branch and create the worktree on first use.
 - Canonical source of truth: `.tasque/events.jsonl` (append-only)
 - Derived cache: `.tasque/state.json` (rebuildable, gitignored)
 - Legacy cache fallback: `.tasque/tasks.jsonl` (read-only fallback when `state.json` is absent; removal target)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bumpyclock/tasque-linux-x64-gnu",
-  "version": "0.4.1",
+  "version": "0.5.1",
   "description": "Tasque binary for Linux x64 (glibc)",
   "license": "MIT",
   "repository": {
@@ -18,6 +18,7 @@
   ],
   "files": [
     "tsq",
+    "tsq-tui",
     "SKILLS/**"
   ],
   "publishConfig": {