Document daily report operations and templates

docs/operations.md

@@ -68,6 +68,10 @@ workspace/
       YYYY-MM-DD/
         <run_id>.modules.json
         <run_id>.metadata.json
+        <run_id>.generated_text.raw.json
+        <run_id>.generated_text.run.json
+        <run_id>.generated_text.json
+        <run_id>.render_context.json
     today/
       YYYY-MM-DD/
         <run_id>.modules.json
@@ -238,6 +242,8 @@ The default idempotency key appends RunID to the rendered bundle ID so each
 report generation has a distinct retry identity. The default bundle path uses
 the valid-period start date, artifact group, and RunID. Distributor owns
 destination merge, retention, and derived snapshot behavior such as `latest`.
+For Daily, the default report ID and artifact group values are both `daily`,
+and the default output filename value is `daily.md`.
 For Today, the default report ID and artifact group values are both `today`,
 and the batch output filename value is `today.md`.
 
@@ -311,7 +317,7 @@ A failed generation run may still leave useful artifacts:
   preflight JSON and metadata are written for inspection.
 - If `scriptorium run` exits nonzero after writing a report, the managed report
   and metadata remain available.
-- Generated-text failures for Today, Tomorrow, and Hourly reports preserve
+- Generated-text failures for Daily, Today, Tomorrow, and Hourly reports preserve
   available intermediate artifacts, such as the structured run result, raw
   generated-text JSON, validated generated text, and render context. Metadata
   links those paths when it can be safely written.