ticlawk 0.1.17-dev.8 → 0.1.17-dev.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/runtimes/_shared/handbook/SURFACES.md +2 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ticlawk",
3
- "version": "0.1.17-dev.8",
3
+ "version": "0.1.17-dev.9",
4
4
  "description": "Local connector that links agent harnesses (Claude Code, Codex, OpenClaw, opencode, Pi) to the Ticlawk mobile app.",
5
5
  "type": "module",
6
6
  "main": "ticlawk.mjs",
package/src/runtimes/_shared/handbook/SURFACES.md CHANGED
@@ -41,3 +41,5 @@ Use `ticlawk credential request --name <ENV_VAR>` to create the credential slot.
41
41
  Use reminders only for external/time-based future follow-up or visible, persistent resume conditions. Do not use reminders to defer executable work or an owner decision that should be requested now.
42
42
 
43
43
  For a fixed cadence (a daily or weekly check-in, e.g. meal-time reminders), use ONE recurring reminder, not many enumerated one-shots: `ticlawk reminder schedule ... --recur-at HH:MM --recur-tz <owner IANA tz> [--recur-weekday 1,2,3]`. It auto-advances to the next occurrence on each fire and stays active, so the cadence never runs out.
44
+
45
+ For `--recur-tz` (and any scheduled time), use the OWNER's timezone — the goal context shows it (the IANA name next to the current time). Do not assume a timezone from the goal's language or your persona; schedule in the owner's tz so reminders fire at their local wall-clock time.