Requests kept and replayed: keys requests per project with retention and a share, ctl request --body and --replay

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

docs/data.md

@@ -51,6 +51,11 @@ limits attached to it. Passwords are hashed.
 
 **Conversations and agent notes** — only for a project that asked. See below.
 
+**Kept requests** — only for a project that asked (`llmgw keys requests`):
+what each request sent the model, after the guardrails' redaction and with
+any stored conversation in it, and the answer the client got, for the hours
+it said, all of them or a share. Never under a `no_store` policy.
+
 **Batch files** — when a client uses the Batch API: the file of requests it
 uploaded (prompts) and the files the batch wrote (answers), in the store,
 until deleted (`DELETE /v1/files/{id}`) or, for what a batch wrote, until
@@ -61,7 +66,7 @@ them.
 ## What is not stored
 
 Prompts. Completions. Anything the model was shown or produced, unless the
-project turned on conversations or notes, or sent a batch.
+project turned on conversations, notes or kept requests, or sent a batch.
 
 The chat page in llmgw's own web interface keeps the conversation in a
 JavaScript variable in the browser. Refresh it and the conversation is gone,