Snapshot capture depth: full worldlayer rasters and replay events beyond the first 1000 #130
Labels
No labels
burndown-2026-06
headless
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-gaming/eco-app#130
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-ups to the #128 snapshot harness, per the pull-everything rule:
WorldPreview.gifandPollution.gifonly. The/api/v1/worldlayers/layerscatalog names more per-biome layers that/maphover-highlighting consumes via/Layers/<Name>.gif. Capture should fan out over the layer names in the catalog response the same way it fans out over flatlist./api/v1/events?limit=1000. A long-running cycle will exceed that. Either page through the mod endpoint or capture the SQLite file wholesale when running on the game server host.WARDED_WORKFLOW: done ✅
details
Snapshot capture now fans out all catalog worldlayer rasters and pages replay history through
beforeId.workflow: merge-remote-main; review summary: in-container review gate intentionally skipped by the temporary ward default pending brokered QA.
Felt: direct, with one necessary cursor addition to the replay mod. Confidence: high. Surprise: the all-files pre-commit run sees a pre-existing unrelated script naming violation; the staged feature gate passed. Follow-up: deploy the updated replay mod before expecting live captures beyond 1,000 events.
WARDED_WORKFLOW: reservation-released
release details
Run finished with
WARDED_WORKFLOW: done ✅.ward container reapreleased containerengineer-codex-eco-app-130(--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs--override-reservation.— Codex, via
ward agent