In skills/Telos/Tools/UpdateTelos.ts, the getPacificDateForLog() function hardcodes PT as the timezone label in changelog entries, regardless of what timezone the principal is actually configured with.
Affected line:
return ${year}-${month}-${day} ${hours}:${minutes}:${seconds} PT;
The function already reads principal.timezone from getPrincipal() — it just doesn't use it in the label. Fix:
return ${year}-${month}-${day} ${hours}:${minutes}:${seconds} (${timezone});
Also, the function name getPacificDateForLog is misleading — it's timezone-aware, not Pacific-specific.
Steps to reproduce: Set principal.timezone to anything other than a Pacific timezone (e.g. Europe/Zurich), run an update, observe that updates.md still shows PT.
In skills/Telos/Tools/UpdateTelos.ts, the getPacificDateForLog() function hardcodes PT as the timezone label in changelog entries, regardless of what timezone the principal is actually configured with.
Affected line:
return
${year}-${month}-${day} ${hours}:${minutes}:${seconds} PT;The function already reads principal.timezone from getPrincipal() — it just doesn't use it in the label. Fix:
return
${year}-${month}-${day} ${hours}:${minutes}:${seconds} (${timezone});Also, the function name getPacificDateForLog is misleading — it's timezone-aware, not Pacific-specific.
Steps to reproduce: Set principal.timezone to anything other than a Pacific timezone (e.g. Europe/Zurich), run an update, observe that updates.md still shows PT.