feat: squads log command — run history with timestamps, output paths, and exit status #692
Description
Problem
Users who return after their first run have no way to see what happened. There is no squads log or squads status showing recent run activity. Users can't tell if their agent ran, what it produced, or whether something broke — especially critical for scheduled runs.
Expected Behavior
squads log [--squad X] [--limit 10] shows recent runs:
squads log --limit 5
TIMESTAMP SQUAD AGENT DURATION STATUS OUTPUT
2026-04-07 09:02 product product-lead 2m 14s done briefs/daily-2026-04-07.md
2026-04-06 09:01 product product-lead 1m 58s done briefs/daily-2026-04-06.md
2026-04-05 09:03 product product-lead 3m 01s failed (see .squads/logs/...)
Why This Matters for D1 Retention
Every serious task runner (make, npm, docker, git log) has history. Without it:
- Users can't verify their scheduled run executed
- Returning users start blind (no continuity)
- Failed runs go unnoticed
This is the "did it work?" signal for users who are building the daily-run habit.
Scope
- Minimal: read from existing execution records (if they exist) or local log file
- Output: timestamp, squad, agent, duration, status, output path
- Flags:
--squad [name],--limit [n],--since [date] - No server required — local only
Source
Friction log FR-016 (product/friction-log/2026-04-07.md)