@einsia/agent-git 0.1.0 → 0.1.2

package/CHANGELOG.md

@@ -0,0 +1,112 @@
+# Changelog
+
+Every notable change to agit, the AgentGit CLI, by release. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and versions follow
+[Semantic Versioning](https://semver.org/). A version's section here is the body of
+its [GitHub Release](https://github.com/Einsia/agent-git/releases), and the
+`@einsia/agent-git` npm package ships this file.
+
+## [0.1.2] - 2026-09-12
+
+### Added
+
+- **Session files with explicit staging.** Use `agit file` to add, inspect, commit,
+  retrieve and link deliverables in a selected branch without changing its conversation
+  VIEW. File staging remains separate from automatic turn settlement.
+- **Windows x64 distribution.** Install the native Windows CLI through npm or
+  download the executable from the GitHub Release, including remote-control support.
+- **More remote-control workflows.** Connect existing Codex conversations through
+  the native inbox, use OpenCode remote control and transcript snapshots, and navigate
+  between connected machines and their workspaces.
+- **Richer history inspection.** Inspect saved VIEWs and LOGs, raw native JSONL and
+  archived evidence; compare semantic prefixes and unsettled native turns with `diff`.
+- **Scoped search and integrity checks.** Search authenticated repository scopes,
+  inspect incomplete-result diagnostics, and run bounded, read-only `doctor` checks.
+- **Safer import and review.** Choose native-session lineage explicitly, preview and
+  name sessions interactively, and review committed VIEWs with guarded scan remedies.
+
+### Changed
+
+- **Explicit session targeting.** Use `owner/repo@branch` or `AGIT_SESSION` for
+  automation. Interactive commands offer target selection; `agit switch` and implicit
+  workspace targeting are removed. Update scripts that depended on those defaults.
+- **Structured agent output.** JSON output includes typed recovery actions, while
+  human output identifies verified targets and quiet mode suppresses progress output.
+- Merge-agent exploration remains available as archived evidence and visible session
+  history without adding that exploration to the merged VIEW.
+
+### Fixed
+
+- Preserve Codex fork history, portable provider metadata, mixed-runtime sharing and
+  paired tool evidence during capture, resume and export.
+- Preserve reference, network, authentication, policy and cancellation error categories;
+  bind credentials to the selected Hub and validate setup before applying changes.
+- Keep failed remote API turns responsive, preserve shared-message authors and native
+  execution feedback, and support HTTP CONNECT proxies between `agitd` and the Hub.
+- Validate imports before adoption, prevent duplicate runtime claims, guard resume
+  against tracking divergence, and preserve private-publication checks.
+- Avoid repository-wide migration scans on clean stores and skip tags already present
+  on a verified remote during push.
+
+## [0.1.1] - 2026-09-04
+
+### Added
+
+- **A terminal interface for people.** `agit`, `agit resume`, `agit new`, `agit log`,
+  `agit import`, `agit init` and `agit config` open a full-screen interface when run in
+  an interactive terminal without their key argument: browse sessions, repositories,
+  the timeline and conversation content; name and adopt sessions that are not tracked
+  yet; an `init` wizard and a `config` editor; hand the terminal to Claude Code or
+  Codex and come back to refreshed lists. Pipes, CI, scripts and agent sessions keep
+  the existing output, and `--no-tui`, `AGIT_TUI=0` or any machine-output flag
+  (`--json`, `-q`, `-y`) turns it off. See [docs/07_tui.md](docs/07_tui.md).
+- **Update check.** On user-facing startup agit checks, at most once a day, whether the
+  hub announces a newer release and prints a reminder; `agit upgrade` installs it.
+  Nothing upgrades on its own.
+- **A file keystore for machines without a credential store.** On an SSH login or a CI
+  runner no Secret Service answers, so the secret-filter key had nowhere to go and the
+  first `agit commit` whose transcript carried a heuristic finding failed with "cannot
+  open the operating-system credential store". `agit config secrets.keystore file` (or
+  `AGIT_SECRETS_KEYSTORE=file`) keeps the key in a private file under
+  `$AGIT_HOME/keystore/` instead. Unix only, chosen explicitly and never a silent
+  fallback; its protection is the file mode, so a backup of `$AGIT_HOME` carries the key
+  along with the global vault — the boundary is drawn in
+  [docs/05_global_secret_filter.md](docs/05_global_secret_filter.md).
+- **`agit doctor` reports the secret keystore.** It probes the configured store the way
+  a commit uses it and unlocks the vault if one exists, so a machine that cannot hold
+  the key shows up at setup time rather than at the first commit that finds a secret.
+
+### Fixed
+
+- `agit fork` of a sealed branch no longer produces a sealed branch: the seal marker is
+  branch-local and is dropped when the fork gets its identity (issue 23).
+- Codex sessions under a custom `CODEX_HOME` are discovered and settled, and the
+  SessionStart and Stop hooks locate the session and settle it correctly.
+- Missing local branches, phantom `origin` branches, the log limit's performance, and
+  cursor restoration after leaving the interface.
+- When the OS credential store is unavailable, the error names both remedies — install
+  and configure a credential store, or select the file keystore. Every other keyring
+  error keeps its own meaning.
+- Hints are highlighted in bright magenta so they stand out from ordinary output.
+
+### Internal
+
+- The GitHub mirror job clears stale replace refs before planting the graft, so a reused
+  runner checkout no longer aborts the mirror.
+
+## [0.1.0] - 2026-09-01
+
+First public release.
+
+- Lossless version control for agent sessions: `agit import`, `commit`, `push`, `clone`
+  and `resume` for Claude Code, Codex, OpenCode and Cursor.
+- Session lines as branches, workspaces, forks and merges across several people.
+- Secret scanning before publishing, a device-local filter for registered low-entropy
+  secrets, and reversible repository-local placeholders.
+- Distribution through npm — `npx -y create-agit` or `npm i -g @einsia/agent-git` — with
+  per-platform packages for Linux and macOS on x64 and arm64, and GitHub Release
+  artifacts with `SHA256SUMS`.
+
+[0.1.2]: https://github.com/Einsia/agent-git/releases/tag/agit-v0.1.2
+[0.1.1]: https://github.com/Einsia/agent-git/releases/tag/agit-v0.1.1
+[0.1.0]: https://github.com/Einsia/agent-git/releases/tag/agit-v0.1.0

package/README.md

@@ -11,24 +11,46 @@ cleaned up at any moment. `agit` puts snapshots and versions on top of them,
 so "that conversation last Wednesday that finally cracked the bug" becomes
 something you can find, continue, and hand to a teammate.
 
+```text
+agit                              choose a session to continue
+agit new                          choose a repo and name a fresh conversation
+agit import                       choose an existing runtime conversation to adopt
+agit log                          choose a session and browse its history
+agit push                         choose a saved session to publish
+agit share                        choose a session and review link settings
+agit open owner/repo@ref           open a saved source, forking when needed
 ```
-agit import <session> -n <agent>   adopt an existing claude / codex / opencode / cursor session and record its first version
-agit commit <agent>                record another version (snapshot of the session's full current content)
-agit push <agent>                  publish to the hub, get a link
-agit clone <owner>/<agent>         fetch (with git history) and pick up right away; --mine creates a copy under your name
-agit upgrade                       upgrade the CLI itself to the latest release the hub announces
-```
+
+These bare commands open their interfaces in a human terminal. `agit resume`
+continues the same session and never forks; `agit open` can start a new writable
+session from a tag, historical point or another author's source. `agit run`
+remains a compatibility alias for `open`.
+
+Inside an adopted agent session, `agit commit` saves completed turns and
+`agit push` publishes that session. For scripts, pass the target explicitly,
+for example `agit push owner/repo@branch --json`. Directory branch pins do not
+choose targets for `commit`, `push` or `share`.
+
+On user-facing startup, `agit` checks for a newer release at most once a day and prints a
+reminder to stderr; it never upgrades automatically. JSON/quiet/CI and internal hook/MCP paths
+skip this reminder.
 
 Adopting and recording the first version are one command — the in-between
 state ("linked, but unversioned") means nothing to anyone. To mark a session
 without versioning it (e.g. offline), pass `--link-only`.
 
-`agit clone` is **read-only by default**: nothing is created in your name,
-`origin` points at the source, the session is installed into your runtime and
-you can `agit commit` locally as usual. When you decide to take over, use
-`--mine` — that creates your copy on the hub, repoints `origin` at it, and
-remembers the source as `upstream`. Running `agit push` from a read-only
-checkout offers exactly that.
+Use a full native session ID and an explicit runtime and destination for lineage discovery.
+The terminal offers verified local bases, independent import, or cancellation. Noninteractive
+calls return choices without writing; pass `--onto <ref>` or `--independent` to select a path.
+`--propose-lineage` prints a read-only report without adopting the session.
+Inspecting lineage in an existing repository requires NUL-framed Git worktree output,
+normally available in Git 2.36 or newer. An unsupported Git reports `git_worktree_format`;
+explicit `--onto`, `--independent`, and `--link-only` imports retain their ordinary checks.
+
+`agit clone` fetches repository history locally. Use `agit open` or `agit resume`
+to start a runtime. A clone is **read-only by default** on the Hub: nothing is
+created in your name and `origin` points at the source. `agit clone --mine`
+creates your copy, repoints `origin` and remembers the source as `upstream`.
 
 The full command list is in `agit --help`.
 
@@ -45,9 +67,13 @@ agit --version
 
 Both routes install a prebuilt binary — no Rust toolchain required. npm
 picks the platform sub-package matching your `os`/`cpu`; on platforms with no
-prebuilt binary (e.g. Windows) running `agit` prints the source-build recipe.
+prebuilt binary (e.g. FreeBSD) running `agit` prints the source-build recipe.
 Details and environment variables: [`npm/README.md`](npm/README.md).
 
+Windows x64 packages include the local RC daemon. Its control channel uses a local named
+pipe restricted to the current Windows user. RC state requires a private, user-owned
+directory; shared or redirected RC paths are rejected.
+
 pnpm (v10+) does not run dependency install scripts by default, so the
 automatic `agit setup` is skipped there — run `agit setup` once yourself
 after installing.
@@ -80,7 +106,7 @@ the binary to `~/.local/bin/agit`. Common flags:
 ```
 
 To build a binary whose built-in hub is the staging deployment, set the build-time default
-explicitly. Runtime `AGIT_HUB_URL` and `agit config set hub.url ...` still take precedence:
+explicitly. Runtime `AGIT_HUB_URL` and `agit config hub.url ...` still take precedence:
 
 ```sh
 AGIT_DEFAULT_HUB_URL=https://staging.agent-git.com cargo build --release --locked
@@ -114,6 +140,7 @@ unreleased versions".
 | Probed storage formats of each runtime  | [`docs/mechanism-probing/`](docs/mechanism-probing/)          |
 | npm package behavior and env vars       | [`npm/README.md`](npm/README.md)                              |
 | Release artifact naming contract        | [`.github/RELEASE_ARTIFACTS.md`](.github/RELEASE_ARTIFACTS.md) |
+| What changed in each release            | [`CHANGELOG.md`](CHANGELOG.md)                                |
 
 The server (**AgentGit**) is a separate repository, deployed on its own.
 
@@ -127,6 +154,13 @@ agree with it (`node scripts/check-version.js` — run in CI and before
 node scripts/bump-version.mjs 0.1.0    # Cargo.toml + Cargo.lock + all npm manifests
 ```
 
+Release notes live in [`CHANGELOG.md`](CHANGELOG.md), and they come first: write the
+version's `## [x.y.z]` section, then bump. `bump-version.mjs` refuses to touch a file for
+a version that has no section, and `check-version.js` refuses one in CI and before `npm pack`.
+The section becomes the GitHub Release body (`scripts/release-notes.mjs` extracts it in
+`release.yml`, with repository-relative links pinned to the release tag) and ships inside
+the `@einsia/agent-git` package.
+
 Pushing the tag runs the whole chain — binaries first, npm right after:
 
 ```sh

package/npm/README.md

@@ -40,6 +40,7 @@ The hub (**AgentGit**) is not in this package; it deploys separately.
 | Linux | aarch64/arm64 | `@einsia/agent-git-linux-arm64`   |
 | macOS | x86_64        | `@einsia/agent-git-darwin-x64`    |
 | macOS | arm64         | `@einsia/agent-git-darwin-arm64`  |
+| Windows | x86_64      | `@einsia/agent-git-win32-x64`    |
 
 **Linux binaries are musl static-linked — no glibc floor.** Verified on Alpine,
 Amazon Linux 2 (glibc 2.26), Debian 11/12, Ubuntu 20.04–24.04, x86_64 and
@@ -48,7 +49,7 @@ arm64. No more `libc.so.6: version 'GLIBC_2.xx' not found`.
 On macOS, if Node runs under Rosetta (it reports itself as x64) the installer
 detects it and installs the arm64 build.
 
-Unsupported platforms (including Windows) get no prebuilt binary: running
+Unsupported operating system and architecture pairs get no prebuilt binary: running
 `agit` prints build-from-source instructions. On WSL, the Linux binary works.
 
 ## Failure behavior
@@ -73,3 +74,9 @@ Unsupported platforms (including Windows) get no prebuilt binary: running
 `agit upgrade` asks the hub for the latest CLI version and downloads the
 platform package tarball straight from the npm registry, verified against the
 registry's SRI (sha512) before anything is replaced.
+
+Windows packages contain `agit.exe`. The `create-agit` installer writes it to
+`%USERPROFILE%\.local\bin`; add that directory to your user PATH if the installer
+reports that it is missing. Windows source builds need Rust and the MSVC C/C++
+toolchain. The local RC daemon uses a current-user Windows named pipe and private
+RC state. It refuses shared or redirected RC paths instead of changing their permissions.

package/npm/lib/platform.js

@@ -10,13 +10,13 @@ const { spawnSync } = require('child_process');
 //
 // Linux is musl static linking: a gnu artifact built on ubuntu:24.04 locks in
 // GLIBC_2.39 and nothing starts on older distributions; musl's static-pie has
-// no interpreter, so it has no glibc floor. No win32: the release pipeline
-// produces no windows artifacts.
+// no interpreter, so it has no glibc floor.
 const KEYS = {
   'linux/x64': 'linux-x64',
   'linux/arm64': 'linux-arm64',
   'darwin/x64': 'darwin-x64',
   'darwin/arm64': 'darwin-arm64',
+  'win32/x64': 'win32-x64',
 };
 
 // Platform key → Rust target triple (CI names artifact archives by triple).
@@ -25,6 +25,7 @@ const TRIPLES = {
   'linux-arm64': 'aarch64-unknown-linux-musl',
   'darwin-x64': 'x86_64-apple-darwin',
   'darwin-arm64': 'aarch64-apple-darwin',
+  'win32-x64': 'x86_64-pc-windows-msvc',
 };
 
 function packageName(key) {
@@ -42,8 +43,7 @@ function realArch(nodePlatform, nodeArch) {
   return !r.error && r.status === 0 && (r.stdout || '').trim() === '1' ? 'arm64' : arch;
 }
 
-// Returns this machine's platform key; an unsupported platform (win32, for
-// example) returns null and the caller picks the wording.
+// Unsupported operating system and architecture pairs have no platform key.
 function packageKey(nodePlatform, nodeArch) {
   const platform = nodePlatform || process.platform;
   const arch = nodeArch === undefined ? realArch() : nodeArch;

package/npm/lib/run.js

@@ -21,7 +21,7 @@ function run() {
 
   if (!bin) {
     // npm skipped the optional dep for this os/cpu = this platform has no
-    // prebuilt artifact (win32, freebsd, ...). This block is often everything
+    // prebuilt artifact (freebsd, ...). This block is often everything
     // the user sees, so on its own it has to say why there is no binary and
     // which command fixes it.
     log.error(`no prebuilt agit binary for ${process.platform}/${process.arch}.`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@einsia/agent-git",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Version control for agent sessions — the agit CLI plus skills/hooks/MCP wiring for Claude Code, Codex, OpenCode and Cursor. The AgentGit hub deploys separately.",
   "keywords": [
     "agit",
@@ -33,7 +33,8 @@
     "npm/postinstall.js",
     "npm/lib/",
     "npm/README.md",
-    "README.md"
+    "README.md",
+    "CHANGELOG.md"
   ],
   "scripts": {
     "postinstall": "node npm/postinstall.js",
@@ -48,9 +49,10 @@
     "access": "public"
   },
   "optionalDependencies": {
-    "@einsia/agent-git-linux-x64": "0.1.0",
-    "@einsia/agent-git-linux-arm64": "0.1.0",
-    "@einsia/agent-git-darwin-x64": "0.1.0",
-    "@einsia/agent-git-darwin-arm64": "0.1.0"
+    "@einsia/agent-git-linux-x64": "0.1.2",
+    "@einsia/agent-git-linux-arm64": "0.1.2",
+    "@einsia/agent-git-darwin-x64": "0.1.2",
+    "@einsia/agent-git-darwin-arm64": "0.1.2",
+    "@einsia/agent-git-win32-x64": "0.1.2"
   }
 }