get_progression ships full per-citizen timelines with no summary mode (266 KB of 275 KB) #232
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#232
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?
QA sweep, Eco via Sirens, day 40, 2026-08-12.
Observed
get_progressionreturns 275,159 characters and exceeds the MCP response cap. Breakdown:citizens(80 entries, each with a fulltimeline)firstSpecialtyGainsdailySeriestopLevelerstrendsThe summary layer is excellent and tiny —
perActionCounts(2,480 character level-ups, 1,030 specialty level-ups),bySpecialty(Logging 28, Mining 26, Gathering 26),topLevelers— roughly 8 KB total. It is unreachable because a 266 KB per-citizen event log rides along with it.Expected
Default to the summary, with per-citizen timelines behind a flag or a
citizenparameter.dailySeriesandtrendsalready cover the "trajectories over time" part of the tool's promise without the raw log.Note
Two fields also read as dead weight on this server:
classCompletions: []withCompleteClass: 0andEnrollAction: 0, andLoseSpecialty: 0.