History of executed requests

[syncended]

Goal

Track the requests a user has actually executed (not just saved templates) so they can review, replay, and inspect past calls.

Status

Candidate for v0.2. Decision pending — may move into v0.1.0 if TUI main screen needs it for the landing list.

Scope (draft)

• Append-only history log on disk (likely JSONL at `<storage.path>/history.jsonl`).
• Entry fields: id, timestamp, method, url, request headers + body, response status + headers + body (or pointer), elapsed time, error (if any).
• Configurable retention (max entries / max disk size) — default sane.
• CLI:
  • `yapi history` — list recent entries.
  • `yapi history show ` — view full entry.
  • `yapi replay ` — re-execute the request.
• TUI: history panel on the main screen.

Out of scope

• Search/filter UI beyond basic listing.
• Sync between machines.

Acceptance criteria

• Every executed request (CLI and TUI) is appended to the history log.
• A user can list and replay past requests.
• History storage location is governed by the storage settings (Settings: configurable storage location for request data #7).