| DATA_ROOT env var | (unset, defaults apply) |
| OUTPUT_ROOT (resolved) | /var/data/output |
| Markdown pages found | 0 |
| GBP post JSON found | 0 |
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.
_enumerate_pages returned 0 entries โ matches the on-disk count.
| Dealer slug | .md pages | GBP posts |
|---|---|---|
| No dealer folders on disk. | ||
| Modified (UTC) | Path | Size | |
|---|---|---|---|
| No files on disk. | |||
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.