Add watch/phone icons and logo, reorder the interpretation report, and stamp every report with the day it's for

docs/input-output-format.md

@@ -171,7 +171,7 @@ cards rendered as an image:
 
 ### `--format json`
 
-A single JSON object mirroring `DailyReading` exactly — `natal`,
+A single JSON object mirroring `DailyReading` exactly — `date`, `natal`,
 `transits`, `spread` — using the **slug** accessors
 (`astro_body_slug()`, `astro_sign_slug()`, `astro_moon_phase_slug()`,
 `astro_aspect_slug()`, `tarot_card_slug()`, `tarot_position_slug()`)
@@ -182,6 +182,7 @@ read.
 
 ```json
 {
+  "date": "2026-07-16",
   "natal": {
     "bodies": [
       {"body": "sun", "sign": "taurus", "degree_in_sign": 23.4926, "ecliptic_longitude": 53.4926, "house": 3},
@@ -210,6 +211,13 @@ read.
 }
 ```
 
+- `date` is the UTC calendar date of `--date` (or the current system time
+  if `--date` was omitted) — the day this reading is *for*, not
+  necessarily the day it was generated on. `reading_generate()` stores
+  the full moment in `DailyReading.utc_moment`; only the date part is
+  serialized here since that's the only thing the rest of this format
+  (and the interpreter's own reports, which read this field back — see
+  "The interpreter" below) ever display.
 - `bodies` is always `NUM_BODIES` (10) entries, Sun..Pluto in `Body` enum
   order; `spread.positions` is always `TAROT_SPREAD_SIZE` (10) entries in
   `CelticCrossPosition` enum order (Present, Challenge, Crown,
@@ -279,11 +287,16 @@ dist/run-interpreter.sh html de      # override format/language for this run
 ### `--format text`
 
 A plain-text report, printed in a fixed order —
-  1. the day's overall significance level (`Quiet`/`Notable`/
+  1. the day this reading is for (`Reading for: 2026-07-16`), from the
+     input JSON's top-level `date` field (see `--format json` above) —
+     not necessarily the day the report is actually being read on, if
+     `reading.json` was generated earlier and piped into
+     `interpreter-cli` later;
+  2. the day's overall significance level (`Quiet`/`Notable`/
      `Significant`/`Major`, plus its rank out of the 4 defined levels,
      e.g. `Notable (2/4)`), with a "worth a deeper Celtic Cross look"
      line on `Major` days only;
-  2. up to 5 of today's aspects ranked by score, each naming the sign
+  3. up to 5 of today's aspects ranked by score, each naming the sign
      and natal house the transiting planet currently occupies and the
      sign and house of the natal planet it's aspecting, followed by a
      short narrative sentence about what that transiting planet
@@ -291,10 +304,10 @@ A plain-text report, printed in a fixed order —
      governs* (see `CLAUDE.md`'s `narrative.c` bullet) — omitted only if
      the source material has nothing to say for that planet/aspect
      combination;
-  3. the full 10-position Celtic Cross spread, in Waite's own drawing
+  4. the full 10-position Celtic Cross spread, in Waite's own drawing
      order, each with its card (and orientation), the position's own
      description, and that card's actual meaning;
-  4. finally, a guidance paragraph tying the day's top transit to the
+  5. finally, a guidance paragraph tying the day's top transit to the
      spread's Attitude/Outcome cards, with its opening sentence tailored
      to `day_level` (stronger wording on `Major`, softer on
      `Quiet`/`Notable`, falling back to a transit-free reading of the
@@ -305,6 +318,8 @@ A plain-text report, printed in a fixed order —
      seen the full spread it references.
 
 ```
+Reading for: 2026-07-16
+
 Day significance: Major (4/4)
 (a major transit today - worth a deeper Celtic Cross look)
 
@@ -354,6 +369,8 @@ The same report with `--lang de` (same input as the Major example
 above):
 
 ```
+Lesung für: 2026-07-16
+
 Bedeutung des Tages: Einschneidend (4/4)
 (ein einschneidender Transit heute - ein genauerer Blick auf das Keltische Kreuz lohnt sich)
 
@@ -415,6 +432,7 @@ has the slugs to work with directly.
 
 ```json
 {
+  "date": "2026-07-16",
   "day_significance": {
     "level": "major",
     "rank": 4,
@@ -448,6 +466,9 @@ has the slugs to work with directly.
 }
 ```
 
+- `date` is copied straight through from the input JSON's own top-level
+  `date` field (see `--format json` above) - always language-independent
+  regardless of `--lang`, same as every other slug in this document.
 - `significant_transits` has `interp.top_item_count` entries (0-5, same
   ranking as `--format text`); `celtic_cross` always has exactly 10, in
   `CelticCrossPosition` enum order (same order as `deck-engine`'s own