Diagnostics
Output disk inventory
Where the server is reading from
| DATA_ROOT env var | (unset, defaults apply) |
| OUTPUT_ROOT (resolved) | /var/data/output |
| Markdown pages found | 1 |
| GBP post JSON found | 0 |
FILES PRESENT
Content Manager enumerator probe
Calls the same _enumerate_pages() the Content Manager uses, then compares the result count to what is on disk. This is where we will catch a mismatch between what is saved and what the listing screen shows.
OK
_enumerate_pages returned 1 entries — matches the on-disk count. First entries returned: type='Vehicle Page' dealer='Claremont Toyota' file='2026-camry-2026-05-20.md'
Per-dealer counts
| Dealer slug | .md pages | GBP posts |
|---|---|---|
| claremont-toyota | 1 | 0 |
Most recent 50 files
| Modified (UTC) | Path | Size | |
|---|---|---|---|
| 2026-05-20 21:21 UTC | claremont-toyota/2026-camry-2026-05-20.md | 42.1 KB | View |
If "FILES PRESENT" but Content Manager shows 0: the files are on disk but the listing/filtering on Content Manager is broken — share this page with Claude.
If "DISK EMPTY": the persistent disk has been cleared or the path is wrong. Files written before the last deploy are gone — but new generations should still work and start populating again.