trajectories 0.1.2 → 0.1.4

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## Unreleased
+
+### Added
+
+- Authenticated shared history through `remote serve/push/pull/list` and Node-compatible handler/client APIs. Native SQLite histories retain machine identity, lineage and diagnostics; managed sessions synchronize canonical logs and required immutable evidence with conflict checks. Local SQLite ingestion and search remain unchanged.
+- Optional DuckDB analytics evaluation: warm cross-session metadata aggregates were 2.9–33.5× faster than indexed SQLite on the measured corpus; no production DuckDB dependency was added.
+- `read --canonical-only` omits duplicated raw native bytes while preserving canonical history, provenance, diagnostics and portability warnings. Default snapshot output remains unchanged.
+
+### Fixed
+
+- Observed `remote pull --machine` skips origin rows only when a local `shared://` copy already exists, so a lost SQLite can recover its own history.
+- The sync worker-deadline regression isolates worker admission from database setup, retaining real abort/reap and resume checks without a CI scheduling-speed assumption.
+
 ## 0.1.2
 
 ### Added

package/README.md

@@ -14,7 +14,7 @@ state converter. Compatibility evidence is in the [source repository](https://gi
 ## Install
 
 Download a native archive and its `.sha256` file from the
-[GitHub release](https://github.com/archeism/oh-my-ai/releases/tag/trajectories%400.1.2).
+[Trajectories releases](https://github.com/archeism/oh-my-ai/releases?q=trajectories%40&expanded=true).
 Choose `linux-x64`, `linux-arm64`, or `darwin-arm64` (Apple Silicon).
 Keep the executable and its `lib/` directory together; the native installer
 places a `trajectories` symlink on PATH. See the
@@ -22,12 +22,13 @@ places a `trajectories` symlink on PATH. See the
 
 ```sh
 # CLI: requires Bun 1.4.2 or newer on PATH.
-bun add --global trajectories@0.1.2
+bun add --global trajectories@latest
 trajectories --version
 trajectories search --help
+trajectories remote --help
 
 # SDK: inside your project; also works in Node 22.13 or newer.
-bun add trajectories@0.1.2
+bun add trajectories@latest
 ```
 
 The package includes the CLI, SDK, agent skill, and OS service installers.
@@ -63,8 +64,12 @@ conversation authority per logical session, shared evidence/artifacts, and
 explicitly bounded native checkpoints. Version 1 stores require explicit migration
 before using these managed APIs. Native scan/sync continues to use Ledger's engine.
 
-The current central store is local, private files. Omakase can use this SDK and
-keep Vercel's HarnessAgent for execution. Same-harness native resume remains
+Managed stores use private local files; [shared history](./docs/shared-history.md)
+adds authenticated cross-machine synchronization of their canonical logs and
+required evidence, plus native histories already indexed in SQLite. SQLite remains
+the local ingestion/search engine. Each session keeps its own history; sync uploads
+missing objects and changes instead of copying whole databases or snapshots.
+Omakase can use this SDK and keep Vercel's HarnessAgent for execution. Same-harness native resume remains
 useful: a transcript does not reconstruct runtime caches, permissions, pending
 approvals, installed tools/skills, filesystem state, or opaque reasoning state.
 The caller must stop the source and provide the target's tools and credentials.
@@ -148,6 +153,17 @@ Aliases: `cc` means `claude-code`. Native artifacts and source transcripts are
 never overwritten. Workspace files must already be present; `--cwd` changes the
 workspace reference, not tool-output text or historical file contents.
 
+For inspection without duplicating the complete native transcript in the JSON:
+
+```sh
+trajectories read /absolute/session.jsonl --from cc --canonical-only
+```
+
+This omits only `raw`; source provenance, canonical records, normalization
+metadata, diagnostics and portability warnings remain intact. The default
+`read` output is unchanged. This inspection output is not a complete portable
+snapshot, and the flag does not make unsupported continuation history resumable.
+
 Inspect a managed conversation directly, or add its current complete history to
 the same search index that holds native sessions: