@einsia/agent-git 0.2.14 → 0.2.16

package/CHANGELOG.md

@@ -8,6 +8,104 @@ its [GitHub Release](https://github.com/Einsia/agent-git/releases), and the
 
 ## [Unreleased]
 
+## [0.2.16] - 2026-10-02
+
+### Added
+
+- Each settled commit records the runtime's own name for the session in
+  `session/meta.json` as `title`: the latest Claude Code title (`custom-title`,
+  falling back to an older transcript's `summary`) or the Codex thread name from
+  `session_index.jsonl`. A rename appears from the next settlement on. The
+  `agit: unnamed` and `agit <owner/repo@branch>` placeholders that agit's own
+  SessionStart hook assigns are not recorded. The title is protected like other
+  metadata observations and is not part of encrypted metadata projection.
+
+### Changed
+
+- Privacy processing runs in a bounded local worker. Detected secrets receive
+  reversible placeholders when their originals can be saved. Incomplete scans
+  keep completed replacements; unavailable storage, scan failures and timeouts
+  skip the affected privacy work and let conversation operations continue.
+- Signed-in accounts obtain an automatically generated cloud dictionary key.
+  Without a usable key, mappings remain in private local pending storage. Push,
+  login and fetch schedule encrypted dictionary synchronization independently;
+  another signed-in device can restore mappings after synchronization succeeds.
+- Local default, global user and repository user rules share one policy path.
+  Explicit blocks override allows, and allows override heuristic findings.
+  Recovery records survive rule changes without becoming permanent block rules.
+- Uploads require no secret-finding review or cloud privacy-policy resolution.
+  Existing Git history is preserved. LFS payloads are outside privacy processing;
+  their authorization, availability and integrity checks remain in place.
+- This release requires the matching backend update to remove older server
+  privacy gates. A skipped local transformation may retain original sensitive
+  content, and pending dictionaries become recoverable on other devices only
+  after successful encrypted synchronization.
+
+- Project Stop hooks start session uploads in a background process and return
+  immediately. Project status reports the resulting upload state.
+
+### Fixed
+
+- Automatic project binding installs hooks for available runtimes that support
+  them; other runtime sessions remain publishable through project sync.
+
+- Live output preserves every emitted fragment and the remaining stream tail
+  when local privacy processing is unavailable.
+- Legacy native message identifiers stored as secret placeholders can be restored
+  without changing unmasked carrier identities.
+
+- `agit project sync` publishes a session that another repository already claims, such
+  as one started from a desktop RC project, as a separate copy of that claim's branch
+  in the project repository, instead of failing with "session already belongs to another
+  repository". The original claim and the RC project's own publication target are
+  unchanged; each later sync refreshes the copy. `--history none` keeps excluding such
+  earlier sessions.
+
+## [0.2.15] - 2026-10-01
+
+### Changed
+
+- **New repositories use ordinary publication by default again.** Without
+  `--encryption` or a `privacy.encryption` preference, `agit push`, `agit init`,
+  `agit repo create` and the init wizard create repositories that publish original
+  history and need no viewing password. Encryption is an explicit opt-in chosen at
+  creation with `--encryption=true` or `agit config privacy.encryption true`, after
+  which `agit privacy init` sets the viewing password. `agit privacy init` still
+  creates a missing repository encrypted unless `false` is chosen, and existing
+  repositories keep the mode they were created with. A separate `agit push --to`
+  destination created from an encrypted repository stays encrypted unless
+  `--encryption=false` or a `privacy.encryption` preference chooses otherwise.
+- Local repositories set up by 0.2.13 or 0.2.14 without an explicit `--encryption`
+  choice follow the new default. If `push.auto` is on and the repository does not
+  exist on the Hub yet, the next automatic push creates it as an ordinary repository,
+  private unless `push.visibility` says otherwise. To keep such a repository
+  encrypted, run `agit privacy init OWNER/REPO` first, or set
+  `agit config --global privacy.encryption true`.
+- A checkout initialized with `agit init --encryption=true` refuses its first push
+  to an existing repository that uses ordinary publication, instead of silently
+  publishing original history there; pass `--encryption=false` to publish anyway,
+  or push to a new repository name to create an encrypted one.
+- Encrypted `agit share` links require an encrypted repository. Sharing from an
+  ordinary repository needs `--public`; without it the command now says so and
+  uploads nothing, instead of asking for a publication that cannot exist. Encrypted
+  links for ordinary repositories are not available in this release.
+
+### Fixed
+
+- Ordinary pushes from scripts, CI and agent sessions no longer require `--yes`;
+  a person at a terminal is still asked to confirm the destination, and declining
+  or cancelling that prompt publishes nothing. Secret findings still block
+  publication unless `--allow-secrets` is given, and encrypted publication keeps
+  its confirmation.
+- Automatic ordinary pushes after settlement, and Remote Control publication to an
+  ordinary repository, no longer need a prior explicit push. `push.auto` authorizes
+  them and they pass the same identity, access and secret checks as a manual push.
+  Outside Remote Control, a missing repository is created with the visibility a
+  non-interactive first push uses. Encrypted repositories still require an explicit
+  push to confirm their policy and viewing recipient before automatic publication.
+- Remote Control retires temporary runtime sources automatically once their
+  directories disappear.
+
 ## [0.2.14] - 2026-09-30
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@einsia/agent-git",
-  "version": "0.2.14",
+  "version": "0.2.16",
   "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.14",
-    "@einsia/agent-git-linux-arm64": "0.2.14",
-    "@einsia/agent-git-darwin-x64": "0.2.14",
-    "@einsia/agent-git-darwin-arm64": "0.2.14",
-    "@einsia/agent-git-win32-x64": "0.2.14"
+    "@einsia/agent-git-linux-x64": "0.2.16",
+    "@einsia/agent-git-linux-arm64": "0.2.16",
+    "@einsia/agent-git-darwin-x64": "0.2.16",
+    "@einsia/agent-git-darwin-arm64": "0.2.16",
+    "@einsia/agent-git-win32-x64": "0.2.16"
   }
 }