trajectories 0.0.0 → 0.1.1

package/CHANGELOG.md

@@ -0,0 +1,23 @@
+# Changelog
+
+## 0.1.1
+
+### Fixed
+
+- Published CLI normalization now uses the same bundled correction as the SDK, preserving exact failed Pi/OMP tool-output text outside the workspace.
+- Packed-consumer checks assert failed-result content through the real CLI sync and show commands.
+
+## 0.1.0
+
+### Added
+
+- Portable session conversion SDK for 11 harness formats, usable in Node.
+- Bun CLI for reading and searching 18 local history formats, retaining Ledger's indexing, bounded sync, watch, deletion, and robot output.
+- Canonical managed session logs, explicit native continuation bindings, and offline migration from version 1 stores.
+- Installation utilities and agent skill for Linux and macOS. Existing Ledger search databases keep their paths.
+- Tested npm publication from reviewed package tags through GitHub Actions.
+
+### Limitations
+
+- Conversion prepares history; callers coordinate harness execution and credentials.
+- See the README for supported compaction boundaries. Optional semantic search requires its embedding runtime and model; lexical search does not.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,3 +1,275 @@
-# trajectories
+# Trajectories
 
-Name reserved. First release in progress; see the `trajector` package.
+Keep one conversation identity while moving its history between 11 harnesses:
+Claude Code, Codex, Pi, Oh My Pi, OpenCode, Grok Build, Cursor, Deep Agents,
+GitHub Copilot, Cline, and fx. Read and search 18 local history formats through
+the CLI, or use the independent conversion SDK.
+
+One package, two entrypoints: `import … from 'trajectories'` works in Node 22.13+;
+the `trajectories` CLI uses Bun 1.4.2+ for the existing Ledger SQLite/search engine.
+Conversion support has explicit fidelity limits; it is not a universal native
+state converter. Compatibility evidence is in the [source repository](https://github.com/archeism/oh-my-ai/tree/main/packages/trajectories/evidence).
+
+## Install
+
+```sh
+# CLI: requires Bun 1.4.2 or newer on PATH.
+bun add --global trajectories@0.1.0
+trajectories --version
+trajectories search --help
+
+# SDK: inside your project; also works in Node 22.13 or newer.
+bun add trajectories@0.1.0
+```
+
+The package includes the CLI, SDK, agent skill, and OS service installers.
+It keeps the existing Ledger database path; installation does not start an
+indexing service. See [installation and service cutover](./ops/README.md).
+Lexical search works without embedding models. Optional semantic search needs
+the ONNX runtime and a downloaded model (`trajectories models pull`); that
+download is separate from the release's lexical installation checks.
+
+The optional Workflow adapter remains a separate package and is not part of
+this release. The SDK and CLI do not require Workflow.
+
+## The session boundary
+
+- A **managed session** has a stable id, an existing workspace reference, a head
+  in its own canonical log, and prepared native-session bindings. Sessions share
+  a schema and artifact store; each retains its own accepted conversation order.
+- A **snapshot** is a transient native codec capture or explicit archive export.
+  Managed history retains accepted records, source evidence and required sidecars
+  through immutable references instead of saving another full snapshot per turn.
+- A **native export** is a new runtime session artifact plus explicit native
+  import/resume argument vectors. Conversion never executes a tool or a harness.
+
+Managed API version 2 follows the
+[canonical-log contract](../../docs/adr/0011-trajectories-log-authority.md): one
+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
+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.
+
+`switch` **prepares** a continuation and publishes a binding event, returning a
+new head and binding id. Carry both into the target's completed capture. Stale
+imports fail instead of overwriting newer history. The caller coordinates native
+execution; preparing a binding never launches a harness.
+
+For durable execution, compose the optional
+[`@oh-my-ai-sdk/trajectories-workflow`](../trajectories-workflow) adapter with
+Vercel Workflow and HarnessAgent. Core history conversion and storage have no
+Workflow dependency. Mutations require a caller-owned intent id. An exact retry
+replays the same receipt while its child head remains current; changed input or
+an advanced head fails. Staged captures and receipts contain retained references,
+not full histories. Local files must live on storage that survives the worker.
+
+## Use the SDK
+
+```ts
+import {
+  readSnapshot, createSession, switchSession, appendCapture, readSession,
+} from 'trajectories';
+
+const history = await readSnapshot({
+  harness: 'claude-code', path: '/absolute/native/session.jsonl',
+});
+const created = await createSession('/absolute/session-store', history, {
+  id: 'conversation', workspace: '/absolute/existing-workspace', intentId: 'import-source',
+});
+const prepared = await switchSession('/absolute/session-store', created.session.id, 'pi', {
+  expectedHead: created.session.head, intentId: 'prepare-pi',
+  write: { directory: '/absolute/new-export-directory', cwd: created.session.workspace },
+});
+// The host executes prepared.native.prepare (if present), then native.resume.
+// Each action carries command, args, and cwd; preserve that cwd when spawning.
+// After the host proves completion and stops the target:
+const capture = await readSnapshot({ harness: 'pi', path: '/absolute/completed-pi.jsonl' });
+const appended = await appendCapture('/absolute/session-store', created.session.id, capture, {
+  expectedHead: prepared.session.head, bindingId: prepared.binding.id, intentId: 'import-pi',
+});
+const page = await readSession('/absolute/session-store', created.session.id, {
+  atHead: appended.session.head, view: 'history', limit: 100,
+});
+// Continue with page.nextCursor, keeping the same session, head and view.
+```
+
+For conversion without central storage, use `readSnapshot`, `convert` (pure),
+or `writeSnapshot` (writes exclusively into a new directory). `NativeExport`
+contains `files`, `entrypoint`, `prepare?`, `resume`, and `diagnostics`.
+Arguments are arrays; callers should not concatenate them into shell commands.
+Model/provider overrides configure the new session, not historical measurements.
+
+## Use the CLI from this checkout
+
+```sh
+bun install --frozen-lockfile
+bun run --cwd packages/trajectories build
+bun packages/trajectories/dist/cli.js --help
+
+# Existing search/index options and existing Ledger database remain supported.
+bun packages/trajectories/dist/cli.js search 'deployment decision' --robot
+
+# Create the named central session; the receipt includes its id and head.
+bun packages/trajectories/dist/cli.js import /absolute/session.jsonl \
+  --from cc --session conversation --intent-id import-source \
+  --cwd /absolute/workspace --store /absolute/session-store
+
+# Use the returned id/head. The output tells the caller how to import and resume.
+bun packages/trajectories/dist/cli.js switch SESSION_ID --to pi \
+  --out /absolute/new-pi-export --expected-head HEAD --intent-id prepare-pi \
+  --store /absolute/session-store
+```
+
+Other history commands: `read`, `convert`, `sessions`, and `session`.
+`sessions` returns a page; continue with `--cursor` and select its size with `--limit`.
+Import after a run with `import FILE --from HARNESS --session ID --expected-head HEAD
+--binding-id BINDING --intent-id IMPORT_INTENT`. The binding is required for a
+prepared target lineage. Reuse the exact session, intent, parent and input on retry.
+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.
+
+Inspect a managed conversation directly, or add its current complete history to
+the same search index that holds native sessions:
+
+```sh
+trajectories show SESSION_ID --store /absolute/session-store
+trajectories index --store /absolute/session-store --db /absolute/ledger.sqlite --robot
+trajectories search 'deployment decision' --db /absolute/ledger.sqlite --robot
+trajectories show managed:SESSION_ID --db /absolute/ledger.sqlite --robot
+```
+
+`index` is an explicit lexical projection, separate from execution. Repeat it
+after importing completed history. A central session keeps the search id
+`managed:SESSION_ID` when its harness changes. Re-indexing replaces the searchable
+head from the accepted log. Uncommitted stages stay outside conversation and
+search views. Managed rows use `source: managed`; records retain their original
+harness, native-session id and prepared binding id across handoffs. Index
+tombstones remain suppressed without excluding native listings. `show --store`
+returns the complete accepted history with central record ids, payloads and origin.
+Indexed `show` returns full Ledger DB record bodies, labels that projection as
+`record_format: ledger-db`, and points to `managed_log_path`. The index remains
+a derived projection. Search snippets are excerpts.
+The scheduled native `sync` does not index managed stores.
+
+## Ledger migration
+
+The [current parity bootstrap](./docs/harness-parity-bootstrap.md) separates
+18 CLI history sources, 11 SDK codecs, and 11 execution implementations
+available through Vercel's adapters plus our OMP adapter. Codec coverage does
+not imply every adapter is installed or every model route has passed a live run.
+The [native results](./evidence/harness-parity-results-2026-10-05.md) retain
+successful and failed live cohorts, current native readback checks and limits.
+The [initial inventory](./docs/harness-support-parity.md) preserves the earlier
+16-reader/six-codec baseline.
+
+The port retains `search/query`, `recent/last`, `sync`, `status`, `scan`, `build`,
+`watch`, `models pull`, and `delete`, including robot output, tombstones, writer
+leases, source discovery, and read-only search. Source attribution and intentional
+changes are in [legacy/NOTICE.md](./legacy/NOTICE.md).
+
+The remaining operational utilities now ship with the package: worktree and
+SHA-pinned release installers, Linux/macOS bounded scheduled sync, the
+[Trajectories agent skill](./skills/trajectories/SKILL.md) and search/recent
+wrappers, prompt-history recovery, native SQLite smoke checks, and the legacy
+retitle recipe. The read-only daemon observer and rollout snapshot/query checks
+are retained under `legacy/scripts`. See [installation](./ops/README.md) and the
+[Ledger retirement checklist](./docs/ledger-migration.md).
+
+The [inspiration index](./docs/inspirations.md) preserves Ledger's pinned source
+research, implemented patterns and rejected experiments. The new
+[Huihua and OAR assessment](./docs/research/2026-10-06-huihua-and-oar.md)
+records the owner's decision to skip the [evidence API design](./docs/evidence-api.md).
+Long-history SDK acquisition remains an unmeasured candidate. Repeated full
+checkpoint storage is a rejected architecture; the managed log replaces that
+storage without adding a harness executor or a new codec.
+
+Search database resolution is `--db`, then `TRAJECTORIES_DB`, then `LEDGER_DB`,
+then the existing `${XDG_DATA_HOME:-~/.local/share}/ledger/ledger.sqlite`.
+Installation does not rename an existing database or reconfigure a running Ledger
+service. For a service cutover, keep the database path and replace only its CLI
+entrypoint after stopping the previous writer. Automatic machine-wide cutover is
+outside this bootstrap.
+
+The [verified Mac cutover](./evidence/mac-cutover-2026-10-07/README.md) replaced
+the command and scheduled writer while keeping the existing database and native
+histories. The receipt records parity checks, one restored rollback, and remaining
+backlog and integrity-check limits. There is no Ledger forwarding command.
+
+Managed-session storage is separate: `--store`, then `TRAJECTORIES_HOME`, then
+`${XDG_DATA_HOME:-~/.local/share}/trajectories`. `index --store` projects managed
+heads into the search database without coupling the conversion SDK to SQLite.
+
+For a version 1 managed store, stop all native and Workflow writers, then migrate
+into a fresh destination:
+
+```sh
+trajectories migrate /absolute/v1-store --out /absolute/new-v2-store --writers-stopped --robot
+```
+
+The source remains recoverable. A successful migration writes `migration.json`
+with preserved session IDs, accepted capture references and prepared binding/head
+mappings. Update caller state to those exact heads and bindings before resuming
+against the destination. Failed destinations remain intact without a completed
+manifest; inspect them and select a new destination for another attempt.
+
+For Claude's prompt-only `history.jsonl`, use `import-claude-history` with explicit
+`--history`, `--session`, zoned `--from`/`--to`, `--db`, and `--evidence` paths.
+It preserves selected source bytes and byte-offset provenance, labels the slice
+partial, and does not reconstruct assistant replies or pasted text.
+
+## Fidelity and supported boundaries
+
+Readers retain complete tool arguments/results and include system records.
+Native writers preserve user/assistant text and completed tool-call/result pairs.
+Source system instructions and reasoning remain in the snapshot and are not
+silently installed as the target's instructions or provider reasoning. Every
+export reports this and other format limitations. Images and native-only state
+are not portable through Letta's text-oriented projection; captured native text
+and retained sidecars remain available. Native-required synthetic usage fields
+are explicitly diagnosed and must not be counted as measured tokens or cost.
+
+Branched, compacted, reset, or inherited-prefix histories whose active context
+cannot be established are rejected for managed capture and conversion. Standalone
+`readSnapshot`/`read` can inspect their raw history where normalization succeeds,
+with portability issues attached.
+Unfinished tool batches are rejected. This version does not guess missing results
+or replay abandoned branches into a new agent's context.
+
+Identified linear Pi v3 compactions can export their verified native summary and
+retained tail while preserving the complete original transcript. See the
+[bounded Pi compaction contract](docs/pi-compaction-context.md) and its native
+Pi-to-OMP transfer receipt. OMP native auto-compaction remains unsupported; an
+actual GLM5.3 reviewer produced it during the
+[canonical-log implementation checks](evidence/canonical-log-2026-10-07/README.md).
+The stopped archive stays inspectable, and managed capture refuses it. Ordinary
+codec handoffs do not imply support for every native compaction schema.
+
+Pi's native provider omits aborted/error assistant drafts from its next model
+context. The SDK applies that same narrow projection to Pi canonical records and
+reports each omission; the complete source remains in `snapshot.raw`. Actual tool
+results remain preserved, so an orphan result still rejects conversion. OMP has
+different interrupted-message behavior and is not projected this way. See the
+[verified source contract](./docs/pi-provider-context.md).
+
+The SDK and CLI converter builds bundle the pinned normalizer, including the
+[Pi/OMP empty-error-output correction](../../repros/trajectory-error-roundtrip/README.md).
+The external Letta dependency remains for types and the legacy search engine.
+
+## Development
+
+```sh
+bun run verify
+bun run test:package
+```
+
+`verify` runs the source and legacy unit suites. The separate `test:package` check
+in `smoke/` installs the packed tarball outside the workspace, imports the SDK
+in Node, checks the patched normalization behavior, and invokes the Bun CLI's
+new and existing command surfaces. Live checks use real native sessions, separate
+workspaces, withheld facts, and actual output files; see the evidence directory.

package/dist/cli.d.ts

@@ -0,0 +1,2 @@
+#!/usr/bin/env bun
+export {};