character-worklog

To track per-character work history, log shifts at specific buildings using punch-in and punch-out workflows, which records units worked and timestamps to compute wages and build a persistent career log across JobType and BuildingId.

Transient shift counters reset on punch-in and are consumed at punch-out for per-shift wage calculations, while persistent career totals accumulate across all shifts per JobType and BuildingId to build a lifetime career log for promotions.

To log a work shift, punch in for a JobType at a BuildingId to start the transient counter, log each work unit during the shift, then finalize the shift to update both the transient counter and the persistent lifetime career totals.

Yes, work history tracking supports promotions by maintaining a WorkPlaceRecord data structure that stores BuildingId, UnitsWorked, ShiftsCompleted, and timestamps, providing the persistent lifetime counters needed for career progression quests.

Work history for UI display is stored using a WorkPlaceRecord data structure that contains BuildingId, BuildingDisplayName, UnitsWorked, ShiftsCompleted, and timestamps, providing the necessary APIs for wage calculation and history rendering.

Wages can be calculated using logged shift data by consuming the transient shift counter at punch-out, which tracks the exact units worked during a specific shift at a given building before resetting for the next session.