feat: checkpoint list/info CLI commands

[greysonlalonde]

Summary

• crewai checkpoint list [location] — lists all checkpoints with timestamp, size, and task completion summary
• crewai checkpoint info [path] — shows details of a single checkpoint or the latest in a directory, including per-task status
• Reads checkpoint JSON metadata without full deserialization

Depends on #5318.

Test plan

• crewai checkpoint list ./checkpoints shows all files
• crewai checkpoint list defaults to ./.checkpoints
• crewai checkpoint info ./checkpoints shows latest
• crewai checkpoint info ./checkpoints/specific.json shows that file
• Empty directory prints "No checkpoints found"

---

Note

Low Risk
Low risk: additive, read-only CLI functionality that inspects local JSON/SQLite checkpoint files without modifying runtime behavior or persisted data.

Overview
Introduces a new crewai checkpoint CLI group with list and info commands for inspecting saved checkpoints.

The implementation adds checkpoint_cli.py, which detects whether a location is a JSON directory or a SQLite DB, extracts lightweight metadata (timestamp, event count, trigger type, and per-entity task completion), and prints either a summary list or detailed per-task status for the latest checkpoint or a specified db_path#checkpoint_id.

^{Reviewed by Cursor Bugbot for commit 7ccf811. Bugbot is set up for automated code reviews on this repo. Configure here.}

[iris-clawd]

Review: Checkpoint CLI

Clean, read-only CLI addition. Nice dual JSON/SQLite support with auto-detection via magic bytes.

Minor notes (non-blocking)

• _info_json_latest and _info_json_file will propagate exceptions uncaught (unlike _list_json which has a try/except). info_checkpoint catches for specific file but not for latest-in-directory. Consistency thing.
• _SELECT_ALL deserializes every checkpoint's json(data) to build the list. For large DBs with big payloads this could be slow. A SELECT id, created_at, length(data) FROM checkpoints would be lighter for the list view, then only deserialize when showing info. Fine for now.
• json(data) in the SQL assumes the column stores JSON text. If it's JSONB (per PR #5318's mention of JSONB), you may need json_extract or just read the raw column.

All minor — good to land. ✅

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 7ccf811. Configure here.}