shipbench 0.1.0 → 0.2.0

package/dist/index.js

@@ -4810,7 +4810,7 @@ Visible order comes from \`config.json\`, the task files, and this partial index
 - The Uncategorized column and the \`done_column\` both ignore \`layout\` entirely.
 - The CLI and Board do not record \`layout[done_column]\`; any existing entry is removed on the next layout write.
 
-Do not read \`layout.json\` alone to determine board order. \`shipbench task list\` returns live tasks in canonical board order, and its JSON output includes each task's zero-based \`position\` within its column. Code clients can apply \`orderedTasksForColumn\` to the task files. Treat the index as machine-managed: do not hand-edit or hand-order it. You may gitignore it if ordering should stay machine-local, but Harbor and fresh clones will then fall back to deterministic \`created\`-descending order for unlisted tasks.
+Do not read \`layout.json\` alone to determine board order. \`shipbench task list --json\` returns live tasks in canonical board order, including each task's zero-based \`position\` within its column. Direct file readers must apply the rules above. Treat the index as machine-managed: do not hand-edit or hand-order it. You may gitignore it if ordering should stay machine-local, but Harbor and fresh clones will then fall back to deterministic \`created\`-descending order for unlisted tasks.
 
 ## Task files
 
@@ -4944,7 +4944,7 @@ Note that \`depends_on\` and the task's column are orthogonal. A column says whe
 
 \`layout.json\` is a partial, machine-managed index, not the visible order. It can omit \`done_column\`, unlisted tasks, and whole columns; retain stale slugs until another layout write; or be absent or gitignored. Reading it alone can therefore give the wrong answer.
 
-\`shipbench task list\` reports live tasks in configured column order and visible within-column order; JSON output includes each task's zero-based \`position\` within its column. Code clients can apply \`orderedTasksForColumn\` to the task files. When working directly with the plain files, combine task statuses with \`config.json\` and the ordering rules in \`README.md\`; do not use \`layout.json\` alone as the answer.
+\`shipbench task list --json\` reports live tasks in configured column order and visible within-column order, including each task's zero-based \`position\` within its column. When working directly with the plain files, combine task statuses with \`config.json\` and the ordering rules in \`README.md\`; do not use \`layout.json\` alone as the answer.
 
 ## Changing Board Order
 
@@ -6567,7 +6567,7 @@ async function runTui(options2) {
 }
 
 // src/cli.ts
-var VERSION = true ? "0.1.0" : "0.0.0-dev";
+var VERSION = true ? "0.2.0" : "0.0.0-dev";
 function commaList(value) {
   return value.split(",").map((s) => s.trim()).filter(Boolean);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "shipbench",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Git-native project management for solo developers. Your task board lives in your repository as Markdown.",
   "license": "MIT",
   "repository": {
@@ -33,14 +33,14 @@
   "dependencies": {
     "chokidar": "^5.0.0",
     "commander": "^15.0.0",
-    "@shipbench/board": "0.1.0"
+    "@shipbench/board": "0.2.0"
   },
   "devDependencies": {
     "@types/node": "^26.0.1",
     "gray-matter": "^4.0.3",
     "tsup": "^8.0.0",
     "typescript": "^5.5.0",
-    "@shipbench/core": "0.1.0"
+    "@shipbench/core": "0.2.0"
   },
   "scripts": {
     "build": "tsup",