Version Packages (#1613)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Ralph Khreish <35776126+Crunchyman-ralph@users.noreply.github.com>

.changeset/add-mcpb-bundle.md

@@ -1,10 +0,0 @@
----
-"task-master-ai": minor
----
-
-Add MCPB bundle for single-click Claude Desktop installation
-
-- Added `manifest.json` for MCP Bundle (MCPB) specification v0.3
-- Added `.mcpbignore` to exclude development files from bundle
-- Added `icon.png` (512x512) for Claude Desktop display
-- Enables users to install Task Master MCP server directly in Claude Desktop without manual configuration

.changeset/add-modifyjson-utils.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Add modifyJSON function for safer file updates

.changeset/cuddly-wings-drop.md

@@ -1,9 +0,0 @@
----
-"task-master-ai": minor
----
-
-Add verbose output mode to loop command with `--verbose` flag
-
-- New `-v, --verbose` flag shows Claude's work in real-time (thinking, tool calls) rather than waiting until the iteration completes
-- New `--no-output` flag excludes full Claude output from iteration results to save memory
-- Improved error handling with proper validation for incompatible options (verbose + sandbox)

.changeset/fair-heads-report.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Add --no-banner to suppress the startup banner.

.changeset/task-metadata-field.md

@@ -1,40 +0,0 @@
----
-"task-master-ai": minor
----
-
-Add optional `metadata` field to tasks for storing user-defined custom data
-
-Tasks and subtasks now support an optional `metadata` field that allows storing arbitrary JSON data such as:
-- External IDs (GitHub issues, Jira tickets, Linear issues)
-- Workflow data (sprints, story points, custom statuses)
-- Integration data (sync timestamps, external system references)
-- Custom tracking (UUIDs, version numbers, audit information)
-
-Key features:
-- **AI-Safe**: Metadata is preserved through all AI operations (update-task, expand, etc.) because AI schemas intentionally exclude this field
-- **Flexible Schema**: Store any JSON-serializable data without schema changes
-- **Backward Compatible**: The field is optional; existing tasks work without modification
-- **Subtask Support**: Both tasks and subtasks can have their own metadata
-- **MCP Tool Support**: Use `update_task` and `update_subtask` with the `metadata` parameter to update metadata (requires `TASK_MASTER_ALLOW_METADATA_UPDATES=true` in MCP server environment)
-
-Example usage:
-```json
-{
-  "id": 1,
-  "title": "Implement authentication",
-  "metadata": {
-    "githubIssue": 42,
-    "sprint": "Q1-S3",
-    "storyPoints": 5
-  }
-}
-```
-
-MCP metadata update example:
-```javascript
-// With TASK_MASTER_ALLOW_METADATA_UPDATES=true set in MCP env
-update_task({
-  id: "1",
-  metadata: '{"githubIssue": 42, "sprint": "Q1-S3"}'
-})
-```