batuta 0.6.2

Orchestration framework for converting ANY project (Python, C/C++, Shell) to modern Rust
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

# PMAT Bug Report

**Repository:** paiml/paiml-mcp-agent-toolkit

## Bug: `pmat work` commands fail to load roadmap after `pmat work init`

### Environment
- PMAT version: v2.198.0
- OS: Linux 4.4.0
- Rust: 1.75+

### Steps to Reproduce

1. Initialize a new git repository
2. Run `pmat work init`
   - Output: "✅ Created roadmap: ./docs/roadmaps/roadmap.yaml"
   - Output: "✅ Installed commit-msg hook"
3. Verify roadmap file exists:
   ```bash
   ls -la docs/roadmaps/roadmap.yaml
   # File exists with proper content
   ```
4. Try to check status:
   ```bash
   pmat work status
   ```

### Expected Behavior
`pmat work status` should load and display the roadmap from `docs/roadmaps/roadmap.yaml`

### Actual Behavior
```
Error: Failed to load roadmap. Run `pmat work init` first.
```

Alternatively, when using other subcommands:
```bash
pmat roadmap status --format table
# Error: Failed to read roadmap from docs/execution/roadmap.md
```

### Issue Analysis
There appears to be a mismatch in expected roadmap locations:
- `pmat work init` creates: `./docs/roadmaps/roadmap.yaml`
- `pmat work status` tries to load from: Unknown (fails to load)
- `pmat roadmap status` tries to load from: `docs/execution/roadmap.md`

### Impact
- Users cannot use `pmat work start <ticket-id>` to begin work
- Users cannot check work status
- Workflow tracking is broken despite successful initialization

### Workaround
None found. Users can manually reference tickets in commit messages (the commit-msg hook works correctly), but cannot use the workflow tracking features.

### Suggested Fix
Standardize on a single roadmap location:
1. Either use `docs/roadmaps/roadmap.yaml` everywhere, OR
2. Update `pmat work init` to create the file where other commands expect it

### Additional Context
The commit-msg hook (installed by `pmat work init`) correctly looks for the roadmap at `docs/roadmaps/roadmap.yaml`:
```bash
ROADMAP="docs/roadmaps/roadmap.yaml"
```

This suggests `docs/roadmaps/roadmap.yaml` should be the canonical location.

### Files Attached
- Roadmap file: `/home/user/Batuta/docs/roadmaps/roadmap.yaml`
- Commit hook: `/home/user/Batuta/.git/hooks/commit-msg`