apple-journal-cli 1.1.0 → 1.3.0
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.
- package/README.md +52 -4
- package/bin/journal-cli +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -51,6 +51,8 @@ Security), then:
|
|
|
51
51
|
journal-cli doctor
|
|
52
52
|
```
|
|
53
53
|
|
|
54
|
+
Release history and upgrade notes: [CHANGELOG.md](CHANGELOG.md).
|
|
55
|
+
|
|
54
56
|
## Reading
|
|
55
57
|
|
|
56
58
|
Reads run against a temp snapshot of the store, so they are safe while
|
|
@@ -96,7 +98,8 @@ journal-cli write --live --body "Golden hour" --live-photo IMG_0123.heic IMG_012
|
|
|
96
98
|
|
|
97
99
|
# location pin
|
|
98
100
|
journal-cli write --live --body "At the office" \
|
|
99
|
-
--lat 47.62055 --lon -122.34930 --place "Space Needle" --city Seattle
|
|
101
|
+
--lat 47.62055 --lon -122.34930 --place "Space Needle" --city Seattle \
|
|
102
|
+
--location-presentation large # small (default) or large
|
|
100
103
|
|
|
101
104
|
# web link (renders as a rich link card)
|
|
102
105
|
journal-cli write --live --body "Read this" --link https://example.com --link-title "A Post"
|
|
@@ -122,6 +125,16 @@ journal-cli edit 103 --live --clear-location --no-bookmark
|
|
|
122
125
|
journal-cli edit 103 --live --journal "Travel" # stage an imported entry
|
|
123
126
|
```
|
|
124
127
|
|
|
128
|
+
### Repairing
|
|
129
|
+
|
|
130
|
+
```sh
|
|
131
|
+
journal-cli repair-locations --dry-run # find maps written by 1.2.0's `off`
|
|
132
|
+
journal-cli repair-locations --live # restore them as small map cards
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
Only needed if you used `--location-presentation off` on journal-cli 1.2.0.
|
|
136
|
+
See "Why there is no location `off`" below.
|
|
137
|
+
|
|
125
138
|
### Deleting
|
|
126
139
|
|
|
127
140
|
```sh
|
|
@@ -141,7 +154,7 @@ S=skills/dayone-import/scripts/dayone-import.py
|
|
|
141
154
|
|
|
142
155
|
python3 $S journals # list Day One journals
|
|
143
156
|
python3 $S plan "Travel Journal" # what imports, and what can't
|
|
144
|
-
python3 $S import "Travel Journal" --into "Travel" --target-db "$(journal-cli sandbox --dir /tmp/r)"
|
|
157
|
+
python3 $S import "Travel Journal" --into "Travel" --location-presentation large --target-db "$(journal-cli sandbox --dir /tmp/r)"
|
|
145
158
|
python3 $S import "Travel Journal" --into "Travel"
|
|
146
159
|
```
|
|
147
160
|
|
|
@@ -210,7 +223,9 @@ Every write path has been verified against a real library on macOS 26:
|
|
|
210
223
|
Journal.app renders CLI-written text, photos, Live Photos (labeled as such),
|
|
211
224
|
link cards, and location pins (which also feed its Places index); the sync
|
|
212
225
|
engine uploads them all to CloudKit — including the attachment files — and a
|
|
213
|
-
delete/restore round trip propagates.
|
|
226
|
+
delete/restore round trip propagates. Map cards were checked against the app's
|
|
227
|
+
three modes: `small` and `large` are reproducible from the asset row, `off` is
|
|
228
|
+
not (see "Why there is no location `off`"). The read pipeline has been swept over an
|
|
214
229
|
entire real store: every entry row and all ~700 asset metadata blobs parse.
|
|
215
230
|
|
|
216
231
|
The test suite (`tests/test_write.sh`) runs the whole command
|
|
@@ -218,7 +233,9 @@ surface against a disposable copy of a store — argument guards, insert
|
|
|
218
233
|
bookkeeping, RTF round-trips, location metadata, media file layout, Live Photo
|
|
219
234
|
pairing, Photos linkage, journal targeting, link assets, the delete/restore
|
|
220
235
|
lifecycle, and `PRAGMA integrity_check`. Point `JOURNAL_SEED` at a backup to
|
|
221
|
-
run it without Full Disk Access
|
|
236
|
+
run it without Full Disk Access, or point it at `tests/make-fixture.sh`'s
|
|
237
|
+
synthetic store to run with no Journal library at all (what CI does); the suite
|
|
238
|
+
is seed-independent and passes either way. `JOURNAL_CLI` selects the binary under test;
|
|
222
239
|
the Python implementation in `reference/` remains an executable reference for
|
|
223
240
|
the original command surface.
|
|
224
241
|
|
|
@@ -268,6 +285,37 @@ entry whose text was typed in the app. Consequences:
|
|
|
268
285
|
entry would.
|
|
269
286
|
- **Authoring the CRDT is out of scope** — fabricating causal history in a
|
|
270
287
|
reverse-engineered protobuf risks corrupting merge for that entry.
|
|
288
|
+
- **Some entry state lives only in the CRDT**, and so is not ours to write.
|
|
289
|
+
Location `off` is the known case — see below.
|
|
290
|
+
|
|
291
|
+
### Why there is no location `off`
|
|
292
|
+
|
|
293
|
+
Journal's map card has three modes (Off / Small / Large), but only two of them
|
|
294
|
+
are in the asset row. The size is `ZISSLIM`; **Off is recorded solely in the
|
|
295
|
+
entry's CRDT**, whose key table reads `title`, `gridAssetIDs`, `slimAssetID`,
|
|
296
|
+
`hiddenAssetIDs`, `assetPlacement`. An Off map is listed under
|
|
297
|
+
`hiddenAssetIDs` there, and its asset row stays byte-identical to a large
|
|
298
|
+
one — `ZISSLIM=0, ZISHIDDEN=0`.
|
|
299
|
+
|
|
300
|
+
Measured against a live store of 5,000+ assets: `ZISHIDDEN` is `0` on every
|
|
301
|
+
asset of every type, Journal never sets it, and on all 39 entries whose CRDT
|
|
302
|
+
carries `hiddenAssetIDs` the asset rows still read `ZISHIDDEN=0`. Five of
|
|
303
|
+
those entries have a map as their only asset and carry `hiddenAssetIDs` with
|
|
304
|
+
no `gridAssetIDs`/`slimAssetID`, which pins the meaning down exactly.
|
|
305
|
+
|
|
306
|
+
So `ZISHIDDEN=1` does not hide a map card. Journal treats the asset as absent
|
|
307
|
+
altogether: no card **and no Places entry**, the location effectively gone.
|
|
308
|
+
journal-cli 1.2.0 shipped `--location-presentation off` written that way;
|
|
309
|
+
1.3.0 refuses the flag rather than silently losing locations.
|
|
310
|
+
|
|
311
|
+
If you imported with 1.2.0, the coordinates are still in the rows and
|
|
312
|
+
`repair-locations` fixes them in place — no re-import:
|
|
313
|
+
|
|
314
|
+
```sh
|
|
315
|
+
journal-cli repair-locations --dry-run # count what is affected
|
|
316
|
+
journal-cli repair-locations --live # restore as small maps
|
|
317
|
+
journal-cli repair-locations --to large --live # or as large ones
|
|
318
|
+
```
|
|
271
319
|
|
|
272
320
|
### Not supported
|
|
273
321
|
|
package/bin/journal-cli
CHANGED
|
Binary file
|