@einsia/agent-git 0.2.22 → 0.2.25

package/CHANGELOG.md

@@ -8,6 +8,133 @@ its [GitHub Release](https://github.com/Einsia/agent-git/releases), and the
 
 ## [Unreleased]
 
+## [0.2.25] - 2026-10-25
+
+### Added
+
+- `agit privacy mode OWNER/REPO@BRANCH plain` selects unencrypted publication before a session's
+  first remote registration. The choice follows the logical session across branches, keeps source
+  history unchanged, and is separate from repository visibility. Use `encrypted` to opt into
+  encryption before registration, or omit the mode to inspect the local choice and registered mode.
+
+- `agit privacy policy tool [NAME] --omit true|false` controls calls and results together, with
+  exact tool-name and runtime-qualified overrides. `--reset` removes a named override.
+- `agit privacy policy attachment omit|metadata|original` controls recorded attachments in
+  encrypted public views, privacy exports and shares. Plain push retains its existing path.
+
+### Changed
+
+- New sessions, first imports and independent forks default to plain publication again.
+  0.2.24 created them with encrypted publication by default, which its release notes did not
+  mention. Existing recorded and registered modes are preserved, including those of sessions
+  0.2.24 created. Select `privacy mode OWNER/REPO@BRANCH encrypted` before registration to
+  enable encryption.
+- Privacy projections default to visible tools and original attachments, including when an
+  existing policy omits the new fields. Configure omission explicitly to hide them. Captured
+  file-tool content no longer requires a workspace/include match; explicit and mandatory file
+  exclusions remain effective. Readable text remains sanitized; recorded binary carriers are retained.
+
+### Fixed
+
+- A privacy dictionary upload that the Hub, or a network policy in front of it, refuses is no
+  longer sent again on every push, fetch, clone and login. agit retries it after a delay that
+  starts at 10 minutes and grows to 6 hours, and keeps downloading dictionaries from other
+  devices meanwhile. `agit push` and `agit doctor` say whether a network policy or the Hub
+  refused it; `agit login` retries at once.
+
+- Publication notices distinguish configured hiding, attachment handling, unsupported formats
+  and unverifiable sources. Omitted tools preserve call/result classification instead of opening
+  user turns, and activity summaries exclude both legacy and specific omission notices.
+
+- Encrypted publication restores originals against a frozen dictionary across all batches and
+  resolves evidence references independently of LOG order. Repeated events no longer fail with
+  "hydration has ambiguous evidence provenance" after partial foreground hydration or forward
+  evidence references; unavailable mappings stop preparation before upload.
+
+- Raise the sanitized public projection budget to 64 MiB to match the private ciphertext budget,
+  so large session displays can be published alongside their encrypted originals. The complete
+  envelope remains bounded to 128 MiB.
+
+- `agit push` previews session branches with a long plain history instead of failing with
+  "plain preview exceeds its content budget", and prepares them substantially faster. The
+  preview shows each distinct file version once and an append-only file as the bytes it adds.
+- After a macOS restart, `agit rc status`, `agit upgrade` and daemon startup
+  recognize the control socket a stopped daemon left behind and reclaim it,
+  instead of asking for a manual `agit rc local recover`.
+- Loading earlier messages of a remote conversation whose saved archive could not
+  be applied no longer fails as an expired history snapshot; the page kept
+  spinning on "Loading the latest conversation" while it retried.
+- A conversation taken over from a registered runtime source keeps the name the
+  device shows for it, instead of appearing as an untitled session in its
+  project.
+- Encrypted publication preserves Git authors, committers, timestamps, message encoding and
+  commit messages. Existing published snapshots remain compatible when history continues.
+
+## [0.2.24] - 2026-10-21
+
+### Added
+
+- `agit activity` and its MCP tool query a person's saved user and assistant messages
+  over an explicit time range, with optional session selection and JSON pagination.
+  Results are grouped by saved commit, oldest first, and a cursor keeps working while
+  new work is saved. Existing clones are fetched once per query and read locally;
+  other repositories are queried on the Hub without cloning. Encrypted publications
+  use accepted account attribution and publication time, and incompleteness is
+  reported for the whole query. `--assistant last` keeps every user message but only the
+  final assistant reply to each. Requires a Hub supporting activity schema version 3.
+
+### Fixed
+
+- The bundled Linux Git runtime uses the current Alpine builds of expat, c-ares
+  and the CA bundle; the previous builds are no longer published, so release
+  builds could not assemble the runtime.
+- Remote control opens Codex conversations that have been idle long enough for
+  Codex to compress their transcript, and conversations Codex continued in a
+  new transcript segment. Such conversations stayed on "Restoring
+  conversation", returned history errors, and never archived their turns.
+  Restoring a compressed transcript no longer pauses other conversations on the
+  machine.
+- A failed or timed-out remote resume releases the conversation once its
+  processes have exited, instead of keeping it busy until the daemon restarts.
+  A capture binding that cannot be resolved no longer blocks control: the
+  conversation runs, and its turns archive once the binding resolves again.
+- Re-registering a runtime source, or upgrading or removing the Codex program it
+  was registered with, keeps existing conversations controllable and their
+  captures valid.
+- Busy and refusal errors say whether they clear on their own, so clients retry
+  passing conditions silently and show the ones that need a person. A refused
+  cloud connection is answered with its reason instead of being dropped, and
+  subscribing to a paused conversation reports that it needs a resume.
+- Opening history no longer copies the transcript and no longer fails while the
+  runtime is writing to it. Identical history requests share one read, and
+  history of a conversation whose folder was removed stays readable.
+- Archive recovery backs off, parks failures that cannot succeed, and lets a
+  resume take the conversation. A conversation larger than the capture budget
+  is reported once instead of after every turn.
+- The control channel keeps a slow or lagging reader connected, stops reads
+  whose requester has left, evicts idle clients before refusing new ones, and
+  reconnects within seconds after the machine wakes from sleep. A message sent
+  again while its first delivery is in flight reports that delivery as pending
+  and is never run twice.
+- Claude Code conversations whose transcript Claude deleted, or that never
+  received a message, reopen under their own id; one whose archived turns no
+  longer have a transcript points to `agit resume`. Claude Code is found outside
+  the daemon's PATH, bypass mode is not offered where Claude refuses it as root,
+  transcript folders follow Claude's naming for long and non-BMP paths, and a
+  terminal Claude session that cannot be shared says why.
+- A failed `agit clone` suggests asking for the owner's grant only when Git
+  reports an authentication failure; any other failed transfer suggests
+  retrying and, if it fails the same way again, reporting it with the output.
+  `agit fetch <owner/repo>` likewise offers the grant hint only when the Hub
+  refuses access. A reader who already had access was sent to check
+  collaborator grants after an interrupted transfer.
+- `agit project bind --history all`, its `--dry-run` preview and `agit project sync`
+  include Claude Code conversations that open with a large prompt, such as a pasted
+  screenshot, instead of silently leaving them out of the project.
+- `agit project bind --dry-run` refuses a directory that is already bound to
+  another repository, as the bind itself does, instead of previewing a bind that
+  would fail.
+
 ## [0.2.22] - 2026-10-07
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@einsia/agent-git",
-  "version": "0.2.22",
+  "version": "0.2.25",
   "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",
@@ -49,10 +49,10 @@
     "access": "public"
   },
   "optionalDependencies": {
-    "@einsia/agent-git-linux-x64": "0.2.22",
-    "@einsia/agent-git-linux-arm64": "0.2.22",
-    "@einsia/agent-git-darwin-x64": "0.2.22",
-    "@einsia/agent-git-darwin-arm64": "0.2.22",
-    "@einsia/agent-git-win32-x64": "0.2.22"
+    "@einsia/agent-git-linux-x64": "0.2.25",
+    "@einsia/agent-git-linux-arm64": "0.2.25",
+    "@einsia/agent-git-darwin-x64": "0.2.25",
+    "@einsia/agent-git-darwin-arm64": "0.2.25",
+    "@einsia/agent-git-win32-x64": "0.2.25"
   }
 }