Inconsistent and non-standard Markdown checkbox format in newTrack directive

[pigochu]

The current system directive for the newTrack workflow (Section 2.4.6) forces a header-based checkbox format
which is non-standard and breaks visual rendering in IDEs like VS Code.

Steps to Reproduce:

1. Execute the /conductor:newTrack command.
2. The agent follows the directive to append the new track using the format: ## [ ] Track: <Description>
3. Open the tracks.md file in VS Code or any GitHub-flavored Markdown preview.

Actual Behavior:
The [ ] is rendered as plain text inside a header tag. No checkbox icon is displayed.

Expected Behavior:
The track should be appended as a list item to comply with GFM (GitHub Flavored Markdown) standards, ensuring
that checkbox icons are rendered correctly.
Suggested format:

Active Tracks

• Track:
  Link: path

Environment:

• Extension: Conductor Spec-driven Development Framework
• IDE: VS Code
• OS: Linux/macOS/Windows