task-graph-mcp 0.5.0

MCP server for agent task workflows with phases, prompts, gates, and multi-agent coordination
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111

# Processes


Agent-targeted reference for project processes. Follow these procedures exactly when executing releases or maintaining the changelog.

## Release Process


### Pre-Release Checklist


Run all quality gates before any release:

1. **Tests, clippy, fmt**
   ```bash
   cargo fmt --check

   cargo clippy -- -D warnings

   cargo test

   ```

2. **test-coverage-pro skill** — Run to analyze coverage, identify gaps, and generate missing tests. Do not proceed if critical paths lack coverage.

3. **doc-sentinel skill** — Run to audit documentation quality, detect code-doc drift, and verify completeness. Fix any drift or gaps before release.

4. **Reconciliation** — Verify consistency across all project artifacts:
   - `CHANGELOG.md` includes all user-facing changes under the correct version heading
   - `README.md` feature table matches current capabilities
   - `README.md` MCP Tools table matches implemented tools (check `src/tools/`)
   - `README.md` MCP Resources table matches implemented resources (check `src/resources/`)
   - All files in `docs/` are current with the codebase — no stale references, no missing docs for new features
   - `Cargo.toml` version matches the release version

5. **Release build verification**
   ```bash
   cargo build --release

   ```

### User Testing


After all pre-release checks pass, push to origin and do hands-on testing before tagging. Do not proceed to publish until the user signs off.

1. **Core workflow** — Connect to the MCP server, run through create → claim → update → complete lifecycle.
2. **New features** — Exercise each feature added in this release (check CHANGELOG "Added" section).
3. **Subdirectory discovery** — Run the server from a git worktree or project subdirectory to confirm uptree project discovery finds the correct config and database.
4. **Subagent coordination** — Spin up multiple agents (coordinator + workers). Verify claiming, prompt delivery, file contention warnings, and cascade cancel work across agents.
5. **Timestamp display** — Confirm ISO 8601 format across `get`, `list_tasks`, `task_history`, `list_agents`.
6. **Resource discovery** — Verify MCP resources return correct data (`docs://overlays/list`, `config://current`, `docs://search/{query}`).
7. **Database error handling** — Test both expected errors and watch for unexpected ones:
   - **Expected errors**: Verify that invalid operations return clear error messages (e.g., claiming a task already claimed, transitioning to an invalid state, deleting a parent without `cascade=true`). The test suite should cover these with assertions on error messages.
   - **Unexpected errors**: Watch for FK constraint violations, SQL errors, or `INTERNAL_ERROR` codes during normal workflows. These indicate missing cleanup (e.g., tables with FKs lacking `ON DELETE CASCADE`) or ordering bugs. When found, fix the root cause, add a regression test, and document the scenario.
   - **Destructive operations**: `obliterate` (hard delete) and `cascade` operations must clean up all referencing tables. Test with tasks that have file_locks, attachments, and state transitions.

### Publish to crates.io


```bash
cargo publish --dry-run
cargo publish
```

### Publish to GitHub


1. Tag the release commit:
   ```bash
   git tag vX.Y.Z

   git push origin vX.Y.Z

   ```

2. Create a GitHub release:
   - Title: `vX.Y.Z`
   - Body: copy the relevant section from `CHANGELOG.md`
   - Attach cross-platform binaries:
     - Linux x86_64
     - macOS Intel (x86_64)
     - macOS ARM (aarch64)
     - Windows x86_64

### Publish to MCP Registry


The release workflow automatically builds MCPB bundles and attaches them to the GitHub release along with a generated `server.json` containing SHA-256 hashes.

To publish to the MCP registry after the GitHub release completes:

1. Download the `server.json` from the GitHub release page.
2. Authenticate (first time only):
   ```bash
   mcp-publisher login github

   ```
3. Publish:
   ```bash
   mcp-publisher publish

   ```

The `server.json` in the repo root is a template with placeholder hashes. The CI-generated version in each GitHub release contains the real hashes.

### Post-Release Verification


1. Verify crates.io install:
   ```bash
   cargo install task-graph-mcp

   ```
2. Check the GitHub release page — binaries, MCPB bundles, and release notes correct.
3. Verify MCP registry listing:
   ```
   https://registry.modelcontextprotocol.io/servers/io.github.Oortonaut/task-graph-mcp
   ```

## Changelog Process


Follow [Keep a Changelog](https://keepachangelog.com/) format.

- Update `CHANGELOG.md` as changes are made, not only at release time.
- Use these categories: **Added**, **Changed**, **Fixed**, **Removed**, **Deprecated**, **Security**.
- Each entry is a single line describing the user-facing effect.
- The `[Unreleased]` section accumulates changes between releases. At release, rename it to the version and add a fresh `[Unreleased]` heading.