backlog.md 0.1.0 → 0.1.3

package/.backlog/tasks/task-5 - cli-docs-decisions.md

@@ -1,57 +0,0 @@
----
-id: task-5
-title: "CLI: Implement Docs & Decisions CLI Commands (Basic)"
-status: Done
-assignee: []
-reporter: @MrLesk
-created_date: 2025-06-04
-labels: ["cli", "command"]
-milestone: "M1 - CLI"
-dependencies: ["task-3"]
----
-
-## Description
-
-Implement basic CLI commands for managing documentation and decision logs:
-
-- `backlog doc create <title> -p <path>` (to create a new documentation file)
-- `backlog doc create <title> --path <path>` (to create a new documentation file)
-- `backlog doc create <title>` (to create a new documentation file in the root folder)
-- `backlog doc list`
-- `backlog decision create <title>`
-- `backlog decision list`
-
-## Acceptance Criteria
-
-- [x] Creation and listing commands functional for docs and decisions.
-- [x] Files are created in the correct `.backlog/docs/` and `.backlog/decisions/` directories.
-
-## Implementation Notes
-
-All CLI commands for docs and decisions have been successfully implemented:
-
-**Document Commands (src/cli.ts:380-412):**
-- `backlog doc create <title>` - Creates docs in `.backlog/docs/` with auto-generated IDs
-- `backlog doc create <title> -p <path>` - Creates docs in subdirectories within `.backlog/docs/`  
-- `backlog doc list` - Lists all documents with ID and title
-- Documents use proper YAML frontmatter with id, title, type, created_date fields
-
-**Decision Commands (src/cli.ts:414-447):**
-- `backlog decision create <title>` - Creates decision logs in `.backlog/decisions/`
-- `backlog decision create <title> -s <status>` - Creates decisions with custom status (default: "proposed")
-- `backlog decision list` - Lists all decisions with ID and title  
-- Decisions use structured template with Context, Decision, Consequences sections
-
-**Core Functionality:**
-- Auto-incremental ID generation for both docs and decisions
-- Proper YAML frontmatter serialization via gray-matter library
-- Git auto-commit integration for created files
-- File sanitization for cross-platform compatibility
-- Comprehensive test coverage in cli.test.ts (lines 862-893)
-
-**File Structure:**
-- Documents: `.backlog/docs/{optional-path}/filename.md`
-- Decisions: `.backlog/decisions/decision-{id} - {title}.md`
-- Both support subdirectories and maintain consistent naming conventions
-
-All tests pass (33/33) confirming full functionality and adherence to acceptance criteria.

package/.backlog/tasks/task-50 - borders-&-padding.md

@@ -1,22 +0,0 @@
----
-id: task-50
-title: Borders & padding
-status: Done
-assignee: []
-created_date: '2025-06-11'
-updated_date: '2025-06-13'
-labels:
-  - enhancement
-dependencies: []
----
-
-## Description
-
-Goal: Give the detail view breathing room.
-
-Detailed work:
-- Wrap the entire detail pane in a box with border.type:\line\ and padding.left = 1.
-
-## Acceptance Criteria
-- [x] Snapshot shows 1-char margin at left.
-- [x] Border stays inside the right pane (not full-width).

package/.backlog/tasks/task-51 - code-path-styling.md

@@ -1,23 +0,0 @@
----
-id: task-51
-title: Code-path styling
-status: Done
-assignee: []
-created_date: '2025-06-11'
-updated_date: '2025-06-13'
-labels:
-  - enhancement
-dependencies: []
----
-
-## Description
-
-Goal: Make file paths stand out and easier to scan.
-
-Detailed work:
-- In the markdown transform, detect back-ticked paths like \.
-- Render them dim grey and place each on its own line if not already isolated.
-
-## Acceptance Criteria
-- [x] Regex captures 100% of code paths in test fixture.
-- [x] Visual diff shows dim-grey paths, separated from surrounding prose.

package/.backlog/tasks/task-52 - cli-filter-tasks-list-by-status-or-assignee.md

@@ -1,29 +0,0 @@
----
-id: task-52
-title: 'CLI: Filter tasks list by status or assignee'
-status: Done
-assignee:
-  - '@codex'
-created_date: '2025-06-13'
-updated_date: '2025-06-13'
-labels: []
-dependencies: []
----
-
-## Description
-
-Add filtering options to task list command
-
-## Acceptance Criteria
-- [x] `backlog task list --status "To Do"` filters by status
-- [x] `backlog task list --assignee user` filters by assignee
-
-## Implementation Notes
-
-Added filtering options to `backlog task list` command in `src/cli.ts:253-268`:
-- `--status <status>`: Filters tasks by exact status match
-- `--assignee <assignee>`: Filters tasks by assignee (checks if user is in assignee array)
-
-Both filters can be used together. Works with `--plain` and interactive UI modes.
-
-Tests added in `src/test/cli.test.ts:265-339` verify both filtering options.

package/.backlog/tasks/task-6 - cli-packaging.md

@@ -1,65 +0,0 @@
----
-id: task-6
-title: "CLI: Argument Parsing, Help, and Packaging"
-status: Done
-assignee: []
-reporter: @MrLesk
-created_date: 2025-06-04
-labels: ["cli", "command"]
-milestone: "M1 - CLI"
-dependencies: ["task-3"]
----
-
-## Description
-
-Implement robust CLI argument parsing (e.g., using `commander.js` or `yargs`).
-Provide helpful `--help` messages for all commands.
-Use `bun build --compile` to create a standalone executable.
-Define `bin` script in `package.json` for npm distribution.
-
-## Acceptance Criteria
-
-- [x] All commands have clear help messages.
-- [x] CLI arguments are parsed correctly.
-- [x] `bun build --compile` produces a working executable.
-- [x] `package.json` configured for CLI publishing.
-
-## Implementation Notes
-
-**CLI Framework & Argument Parsing (src/cli.ts:7-11):**
-- Implemented using Commander.js for robust argument parsing and command structure
-- All commands provide comprehensive help messages with `--help` flag
-- Supports command aliases (e.g., `task` and `tasks`)
-- Proper option parsing with short and long flags (e.g., `-d, --description`)
-
-**Help System:**
-- Main CLI help: `backlog --help` shows all available commands
-- Command-specific help: `backlog task --help`, `backlog doc --help`, etc.
-- Subcommand help: `backlog task create --help` shows create-specific options
-- All help messages include clear descriptions and usage examples
-
-**Build System (package.json:24):**
-- Dual build process: Node.js distribution + standalone executable
-- `bun build --compile` creates platform-specific binary (`cli/backlog`)
-- Node.js wrapper script (`cli/index.js`) for npm distribution
-- Automatic executable permissions (`chmod +x`) for both formats
-
-**NPM Distribution (package.json:6-8):**
-- `bin` field configured to point to `./cli/index.js`
-- Enables global installation via `npm install -g backlog.md`
-- Entry point uses ES modules with dynamic import for compatibility
-
-**Testing Coverage:**
-- `src/test/build.test.ts` validates compiled executable functionality
-- Tests verify help output and binary execution
-- All 111 tests pass including build verification
-- CLI integration tests cover all command argument parsing
-
-**Key Features Verified:**
-- Complex argument parsing: multi-flag commands work correctly
-- Help system: comprehensive documentation for all commands
-- Executable compilation: `./cli/backlog --help` functions properly
-- NPM compatibility: `./cli/index.js` works as distribution entry point
-- Cross-platform: builds succeed and tests pass on current platform
-
-This implementation provides a professional CLI experience with both standalone and npm distribution options.

package/.backlog/tasks/task-6.1 - cli-local-installation-support-for-bunx-npx.md

@@ -1,49 +0,0 @@
----
-id: task-6.1
-title: 'CLI: Local installation support for bunx/npx'
-status: Done
-assignee: []
-reporter: @MrLesk
-created_date: '2025-06-08'
-updated_date: '2025-06-09'
-labels:
-  - cli
-dependencies: []
-parent_task_id: task-6
----
-
-## Description
-
-Allow installing Backlog.md locally in JS projects so agents can run bunx/npx backlog create when global install isn't available.
-
-## Acceptance Criteria
-
-- [x] Remove `"private": true` from package.json to allow publishing
-- [x] Configure proper package name/scope for npm registry
-- [x] Test and verify `npx backlog` and `bunx backlog` work from any project directory
-- [x] Update documentation with local installation instructions
-
-## Implementation Notes
-
-**Package Configuration:**
-- `package.json` configured for npm publishing with proper `name`, `version` (0.1.0), and `bin` entry
-- `bin` field points to `./cli/index.js` enabling global CLI access after installation
-- Build script creates both Node.js bundle and compiled binary for distribution flexibility
-
-**Local Installation Support:**
-- Package installable via `npm install backlog.md --save-dev` or `bun add -d backlog.md`
-- CLI accessible through `npx backlog` and `bunx backlog` commands
-- Works from any directory within the project after local installation
-
-**Documentation:**
-- `readme.md` includes comprehensive local installation section (lines 15-30)
-- Documents both npm and bun installation methods
-- Provides clear usage examples for npx/bunx execution
-
-**Test Coverage:**
-- `local-install.test.ts` automatically tests both execution methods
-- Creates temporary project, builds tarball, installs locally, and verifies CLI functionality
-- Tests confirm `--help` output contains expected "Backlog project management CLI" text
-- Both npx and bunx execution paths validated in isolated environment
-
-The implementation ensures seamless local installation for projects where global CLI installation isn't available, particularly useful for AI agents working in constrained environments.

package/.backlog/tasks/task-6.2 - cli-github-actions-for-build-&-publish.md

@@ -1,64 +0,0 @@
----
-id: task-6.2
-title: 'CLI: GitHub Actions for Build & Publish'
-status: Done
-assignee: []
-reporter: '@MrLesk'
-created_date: '2025-06-09'
-updated_date: '2025-06-09'
-labels:
-  - ci
-dependencies: []
-parent_task_id: task-6
----
-
-## Description
-
-Set up continuous integration for the CLI. Use GitHub Actions to build the project with Bun, run tests, and publish the package to npm (and by extension Yarn) when a release tag is pushed.
-
-## Acceptance Criteria
-
-- [x] Workflow builds the CLI with `bun build` and runs tests
-- [x] Publishing step deploys to npm using `NODE_AUTH_TOKEN`
-- [x] Trigger on version tags like `v*.*.*`
-- [x] Documentation updated with release instructions
-
-## Implementation Notes
-
-**GitHub Actions Workflow (.github/workflows/ci.yml):**
-- Created comprehensive CI/CD pipeline with name "Build and Publish"
-- **Triggers**: Main branch pushes, pull requests, and version tags matching `v*.*.*` pattern
-- **Environment**: Runs on `ubuntu-latest` with Bun runtime setup via `oven-sh/setup-bun@v1`
-- **Build Process**: Executes `bun install`, `bun run build`, and `bun test` in sequence
-- **Publishing**: Conditional publishing to npm only when tags are pushed (`startsWith(github.ref, 'refs/tags/')`)
-
-**Build & Test Pipeline:**
-- **Dependencies**: `bun install` installs all project dependencies
-- **Build**: `bun run build` executes complex build script creating both Node.js bundle and compiled binary
-- **Testing**: `bun test` runs entire test suite (122+ tests) to ensure quality before publishing
-- **Build Artifacts**: Creates `cli/index.js` (Node.js entry point) and `cli/backlog` (standalone binary)
-
-**NPM Publishing Configuration:**
-- Uses `npm publish --access public` for publishing to npm registry
-- Authenticates via `NODE_AUTH_TOKEN` environment variable from GitHub secrets
-- Package configured with `"name": "backlog.md"` and proper `bin` entry pointing to `./cli/index.js`
-- Version controlled via `package.json` version field (currently 0.1.0)
-
-**Documentation & Release Process (readme.md:245-257):**
-- Added comprehensive "Release" section with step-by-step instructions
-- **Process**: Update version in package.json → Commit changes → Create git tag → Push tag
-- **Automation**: Git tag push automatically triggers GitHub Actions workflow
-- **Security**: Workflow uses repository `NODE_AUTH_TOKEN` secret for secure npm publishing
-
-**Quality Assurance:**
-- Workflow validates build process before any publishing attempt
-- All tests must pass before package publication
-- Conditional publishing prevents accidental releases from non-tag pushes
-- Multi-trigger setup enables CI validation on PRs and main branch changes
-
-**Future Considerations:**
-- Workflow ready for production use with proper security practices
-- Supports semantic versioning via git tags (v1.0.0, v2.1.3, etc.)
-- Can be enhanced with version consistency validation and artifact retention if needed
-
-The implementation provides a complete automated CI/CD pipeline that builds, tests, and publishes the Backlog.md CLI package to npm whenever a version tag is pushed, ensuring quality releases with minimal manual intervention.

package/.backlog/tasks/task-7 - cli-kanban-view.md

@@ -1,60 +0,0 @@
----
-id: task-7
-title: "Kanban Board: Implement CLI Text-Based Kanban Board View"
-status: Done
-assignee: []
-reporter: "@MrLesk"
-created_date: 2025-06-04
-updated_date: 2025-06-09
-completed_date: 2025-06-09
-labels: ["cli", "command"]
-milestone: "M2 - CLI Kanban Board"
-dependencies: ["task-3"]
----
-
-## Description
-
-Design and implement a CLI command (`backlog board view` or similar) that reads tasks from `.backlog/tasks/` and displays them in a simple text-based Kanban board format in the terminal. Columns should be derived from task statuses.
-
-## Acceptance Criteria
-
-- [x] Command parses task files and groups them by status.
-- [x] Output is a readable text-based representation of the Kanban board.
-- [x] Columns are dynamically generated.
-
-## Implementation Notes
-
-**Core Implementation (src/board.ts):**
-- `generateKanbanBoard()` function creates text-based kanban board from task array
-- Dynamically groups tasks by status using Map for efficient lookup
-- Respects configured status order from project config (`config.yml`)
-- Auto-adjusts column widths based on longest content (status name or task title)
-- Handles empty task lists by showing configured status columns
-- Supports tasks with missing/empty status under "No Status" column
-
-**CLI Integration (src/cli.ts:380-399):**
-- Added `backlog board view` command with proper help documentation
-- Loads tasks from filesystem and project configuration
-- Gracefully handles empty projects with "No tasks found" message
-- Integrates with existing Core/FileSystem infrastructure
-
-**Algorithm Features:**
-- Column-based layout with proper padding and separators
-- Maintains visual alignment with calculated column widths
-- Status ordering: configured statuses first, then any unrecognized statuses
-- Clean table format: header row, separator line, task rows
-- Multi-line task display: task ID on first line, title on second line
-- Empty rows between tasks for improved readability
-- Screen-friendly format that accommodates long task titles
-
-**Test Coverage (src/test/board.test.ts + src/test/cli.test.ts):**
-- Unit tests for core board generation function (5 test cases)
-- Integration tests for CLI board command (2 test cases)
-- Edge cases: empty tasks, no status, long titles, status ordering
-- Comprehensive verification of board structure and content
-
-**Export Integration (src/index.ts:25):**
-- Function exported for reuse in other modules
-- Follows project's modular architecture pattern
-
-The implementation provides a professional text-based kanban view that works seamlessly with the existing CLI infrastructure and maintains visual consistency across different terminal widths.

package/.backlog/tasks/task-7.1 - cli-kanban-board-detect-remote-task-status.md

@@ -1,62 +0,0 @@
----
-id: task-7.1
-title: 'CLI: Kanban board detect remote task status'
-status: Done
-assignee: []
-reporter: @MrLesk
-created_date: '2025-06-09'
-updated_date: '2025-06-09'
-labels: []
-dependencies: []
-parent_task_id: task-7
----
-
-## Description
-
-Improve the Kanban board command so it checks all branches on the `origin`
-remote for task updates before rendering the board. Use `git fetch` to get the
-latest references and then iterate through each branch to collect task files
-using `git ls-tree`. Retrieve each task file with `git show` and merge the most
-recent status into the board view. If multiple branches contain the same task,
-adopt the frontmatter from the task that supplies the latest status so fields
-like `title` and `assignee` remain current.
-
-Status conflicts can occur when the same task has different status values in
-multiple branches. In that case always display the last status found in the
-iteration order and respect the status sequence defined in `config.yml`.
-All frontmatter fields should also come from the task file that provided the
-chosen status.
-
-## Acceptance Criteria
-
-- [x] `backlog board view` fetches and scans every branch under `origin` for task files.
-- [x] The displayed status for each task reflects the most recent entry across all branches.
-- [x] Status columns follow the configured order and fall back to the last seen status on conflicts, copying the full frontmatter from the task that provided the displayed status.
-
-## Implementation Notes
-
-Added remote task status detection to the CLI kanban board view. Key technical details:
-
-**Git Operations Enhanced:**
-- Added `fetchRemote()`, `listRemoteBranches()`, `listFilesInTree()`, and `showFile()` methods to `GitOperations` class in `src/git/operations.ts`
-- These methods use git commands: `fetch`, `branch -r`, `ls-tree -r --name-only`, and `show` respectively
-
-**Board View Logic (src/cli.ts:428-454):**
-- Fetches latest remote references using `core.gitOps.fetchRemote()`
-- Iterates through all remote branches from `core.gitOps.listRemoteBranches()`
-- For each branch, scans `.backlog/tasks` directory using `core.gitOps.listFilesInTree()`
-- Retrieves and parses task files using `core.gitOps.showFile()` and `parseTask()`
-- Merges task status based on configured status order - later statuses override earlier ones
-- Preserves all frontmatter (title, assignee, etc.) from the task providing the winning status
-- Gracefully handles remote access errors (offline scenarios, missing remotes)
-
-**Status Conflict Resolution:**
-- Uses `statuses.indexOf()` to determine status progression order from config.yml
-- Condition `newIdx > currentIdx || currentIdx === -1 || newIdx === currentIdx` ensures the most advanced status wins
-- When status indices are equal, the last seen task (iteration order) takes precedence
-- Entire task object is replaced (not just status) to maintain frontmatter consistency
-
-**Testing:**
-- Comprehensive test in `src/test/cli.test.ts` verifies remote status merging with bare git repositories
-- Test creates a feature branch with updated task status and verifies main branch picks up the advanced status
-

package/.backlog/tasks/task-8 - gui-project-setup.md

@@ -1,21 +0,0 @@
----
-id: task-8
-title: "GUI: Setup GUI Project Structure"
-status: "To Do"
-assignee: []
-reporter: @MrLesk
-created_date: 2025-06-04
-labels: ["gui", "setup"]
-milestone: "M3 - GUI"
-dependencies: ["task-7"]
----
-
-## Description
-
-Initialize the GUI project using Tauri. Integrate the core logic library. Set up basic window layout and navigation placeholders.
-
-## Acceptance Criteria
-
-- [ ] GUI project created with Tauri.
-- [ ] Core logic library successfully imported and usable.
-- [ ] Basic application window opens.

package/.backlog/tasks/task-9 - gui-task-crud.md

@@ -1,24 +0,0 @@
----
-id: task-9
-title: "GUI: Implement GUI Task Creation/Editing Forms"
-status: "To Do"
-assignee: []
-reporter: @MrLesk
-created_date: 2025-06-04
-labels: ["gui"]
-milestone: "M3 - GUI"
-dependencies: ["task-8"]
----
-
-## Description
-
-Create forms/modals in the GUI for:
-
-- Creating new tasks (as active tasks or draft).
-- Editing existing tasks (all fields from frontmatter and description).
-- All operations should use the core logic library to update Markdown files and commit.
-
-## Acceptance Criteria
-
-- [ ] Task creation form works and saves new tasks.
-- [ ] Task editing form loads existing task data and saves changes.