Commit eco data fixtures #89
Labels
No labels
burndown-2026-06
burndown-2026-08
headless
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-gaming/eco-app#89
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?
Unpack it into json and then scramble all the usernames
The apply strict formatting on the json - and format it for human readability so I can check it against the UI
Closing this older fixture plan as superseded by #128.
The repository now has a complete snapshot harness that captures every Eco endpoint, stores snapshots privately in S3, and replays them locally through
ward exec snapshot-pull,snapshot-serve, andhttp-offline..snapshots/is deliberately gitignored because the source contains player names and other live world state.Committed tests already use synthetic, reviewable fixtures for stable contracts. Adding a hand-scrambled live dump would create a second fixture system, lose reproducibility when the scrambling changes joins, and require repeated human privacy review.
The selected boundary is private full-fidelity snapshots for integration work plus synthetic committed fixtures for tests. No live dataset should be added to git.