@odarino/backlog.md 1.55.0 → 1.57.0-next.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -29,6 +29,8 @@ Homebrew and Nix install the upstream package, which does not have the fork feat
29
29
 
30
30
  - **Image zoom.** Click an image in a task, a document, or a decision to open it full screen. Zoom with the mouse wheel, a double-click, or a pinch. Drag to pan. Use the arrow keys to move between all images of the task.
31
31
  - **Image upload, paste, and drag-drop.** Paste a screenshot or drop image files into any task editor. The server compresses each image to WebP and saves it under `backlog/assets/images/<task-id>/`. Images that you add before a task has an ID go to `_unsorted/`, and they move to the task folder when you create the task. An image that another task also links is copied, not moved.
32
+ - **Image upload mode.** A dialog shows a preview of each image and lets you choose to convert it to WebP or keep the original. From the CLI, run `backlog asset add <file> [--task <id>] [--original]`. MCP uses `asset_add`.
33
+ - **Random task IDs.** Set `taskIdMode` to `random` (`backlog config set taskIdMode random`) to give new tasks a random 6-digit ID (100000-999999). The default is `sequential`. The mode applies to tasks only. Subtasks keep the `.1` form. Duplicate-ID repair and draft promotion still allocate IDs as before, and collisions across unsynced branches remain possible (repairable with the duplicate-ID repair).
32
34
  - **Image picker.** The image button in the editor toolbar opens a picker. Search, select, and insert existing images, or upload new ones.
33
35
  - **Workflow editor.** In Settings, add, rename, reorder, color, and delete statuses. A rename or delete rewrites the affected tasks in `tasks/`, `completed/`, and `archive/tasks/`. Status colors show on the board columns and in the task list.
34
36
  - **Clone task.** Copy a task into a new one from the task view (**Clone**), the CLI (`backlog task clone <id> [--title <title>]`), or MCP (`task_clone`). The copy keeps the content, labels, links, and checklists (unchecked), and resets the status (drafts stay drafts), due date, notes, summary, and comments.
@@ -0,0 +1,22 @@
1
+ {
2
+ "name": "backlog",
3
+ "harenApi": "1",
4
+ "description": "Two-way sync between haren tasks and a Backlog.md board",
5
+ "requires": [
6
+ {
7
+ "bin": "backlog",
8
+ "version": ">=1.57.0-0",
9
+ "install": "npm i -g @odarino/backlog.md"
10
+ }
11
+ ],
12
+ "setup": [
13
+ "sh -c 'if [ -f backlog/config.yml ] || [ -f backlog/config.yaml ] || [ -f .backlog/config.yml ] || [ -f .backlog/config.yaml ] || [ -f backlog.config.yml ] || [ -f backlog.json ]; then exit 0; fi; if git rev-parse --git-dir >/dev/null 2>&1; then backlog init \"$0\" --defaults; else backlog init \"$0\" --defaults --no-git; fi' '{{project}}'"
14
+ ],
15
+ "hooks": {
16
+ "session-start": "backlog haren-hook session-start",
17
+ "after-plan": "backlog haren-hook after-plan",
18
+ "on-task-status": "backlog haren-hook on-task-status"
19
+ },
20
+ "config": {},
21
+ "skills": ["skills/haren-board"]
22
+ }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@odarino/backlog.md",
3
- "version": "1.55.0",
3
+ "version": "1.57.0-next.0",
4
4
  "module": "src/cli.ts",
5
5
  "files": [
6
6
  "cli.js",
@@ -8,18 +8,20 @@
8
8
  "postuninstall.cjs",
9
9
  "package.json",
10
10
  "README.md",
11
- "LICENSE"
11
+ "LICENSE",
12
+ "haren-plugin.json",
13
+ "skills/"
12
14
  ],
13
15
  "bin": {
14
16
  "backlog": "cli.js"
15
17
  },
16
18
  "optionalDependencies": {
17
- "@odarino/backlog.md-darwin-arm64": "1.55.0",
18
- "@odarino/backlog.md-darwin-x64": "1.55.0",
19
- "@odarino/backlog.md-linux-arm64": "1.55.0",
20
- "@odarino/backlog.md-linux-x64": "1.55.0",
21
- "@odarino/backlog.md-windows-arm64": "1.55.0",
22
- "@odarino/backlog.md-windows-x64": "1.55.0"
19
+ "@odarino/backlog.md-darwin-arm64": "1.57.0-next.0",
20
+ "@odarino/backlog.md-darwin-x64": "1.57.0-next.0",
21
+ "@odarino/backlog.md-linux-arm64": "1.57.0-next.0",
22
+ "@odarino/backlog.md-linux-x64": "1.57.0-next.0",
23
+ "@odarino/backlog.md-windows-arm64": "1.57.0-next.0",
24
+ "@odarino/backlog.md-windows-x64": "1.57.0-next.0"
23
25
  },
24
26
  "scripts": {
25
27
  "postuninstall": "node postuninstall.cjs"
@@ -0,0 +1,20 @@
1
+ ---
2
+ name: haren-board
3
+ description: Use the Backlog.md board inside a haren project. Open the board, read task status, and change status through haren.
4
+ ---
5
+
6
+ # Backlog board for haren
7
+
8
+ haren syncs its planned features with Backlog.md tasks. Each synced task has the label `haren:<module>/<feature>`.
9
+
10
+ ## Open the board
11
+
12
+ - Terminal board: `backlog board`
13
+ - Web board: `backlog browser`
14
+
15
+ ## Rules
16
+
17
+ 1. In a haren session, change a feature status with the haren `update-tracking` skill. Do not change it with `backlog task edit`. haren then updates the board.
18
+ 2. A person can move a task on the board. haren reads the change at the next session start.
19
+ 3. haren owns the title, the description, and the dependencies of a synced task. Change them in the haren plan, not on the board.
20
+ 4. Do not remove the `haren:` label from a task. haren uses it to find the task.