@squirreljetpack/im-dynamic 0.2.9 → 0.2.11

package/CHANGELOG.md

@@ -1,3 +1,73 @@
+## [0.2.11] - 2026-11-02
+
+### 🚀 Features
+
+- `im :c mm` opens the matchmaker render config (`mm.toml`) in
+  `$VISUAL`/`$EDITOR`, alongside the config, `moods` and `colors` targets.
+- Log entries (moods, trackers, todo completions) store the UTC offset and
+  the location string (the system IANA name, or empty when it has none) in
+  effect where they were written. The today view groups log entities by their
+  recorded **civil day** and renders their recorded civil time; ordering stays
+  absolute. Mood/tracker previews show the differing location and wall-clock
+  shift under the timestamp; task previews append the same parts inline to
+  `last:` as `prev:`.
+- Tracker interval anchors are unzoned civil datetimes resolved in the current
+  local zone. Replace-mode slots and cumulative sums assign foreign logs by
+  their recorded wall clock, so an entry stays in the same civil slot when
+  viewed from another zone.
+- Replace-mode null trackers store their absolute seconds from the interval
+  start in the entry payload; color and the strict when-zone use that stored
+  position.
+- Explicit todo completions join the today view on their civil completion day.
+  `B` now merges explicitly completed scheduled tasks on that day instead of on
+  an overlapping availability window.
+
+### 💥 Breaking changes
+
+- Sync vocabulary is version 4: `tz_offset` (required int) and `location`
+  (required text; empty when the system has no name) on mood, tracker and
+  completion. Pre-v4 creates lack the
+  location or offset and are intentionally unbuildable; reset the sync log
+  when replaying one.
+- Databases from earlier builds are not migrated. Delete the database file and
+  sign in to rebuild from the log. Tracker configs must drop the `Z`/numeric
+  offset from interval anchors.
+
+## [0.2.10] - 2026-10-31
+
+### 🚀 Features
+
+- `im :sync --reset` asks before it discards local changes the server never
+  received; `--force` skips the question, and an idle database rebuilds without
+  a prompt.
+- Sync is versioned end to end. A cursor names the log it indexes, and the
+  client and worker exchange the envelope `protocol` and cell `version` on
+  every round: a cursor minted by another log, one past the end of this log, or
+  a peer that speaks another version is refused instead of merging unrelated
+  histories or skipping what it cannot read. `im :sync status` prints the log,
+  cursor version and both protocol numbers.
+
+### 🐛 Bug Fixes
+
+- A task's start time is required, and an edit can no longer clear the column
+  that defines a task's kind. A scheduled task's window opens at that start, a
+  recurring task's intervals tile from it, and a oneshot is stamped with it at
+  creation; clearing the duration or interval that goes with it is refused
+  instead of silently reclassifying the task (and with it its availability,
+  view membership and completion scope).
+- An end time is cleared by a blank answer (or `never`/`none`) in both the
+  create and edit menus; a blank previously kept the old value.
+
+### 💥 Breaking changes
+
+- A task create must carry `start_time`, so the cell vocabulary is now version
+  2. A peer that speaks another version refuses the round rather than skip the
+  cell, and v0.2.9 and earlier clients send no version at all: redeploy the
+  worker and upgrade the client together.
+- Databases from earlier builds are not migrated: a schema change means
+  deleting the database file, then signing in to rebuild from the log.
+
+
 ## [0.2.9] - 2026-10-30
 
 ### 🚀 Features

package/README.md

@@ -76,8 +76,8 @@ Usage:
                                                         (optionally attached to a mood)
 
   im ! [name] [@<time>]                          create a task (interactive without a name)
-  im ! %[<interval>] [[:]name]                   create a recurring task (interactive)
-  im ! @[<time>] [:<name>] [%<duration>]         scheduled a task (interactive if partial)
+  im ! %[interval] [[:]name]                   create a recurring task (interactive)
+  im ! @[time] [:<name>] [%<duration>]         scheduled a task (interactive if partial)
   im +[task] [count]                             edit or update a task by its reference
                                                         (see `im -vh`)
 
@@ -96,11 +96,11 @@ Trackers and grids:
 
 Other:
   im :tool embed|mood|clear|..                   (see `im :tool --help`)
-  im :tool config | :c [moods|colors]            open the config in $VISUAL / $EDITOR
+  im :tool config | :c [moods|colors|mm]         open the config in $VISUAL / $EDITOR
   im -                                           browse trackers
   im :db prune|backfill|doctor                   database utilities
 
-  im :sync [register|login|status|logout]        setup/manage/run sync 
+  im :sync [register|login|status|logout]        setup/authenticate/run sync 
 
 
 Flags:
@@ -149,10 +149,14 @@ Trackers are defined in your configuration (`im :tool config`); each `[tracker.<
 section is logged through `im -<name> <value>` (no value for `null` trackers):
 
 - Kinds: `text`, `integer`, `float`, `duration` (strings like `6m 30s`), `null` (timestamp/count markers — requires an interval).
-- `interval = { anchor = "2026-01-01T00:00:00-04:00", span = "1 day" }` bins
-  entries into calendar slots. By default, a new log in a slot
-  replaces the slot's previous entry; `interval.cumulative = true` keeps every log and
-  the slot's grid dot shows the aggregate.
+- `interval = { anchor = "2026-01-01T00:00:00", span = "1 day" }` bins
+  entries into calendar slots. The anchor is an unzoned civil datetime (no `Z`
+  or numeric offset) resolved in your current local zone. By default, a new log
+  in a slot replaces the slot's previous entry; `interval.cumulative = true`
+  keeps every log and the slot's grid dot shows the aggregate. Logs record the
+  UTC offset and location string (the system IANA name, or empty) they were
+  written in, so they stay on their recorded civil day and interval slot when
+  viewed from another zone.
 
 ## FAQ
 

package/npm-shrinkwrap.json

@@ -18,7 +18,7 @@
       },
       "hasInstallScript": true,
       "name": "@squirreljetpack/im-dynamic",
-      "version": "0.2.9"
+      "version": "0.2.11"
     },
     "node_modules/detect-libc": {
       "engines": {
@@ -47,5 +47,5 @@
     }
   },
   "requires": true,
-  "version": "0.2.9"
+  "version": "0.2.11"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/Squirreljetpack/im/releases/download/v0.2.9"
+    "https://github.com/Squirreljetpack/im/releases/download/v0.2.11"
   ],
   "bin": {
     "im-dynamic": "run-im-dynamic.js"
@@ -87,7 +87,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "0.2.9",
+  "version": "0.2.11",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"