Structured progress logging

[adamdaum]

Summary

Progress is currently tracked in a free-form progress.txt file. This makes it difficult to parse programmatically, build dashboards, or analyze loop performance over time.

Current Behavior

• Agents append free-text session notes to progress.txt (Step 8 of coding prompt)
• No consistent format or schema
• Feature status is tracked separately in feature_list.json but not correlated with timing or iteration data
• No machine-readable log of what happened per iteration

Proposal

Replace or supplement progress.txt with a structured log file (e.g., progress.json or progress.jsonl):

{
  "iteration": 3,
  "timestamp": "2025-06-08T14:32:00Z",
  "feature_id": "API-001",
  "status": "completed",
  "duration_seconds": 145,
  "tests_passed": true,
  "commit_sha": "abc123f",
  "notes": "Implemented REST endpoints for item CRUD"
}

• Each iteration appends one entry (JSONL format for easy streaming)
• Update coding_prompt.md to instruct agents to write structured entries
• Add a summary command that reads the log and prints stats (features done, avg time, success rate)
• Optionally, serve a local HTML dashboard that reads the log

Considerations

• JSONL is append-friendly and works well with streaming
• Keep progress.txt as an optional human-readable companion if desired
• The structured log enables future analytics and monitoring integrations