Problem
The researcher/spec pipeline produces issue bodies with two `## Dependencies` sections: one from the spec template (meaning 'code dependencies to reuse,' line 185 of `.claude/commands/spec.md`) and one written by the LLM (meaning 'issue blockers'). The dependency graph parser warns on every poll cycle for all 18 affected issues.
Root Cause
The spec template (`.claude/commands/spec.md`) uses `## Dependencies` as a section header for code-level dependencies (existing services, utilities, patterns to reuse). The researcher LLM also writes a `## Dependencies` section listing issue-level blockers (`#NNN`). When both appear in the issue body, the dependency graph parser logs warnings and uses only the first section.
Solution
- Rename the spec template section from `## Dependencies` to `### Code Dependencies` (or similar) to disambiguate from the issue-level `## Dependencies` section that the dependency graph parser expects.
- Update `parse_dependencies()` in `sova/supervisor/dependency_graph.py` if needed to match the renamed section.
- Fix the 18 affected issue bodies on GitHub (batch edit to remove the duplicate section).
Affected Files
- `.claude/commands/spec.md` (line 185): rename section header
- `commands/spec.md` (distributable copy): mirror the change
- `sova/supervisor/dependency_graph.py` (line 441-454): verify parser still works
Scope
- Interactive session recommended: batch-editing 18 GitHub issue bodies requires human review.
- The fix is a one-line rename in the template + batch cleanup of existing issues.
Dependencies
None.
Problem
The researcher/spec pipeline produces issue bodies with two `## Dependencies` sections: one from the spec template (meaning 'code dependencies to reuse,' line 185 of `.claude/commands/spec.md`) and one written by the LLM (meaning 'issue blockers'). The dependency graph parser warns on every poll cycle for all 18 affected issues.
Root Cause
The spec template (`.claude/commands/spec.md`) uses `## Dependencies` as a section header for code-level dependencies (existing services, utilities, patterns to reuse). The researcher LLM also writes a `## Dependencies` section listing issue-level blockers (`#NNN`). When both appear in the issue body, the dependency graph parser logs warnings and uses only the first section.
Solution
Affected Files
Scope
Dependencies
None.