backlog.md 0.1.0 → 0.1.3

package/.backlog/tasks/task-36 - cli-prompt-for-project-name-in-init.md

@@ -1,24 +0,0 @@
----
-id: task-36
-title: 'CLI: Prompt for project name in init'
-status: Done
-assignee:
-  - '@codex'
-created_date: '2025-06-10'
-updated_date: '2025-06-10'
-labels: []
-dependencies: []
----
-
-## Description
-
-Allow `backlog init` to run without specifying a project name. When omitted, the CLI should prompt for the name before proceeding.
-
-## Acceptance Criteria
-- [x] `backlog init` works without project name parameter
-- [x] When project name is missing, CLI prompts for it before initialization
-- [x] Task committed to repository
-
-## Implementation Notes
-- Updated `src/cli.ts` to accept optional project name and prompt when omitted.
-- Added integration test covering prompt behavior in `src/test/cli.test.ts`.

package/.backlog/tasks/task-37 - cli-board-view-open-tasks-in-ide.md

@@ -1,19 +0,0 @@
----
-id: task-37
-title: 'CLI: Board view open tasks in IDE'
-status: In Progress
-assignee:
-  - '@AI'
-created_date: '2025-06-10'
-labels: []
-dependencies: []
----
-
-
-## Description
-
-Add clickable links to each task id in the board view that open the task file in the user's default IDE.
-
-## Acceptance Criteria
-- [ ] Every task id displayed in the board is a hyperlink that opens the task file in the configured IDE when clicked.
-- [ ] Provide a --no-links option to disable hyperlink generation.

package/.backlog/tasks/task-38 - cli-improved-agent-selection-for-init.md

@@ -1,25 +0,0 @@
----
-id: task-38
-title: 'CLI: Improved Agent Selection for Init'
-status: Done
-assignee:
-  - '@AI'
-created_date: '2025-06-10'
-updated_date: '2025-06-10'
-labels: []
-dependencies: []
----
-
-## Description
-Implement interactive checkbox-style selection for agents during 'backlog init'. Users should select one or multiple agents using space or enter, similar to modern CLI tools.
-
-## Acceptance Criteria
-- [x] Interactive checkbox UI replaces current agent selection
-- [x] Users can select one or multiple agents using space and confirm with enter
-- [x] Works consistently across Node and Bun runtimes
-- [x] Task committed to repository
-
-## Implementation Notes
-- Added `prompts` dependency for interactive CLI prompts.
-- Replaced numeric input with `multiselect` checkbox prompt in `src/cli.ts`.
-- Supports selecting multiple agent instruction files with space/enter.

package/.backlog/tasks/task-39 - cli-fix-empty-agent-instruction-files-on-init.md

@@ -1,31 +0,0 @@
----
-id: task-39
-title: 'CLI: fix empty agent instruction files on init'
-status: Done
-assignee:
-  - '@codex'
-reporter: '@MrLesk'
-created_date: '2025-06-10'
-updated_date: '2025-06-10'
-labels:
-  - cli
-  - bug
-dependencies: []
----
-
-## Description
-
-Backlog init should populate selected agent instruction files with default content instead of creating empty files.
-
-## Acceptance Criteria
-
-- [x] Selected agent instruction files contain default guideline text after running `backlog init`
-- [x] Automated test verifies non-empty content is written to each created file
-
-## Implementation Notes
-
-- Imported guideline constants may resolve to file paths when bundled. Added
-  `_loadAgentGuideline` helper to read file contents when needed.
-- `addAgentInstructions` now loads guideline text before writing files, ensuring
-  non-empty content in `AGENTS.md`, `CLAUDE.md`, and `.cursorrules`.
-- Updated CLI and tests to verify content length instead of specific words.

package/.backlog/tasks/task-4 - cli-task-management-commands.md

@@ -1,28 +0,0 @@
----
-id: task-4
-title: 'CLI: Task Management Commands'
-status: Done
-assignee: []
-reporter: '@MrLesk'
-created_date: '2025-06-04'
-updated_date: '2025-06-09'
-completed_date: '2025-06-09'
-labels:
-  - cli
-  - command
-milestone: M1 - CLI
-dependencies:
-  - task-3
----
-
-## Description
-
-Implement comprehensive task management functionality including creation, listing, viewing, editing, and archiving of tasks and drafts. This encompasses all user-facing CLI commands for task lifecycle management.
-
-## Implementation Notes
-
-- Subtasks **task-4.1** through **task-4.13** introduced complete CLI support for task and draft management.
-- Commands include `task create`, `task list`, `task view`, `task edit`, `task archive`, `task demote`, and draft variants.
-- Tasks can be created as subtasks using the `--parent` option and moved between draft and active states.
-- Metadata updates such as status and labels persist correctly through the `edit` command.
-- Extensive tests and documentation were added in each subtask to ensure reliability.

package/.backlog/tasks/task-4.1 - cli-task-create.md

@@ -1,27 +0,0 @@
----
-id: task-4.1
-title: "CLI: Task Creation Commands"
-status: Done
-assignee: @MrLesk
-reporter: @MrLesk
-created_date: 2025-06-04
-labels: ["cli", "command"]
-milestone: "M1 - CLI"
-dependencies: ["task-3"]
-parent_task_id: task-4
----
-
-## Description
-
-Implement commands for creating tasks, drafts, and subtasks:
-
-- `backlog task create` to add active tasks.
-- `backlog draft create` to create tasks in draft mode.
-- `backlog task create --parent <task-id>` to create a subtask under an existing task.
-
-## Acceptance Criteria
-
-- [x] Commands create Markdown files in the correct directories.
-- [x] Required metadata is captured from flags or prompts.
-- [x] Subtasks are saved using decimal IDs under `.backlog/tasks/`.
-- [x] Changes are committed with a descriptive message.

package/.backlog/tasks/task-4.10 - use-cli-to-mark-tasks-done.md

@@ -1,51 +0,0 @@
----
-id: task-4.10
-title: 'CLI: enforce Agents to use backlog CLI to mark tasks Done'
-status: Done
-assignee: []
-reporter: @MrLesk
-created_date: '2025-06-08'
-updated_date: '2025-06-09'
-labels:
-  - cli
-  - agents
-dependencies: []
-parent_task_id: task-4
----
-
-## Description
-
-Update agent guidelines so that after implementing and testing a task, they use the backlog CLI to set the task status to **Done**.
-
-## Acceptance Criteria
-- [x] Documentation instructs agents to run `backlog task edit <task-id> --status Done` after testing.
-- [x] Example usage included in AGENTS.md, CLAUDE.md and .cursorrules files
-
-## Implementation Notes
-
-**Task 4.10 Implementation Summary:**
-
-1. **Review Found Complete Implementation:**
-   - All agent guidance files already included the CLI command instruction
-   - Implementation was found to be complete during merge conflict resolution
-
-2. **Documentation Updates Applied:**
-   - **AGENTS.md**: Added CLI command instruction in guidelines section and Definition of Done
-   - **CLAUDE.md**: Added CLI command instruction in AI Agent Integration section  
-   - **.cursorrules**: Added CLI command instruction in Task Management section
-
-3. **Consistent Command Format:**
-   - All files now include the same command: `backlog task edit <task-id> --status Done`
-   - Command is presented in code blocks for clarity
-   - Instructions emphasize using this after implementing and testing tasks
-
-4. **Merge Conflict Resolution:**
-   - Resolved conflict in AGENTS.md by combining task 4.10 implementation with Definition of Done from main
-   - Ensured CLI command appears both in guidelines and Definition of Done for consistency
-
-5. **Quality Assurance:**
-   - All 105 tests pass
-   - Code passes all Biome linting and formatting checks  
-   - All agent guidance files now consistently instruct using the Backlog CLI
-
-All AI agents working with this project are now properly guided to mark tasks as Done using the CLI command, ensuring consistent workflow and proper task status management.

package/.backlog/tasks/task-4.11 - docs-add-definition-of-done-to-agent-guidelines.md

@@ -1,23 +0,0 @@
----
-id: task-4.11
-title: 'Docs: add definition of done to agent guidelines'
-status: Done
-assignee: []
-reporter: @MrLesk
-created_date: 2025-06-08
-updated_date: 2025-06-08
-labels:
-  - docs
-  - agents
-dependencies: []
-parent_task_id: task-4
----
-
-## Description
-
-Add 'Definition of Done' section to AGENTS.md, CLAUDE.md and .cursorrules.
-
-The Definition of done should be about verifying that all acceptance criteria are met, tests are implemented (when necessary) and checked, documentation is updated. Finally the task should be marked as done using the same Backlog CLI tool commands.
-
-## Acceptance Criteria
-- [x] Each file includes a Definition of Done

package/.backlog/tasks/task-4.12 - cli-handle-task-id-conflicts-across-branches.md

@@ -1,53 +0,0 @@
----
-id: task-4.12
-title: 'CLI: Handle task ID conflicts across branches'
-status: Done
-assignee: []
-reporter: @MrLesk
-created_date: '2025-06-09'
-labels: []
-dependencies: []
-parent_task_id: task-4
----
-## Description
-Implement detection of the latest task ID across all remote branches when creating a new task. The CLI should fetch branch references and inspect task files, similar to the kanban board remote status check, to determine the highest available ID before assigning the next one.
-
-## Acceptance Criteria
- - [x] `backlog task create` checks all remote branches for task files and chooses the next sequential ID.
- - [x] New tasks always use an ID higher than any found across branches to avoid conflicts.
-
-## Implementation Notes
-
-**Core Git Operations Added (src/git/operations.ts):**
-- `fetch(remote = "origin")`: Executes `git fetch` to update remote branch information
-- `listRemoteBranches(remote = "origin")`: Uses `git branch -r --list origin/*` to discover all remote branches
-- `listFilesInRemoteBranch(branch, path)`: Uses `git ls-tree -r origin/{branch} --name-only -- {path}` to list files in specific remote branch paths
-
-**Enhanced ID Generation (src/cli.ts:74-128):**
-- Modified `generateNextId()` to scan all remote branches for existing task IDs before assignment
-- Fetches latest remote branch information via `git fetch origin`
-- Iterates through all remote branches and scans `.backlog/tasks` directory for task files
-- Extracts task IDs using regex `/task-([\d.]+)/` pattern matching
-- Prevents ID collisions for both main tasks (`task-N`) and subtasks (`task-N.M`)
-- Gracefully handles git failures with try-catch, falling back to local-only ID generation
-
-**Comprehensive ID Conflict Prevention:**
-- Compares both local and remote task IDs to determine next available sequential ID
-- Handles subtask creation by checking parent task patterns across all branches
-- Ensures new task IDs are always higher than any found across local and remote sources
-- Maintains backward compatibility with existing local-only ID generation logic
-
-**Test Coverage (src/test/remote-id-conflict.test.ts):**
-- Creates comprehensive test scenario with bare git repository and remote branches
-- Sets up feature branch with task-1, then tests main branch task creation
-- Verifies that `backlog task create` correctly assigns task-2 (avoiding conflict with remote task-1)
-- Confirms CLI properly detects and respects remote task IDs during ID assignment
-- Test passes successfully, validating cross-branch ID conflict prevention
-
-**Quality Assurance:**
-- All 122 tests pass, including the new remote ID conflict test
-- Code passes all Biome linting and formatting checks
-- Implementation maintains existing functionality while adding robust remote branch support
-- Error handling ensures CLI remains functional even when git operations fail
-
-The implementation successfully prevents task ID conflicts across all repository branches, enabling safe collaborative development with distributed task creation across multiple feature branches.

package/.backlog/tasks/task-4.13 - cli-fix-config-command-local-global-logic.md

@@ -1,58 +0,0 @@
----
-id: task-4.13
-title: 'CLI: Fix config command local/global logic'
-status: Done
-assignee: []
-created_date: '2025-06-09'
-updated_date: '2025-06-09'
-labels: []
-dependencies: []
-parent_task_id: task-4
----
-
-## Description
-
-Fix config commands to correctly use local or global config files
-
-## Acceptance Criteria
-- [x] `backlog config set <key> <value> --local` saves changes to `.backlog/config.yml`.
-- [x] `backlog config set <key> <value> --global` saves changes to the user config file.
-- [x] `backlog config get <key>` checks local config first, then global config, then defaults.
-- [x] Behavior prioritizes local configuration over global and built-in defaults.
-- [x] Documentation updated to describe local and global configuration behavior.
-
-## Implementation Notes
-
-**CLI Command Implementation (src/cli.ts:497-548):**
-- Added `config get <key>` command that implements proper priority order: local config → global config → built-in defaults
-- Added `config set <key> <value>` command with `--local` and `--global` flags
-- `--local` flag (default behavior) saves to `.backlog/config.yml` in current project
-- `--global` flag saves to `~/.backlog/.user` in user's home directory
-- Built-in defaults include `statuses: ["Draft", "To Do", "In Progress", "Done"]` and `defaultStatus: "To Do"`
-
-**FileSystem Implementation (src/file-system/operations.ts:349-392):**
-- Added `getUserSetting(key, global)` method to read from user config files
-- Added `setUserSetting(key, value, global)` method to write to user config files
-- Global config stored in `~/.backlog/.user` (home directory)
-- Local config stored in `./.user` (project directory)
-- Supports key-value format with colon separation and optional quotes
-- Fixed `serializeConfig()` and `saveUserSettings()` to always include trailing newlines for proper file formatting
-
-**Configuration Priority Logic:**
-1. **Local config first**: Checks `.backlog/config.yml` for project-specific settings
-2. **Global config fallback**: Checks `~/.backlog/.user` for user-wide settings
-3. **Built-in defaults**: Falls back to hardcoded values for core settings like statuses
-
-**Documentation Updates (readme.md:176-179):**
-- Added explanation of `--local` (default) and `--global` flags
-- Documented priority order: local → global → defaults
-- Updated usage examples to show flag usage
-- Clarified behavior for both `config get` and `config set` commands
-
-**Quality Assurance:**
-- All filesystem tests pass, including new user config operations test
-- Manual testing confirms proper flag behavior and priority order
-- CLI help text includes proper flag documentation
-- Implementation maintains backward compatibility with existing config operations
-
-The config commands now correctly handle local/global configuration with proper precedence rules, enabling users to maintain both project-specific and user-wide settings.

package/.backlog/tasks/task-4.2 - cli-task-list-view.md

@@ -1,25 +0,0 @@
----
-id: task-4.2
-title: "CLI: Task Listing and Viewing"
-status: Done
-assignee: @MrLesk
-reporter: @MrLesk
-created_date: 2025-06-04
-labels: ["cli", "command"]
-milestone: "M1 - CLI"
-dependencies: ["task-4.1"]
-parent_task_id: task-4
----
-
-## Description
-
-Add commands to browse tasks:
-
-- `backlog task list` / `backlog tasks list` to show tasks.
-- `backlog task view <task-id>` or `backlog task <task-id>` to show a specific task.
-
-## Acceptance Criteria
-
-- [x] Listing shows tasks grouped by status.
-- [x] Viewing displays task details with Markdown formatting.
-- [x] Commands do not modify task files.

package/.backlog/tasks/task-4.3 - cli-task-edit.md

@@ -1,24 +0,0 @@
----
-id: task-4.3
-title: "CLI: Task Editing"
-status: Done
-assignee: @MrLesk
-reporter: @MrLesk
-created_date: 2025-06-04
-updated_date: 2025-06-08
-labels: [cli, command]
-milestone: "M1 - CLI"
-dependencies: [task-4.2]
-parent_task_id: task-4
----
-## Description
-
-Implement editing of existing tasks:
-
-- `backlog task edit <task-id>`
-
-## Acceptance Criteria
-
-- [x] Updates to title, description, status, labels, and assignee are persisted.
-- [x] The command respects YAML frontmatter formatting.
-- [x] A commit records the changes to the task file.

package/.backlog/tasks/task-4.4 - cli-task-archive-transition.md

@@ -1,27 +0,0 @@
----
-id: task-4.4
-title: "CLI: Task Archiving and State Transitions"
-status: Done
-assignee: @MrLesk
-reporter: @MrLesk
-created_date: 2025-06-04
-updated_date: 2025-06-08
-labels: ["cli", "command"]
-milestone: "M1 - CLI"
-dependencies: ["task-4.1"]
-parent_task_id: task-4
----
-
-## Description
-
-Add commands for finalizing and moving tasks:
-
-- `backlog task archive <task-id>` and `backlog draft archive <task-id>`
-- `backlog draft promote` (move a draft to tasks)
-- `backlog task demote` (move a task back to drafts)
-
-## Acceptance Criteria
-
-- [x] Archived tasks are moved to `.backlog/archive/` with history preserved.
-- [x] Promote/demote commands relocate files between drafts and tasks.
-- [x] Commits clearly state the action performed.

package/.backlog/tasks/task-4.5 - cli-init-prompts-for-reporter-name-and-global-local-config.md

@@ -1,28 +0,0 @@
----
-id: task-4.5
-title: "CLI: Init prompts for reporter name and global/local config"
-status: "Done"
-assignee: @MrLesk
-reporter: @MrLesk
-created_date: 2025-06-08
-updated_date: 2025-06-08
-labels: ["cli", "config"]
-milestone: "M1 - CLI"
-dependencies: ["task-3"]
-parent_task_id: task-4
----
-
-## Description
-
-Enhance `backlog init` with interactive prompts:
-
-- Ask for a default **reporter** name for new tasks.
-- Prompt whether to store this configuration globally or only for the current repository.
-- When storing locally, create a hidden `.user` settings file and make sure it is ignored by Git.
-
-## Acceptance Criteria
-
-- [x] Running `backlog init` asks for a default reporter name.
-- [x] User can choose between storing the reporter setting globally or locally.
-- [x] Choosing the local option creates a `.user` settings file and appends it to `.gitignore`.
-- [x] Reporter name saved based on the chosen scope.

package/.backlog/tasks/task-4.6 - cli-add-empty-assignee-array-field-for-new-tasks.md

@@ -1,35 +0,0 @@
----
-id: task-4.6
-title: "CLI: Add empty assignee array field for new tasks"
-status: Done
-assignee: @MrLesk
-reporter: @MrLesk
-created_date: 2025-06-08
-updated_date: 2025-06-08
-labels: ["cli", "command"]
-milestone: "M1 - CLI"
-dependencies: ["task-4.1"]
-parent_task_id: task-4
----
-
-## Description
-
-Ensure every task created via the CLI includes an empty `assignee` array in its frontmatter. Investigate the current parsing and serialization logic which uses a single string value. If assignees are not handled as an array, update the code to support `string[]`.
-
-## Acceptance Criteria
-
-- [x] New tasks contain `assignee: []` by default.
-- [x] Parsing and serialization read and write the assignee field as an array.
-- [x] Documentation provides instructions to migrate existing logic if needed.
-
-## Implementation Notes
-
-**YAML Flexibility Support**: Implemented proper YAML specification support where assignee field accepts both string and array formats. The parser (`src/markdown/parser.ts:19-23`) automatically normalizes single strings to arrays using `Array.isArray()` check.
-
-**Core Normalization**: Added assignee normalization in `createTask`, `createDraft`, and `updateTask` methods (`src/core/backlog.ts`) with biome-ignore comments for TypeScript `any` usage required for YAML flexibility.
-
-**CLI Integration**: Updated `buildTaskFromOptions` function (`src/cli.ts:108`) to create arrays by default, and edit command to handle array assignment properly.
-
-**Comprehensive Testing**: Fixed all 99 tests by adding missing `assignee: []` fields and updating expectations from `.toBe("string")` to `.toEqual(["string"])` to match array format.
-
-**Type Safety**: Maintained `Task` interface with `assignee: string[]` type while supporting both input formats through runtime normalization.

package/.backlog/tasks/task-4.7 - cli-parse-unquoted-created_date.md

@@ -1,40 +0,0 @@
----
-id: task-4.7
-title: "CLI: Parse unquoted created_date"
-status: Done
-assignee: @MrLesk
-reporter: @MrLesk
-created_date: 2025-06-08
-updated_date: 2025-06-08
-labels: ["cli", "command"]
-milestone: "M1 - CLI"
-dependencies: ["task-4.4"]
-parent_task_id: task-4
----
-
-## Description
-
-Support unquoted `created_date` values in task frontmatter. Accept multiple date formats:
-
-- `created_date: 2025-06-08`
-- `created_date: '2025-06-08'`
-- `created_date: 08-06-25`
-- `created_date: 08/06/25`
-- `created_date: 08.06.25`
-
-Allow configuration of the expected `date_format` in `.backlog/config.yml` with default `yyyy-mm-dd`.
-
-## Acceptance Criteria
-
-- [x] Unquoted dates are parsed correctly when viewing tasks.
-- [x] `date_format` option is documented in `config.yml`.
-
-## Implementation Notes
-
-**Date Normalization Function**: Implemented `normalizeDate` function in `src/markdown/parser.ts:4-33` that handles multiple date formats including unquoted values. The function supports `yyyy-mm-dd`, `dd-mm-yy`, `dd/mm/yy`, and `dd.mm.yy` formats with automatic normalization to ISO format.
-
-**Parser Integration**: The `parseTask` function uses `normalizeDate(frontmatter.created_date)` at line 56 to process date fields, ensuring consistent date handling across all task parsing operations.
-
-**Configuration Documentation**: Added `date_format` field documentation in `.backlog/docs/readme.md:15` and included `dateFormat: string` in the `BacklogConfig` interface for future extensibility.
-
-**Comprehensive Testing**: Added test cases in `src/test/markdown.test.ts:133-155` covering both unquoted dates (`created_date: 2025-06-08`) and short format dates (`created_date: 08-06-25`) with proper normalization verification.

package/.backlog/tasks/task-4.8 - cli-enforce-description-header.md

@@ -1,48 +0,0 @@
----
-id: task-4.8
-title: 'CLI: enforce description header'
-status: Done
-assignee: []
-reporter: @MrLesk
-created_date: 2025-06-08
-labels: []
-dependencies: []
-parent_task_id: task-4
----
-
-## Description
-
-Ensure new tasks have a Description header. Update docs to require acceptance criteria and tests.
-
-## Acceptance Criteria
-- [x] CLI automatically adds "## Description" when creating a task if missing.
-- [x] Documentation updated in AGENTS.md, CLAUDE.md, and .cursorrules to mandate acceptance criteria and relevant tests when necessary.
-
-## Implementation Notes
-
-**Task 4.8 Implementation Summary:**
-
-1. **Core Functionality (`src/core/backlog.ts`):**
-   - Implemented `ensureDescriptionHeader()` function that automatically adds "## Description" header to task descriptions if missing
-   - Integrated this function into all task creation and update methods: `createTask()`, `createDraft()`, and `updateTask()`
-   - Function intelligently handles empty descriptions and prevents duplicate headers
-
-2. **Test Coverage:**
-   - Existing tests for description header functionality were found in `src/test/core.test.ts`
-   - Tests verify both adding headers when missing and not duplicating existing headers
-   - Updated CLI integration tests to expect the new description header format in task descriptions
-
-3. **Documentation Updates:**
-   - Updated AGENTS.md, CLAUDE.md, and .cursorrules to explicitly mandate writing relevant tests when implementing new functionality or fixing bugs
-   - All three files already contained requirements for Description sections and Acceptance Criteria checklists
-
-4. **Merge Resolution:**
-   - Successfully resolved merge conflicts between task 4.8 (description header) and task 4.6 (assignee normalization)
-   - Both features now work together in all task creation/update methods
-
-5. **Quality Assurance:**
-   - All 104 tests pass, including the updated expectations for description headers
-   - Code passes all Biome linting and formatting checks
-   - Features work correctly across task creation, updating, and draft management
-
-The CLI now automatically ensures all tasks have proper "## Description" headers, improving consistency across the project's task management system.

package/.backlog/tasks/task-4.9 - cli-normalize-task-id-inputs.md

@@ -1,66 +0,0 @@
----
-id: task-4.9
-title: 'CLI: Normalize task-id inputs'
-status: Done
-assignee: []
-reporter: @MrLesk
-created_date: 2025-06-08
-labels:
-  - cli
-  - bug
-dependencies: []
-parent_task_id: task-4
----
-
-## Description
-
-Ensure parent task id uses task-<number> format and accept both forms across commands
-Using `--parent 4` results in `parent_task_id: '4'` but should result in `parent_task_id: 'task-4'`, while other tasks expect the `task-<number>` prefix.
-
-Update the CLI so that the parent ID is normalized to include the `task-` prefix when creating subtasks. All commands that accept a task ID should support both `task-<number>` and plain `<number>` inputs.
-
-## Current Status
-✅ `generateNextId()` already normalizes parent input: `task-4` or `4` → `task-4`  
-✅ `outputTask()` (view command) already normalizes: `task-4` or `4` → `task-4`  
-✅ `buildTaskFromOptions()` now normalizes parent input: `task-4` or `4` → `task-4`
-
-## Acceptance Criteria
-
-- [x] Normalize `parentTaskId` in `buildTaskFromOptions()` to always use `task-` prefix
-- [x] Test that `--parent 4` results in `parent_task_id: 'task-4'` in saved files
-- [x] Ensure all future commands accepting task IDs support both input formats
-
-## Implementation Notes
-
-**Task 4.9 Implementation Summary:**
-
-1. **Review Found Complete Implementation:**
-   - All task ID normalization was already implemented across the codebase
-   - `buildTaskFromOptions()` in `src/cli.ts` (lines 104-109) properly normalizes parent task IDs
-   - All CLI commands already support both `task-<number>` and plain `<number>` input formats
-
-2. **Comprehensive ID Normalization Coverage:**
-   - **`buildTaskFromOptions()`**: Normalizes `--parent 4` → `parentTaskId: 'task-4'`
-   - **`generateNextId()`**: Normalizes parent input for subtask ID generation
-   - **`outputTask()`**: Normalizes input for task view command
-   - **`loadTask()`**: Normalizes input for task loading operations
-   - **`archiveTask()`**: Normalizes input for task archiving
-   - **`demoteTask()`**: Normalizes input for task demotion
-   - **`promoteDraft()`**: Normalizes input for draft promotion
-
-3. **Test Coverage:**
-   - Found existing test in `src/test/parent-id-normalization.test.ts`
-   - Fixed test to include required `assignee` field (task 4.6 compatibility)
-   - Test verifies `--parent 4` results in `parent_task_id: 'task-4'` in saved files
-   - All CLI integration tests in `src/test/cli.test.ts` demonstrate ID normalization working
-
-4. **Configuration Cleanup:**
-   - Resolved merge conflicts in `biome.json` and removed redundant `.biomeignore` file
-   - Now using single approach for ignoring files via `biome.json` configuration
-
-5. **Quality Assurance:**
-   - All 105 tests pass including the parent ID normalization test
-   - Code passes all Biome linting and formatting checks
-   - All CLI commands uniformly accept both input formats
-
-The CLI now comprehensively normalizes all task ID inputs, ensuring consistent behavior across all commands while maintaining user-friendly input flexibility.