Name today in the HEY account's time zone

[robzolkos]

mise ~/.config/mise/config.toml tools: gh@2.101.0
Commands that default to today were naming tomorrow in the evening in New York and anywhere else west of UTC.

• hey event day and hey event week sent now. HEY reads now in UTC on a JSON request, so after 20:00 in New York the command showed tomorrow's schedule.
• hey event list, hey habit list, complete and uncomplete, and hey journal read and write took today from the machine's clock. hey todo add left the date to the SDK, which does the same thing. A server's clock and most sandboxes' clocks run on UTC, so on those machines these commands also named tomorrow.

Each of these commands now works out today in the account's time zone and sends that date. This follows the pattern #498 set for event times. Resolving an omitted date reads the identity once for the account's zone; naming the date skips that read. A specific --account is validated by a separate identity read before the command runs, so a defaulted command with it reads identity twice and a dated command once.

When the account's zone can't be used

Case	Reads (event day/week/list, habit list, journal read)	Writes (habit complete/uncomplete, journal write, todo add)
Account has no zone, or one this build doesn't know	Uses the machine's today and prints a notice on stderr	Refused as a usage error, with a hint to name the date
Identity read fails (network, 5xx, rate limit)	Refused, keeping the SDK error code, with a hint to name the date	Same
Sign-in rejected	Reported as an auth error	Same

An account with no zone is a lasting state. If reads refused in that case, those commands could never run without a date. Falling back to the machine's date matches what HEY's web app does when an identity has no zone: it uses the browser's zone.

Writes are stricter because a wrong guess does damage. It could mark the wrong day's habit done or overwrite another day's journal entry. #498 already refuses event writes rather than guess.

A failed identity read is temporary, so it is reported as an error with its original code and can be retried, rather than answered with a guessed day.

Also in this PR

• Shared zone code. The account-zone read moves out of the event fields into its own accountZone in internal/cmd/account_zone.go. Event writes, countdown decoding and the new today logic all use it.
• hey bubble up --on. It compared the date with the machine's today to decide whether to use HEY's Later today slot. HEY lays out every bubble-up slot in UTC, so it now compares with today in UTC.
• Left alone on purpose. hey todo list and hey journal list read years either side of today, and an event edit searches a year either side. They keep the machine's clock rather than read the identity for one day's difference at the edge.

The help text, docs/cli.md and the skill describe the new behaviour.

---

Summary by cubic

Commands that default to today now name the HEY account's today instead of tomorrow in the evening west of UTC.

hey event day and hey event week sent now, which HEY reads in UTC on a JSON request; the rest read the machine's clock (UTC on servers and sandboxes), and hey todo add left the date to the SDK. Every command that defaults to today now reads the account's time zone at most once per command — and not at all when a date is given — and sends that day.

• Reads (event day/week/list, habit list, journal read) fall back to the machine's today with a notice on stderr when the account has no usable zone.
• Writes (habit complete/uncomplete, journal write, todo add) refuse with a hint to name the date instead of guessing.
• A failed identity read keeps its error code for both; a sign-in failure stays an auth error. A specific --account adds one validation read, so a defaulted command reads the identity twice and a dated one once.
• hey bubble up --on now picks HEY's Later today slot by comparing with today in UTC, HEY's clock for bubble-up slots.
• The account-zone logic moved into internal/cmd/account_zone.go; hey todo list and hey journal list keep the machine's clock on purpose.

^{Written for commit 5022ee5. Summary will update on new commits.}

[Copilot]

Copilot review overview

🟢 Approved

The implementation consistently applies the documented policy and includes broad boundary, fallback, error, and request-count coverage.

Review effort: Balanced
Findings: None

What changed in this PR

Updates date-defaulting commands to use the HEY account’s time zone, preventing UTC-boundary errors.

Changes:

• Adds shared account-zone date resolution with safe read/write fallbacks.
• Updates calendar, habit, journal, todo, and Bubble Up behavior.
• Adds comprehensive tests and documentation.

[!TIP]
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.

File	Description
internal/​cmd/​account_zone.go	Adds shared account-zone and today resolution.
internal/​cmd/​account_zone_test.go	Tests date defaults, fallbacks, errors, and request counts.
internal/​cmd/​events.go	Uses account-local today for event defaults.
internal/​cmd/​events_period.go	Sends explicit account-local dates for day/week views.
internal/​cmd/​events_period_test.go	Removes obsolete now behavior test.
internal/​cmd/​events_zone.go	Reuses shared account-zone resolution.
internal/​cmd/​events_zone_test.go	Migrates tests to the shared clock seam.
internal/​cmd/​events_occurrence.go	Uses shared zone lookup for countdown decoding.
internal/​cmd/​recording_filter.go	Supports configurable default-window dates.
internal/​cmd/​calendar_commands_test.go	Supplies identity data for event-list tests.
internal/​cmd/​habit.go	Applies account-local defaults to habit operations.
internal/​cmd/​journal.go	Applies safe account-local journal defaults.
internal/​cmd/​journal_test.go	Adds identity handling to journal fixtures.
internal/​cmd/​todo.go	Explicitly files new todos on account-local today.
internal/​cmd/​todo_test.go	Adds identity handling to todo fixtures.
internal/​cmd/​mutation_test.go	Makes an unrelated todo test date-explicit.
internal/​cmd/​bubble.go	Compares Bubble Up dates against UTC today.
internal/​cmd/​bubble_test.go	Covers UTC versus local-date scheduling.
docs/​cli.md	Documents account-local default-date behavior.
skills/​hey/​SKILL.md	Updates agent guidance for date defaults.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Copilot review overview

🟡 Changes recommended

Specific --account invocations can read identity twice, contradicting the documented request-count guarantee.

Review effort: Balanced
Findings: 1

Open (1)

• Avoid duplicate identity fetches for --account commands · New

[cursor]

Approved. Cursor Bugbot was not running and Cursor Security Agent was skipped, so those signals were not used. No approval policy required human review, and reviewers were not assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Approver}

[robzolkos]

Fixed — clarified that resolving an omitted date makes one identity read, while a specific --account is independently validated first. Added coverage showing two reads for a defaulted --account command and one for an explicit-date invocation.

[Copilot]

Copilot review overview

🟢 Approved

The shared implementation, command integrations, documentation, and broad behavioral coverage are consistent and complete.

Review effort: Balanced
Findings: None

Resolved since last review (1)

• Avoid duplicate identity fetches for --account commands