@einsia/agent-git 0.2.13 → 0.2.15

package/CHANGELOG.md

@@ -8,6 +8,86 @@ its [GitHub Release](https://github.com/Einsia/agent-git/releases), and the
 
 ## [Unreleased]
 
+## [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
+
+- `agit project bind` enrolls a selected directory and its unbound subdirectories
+  in an existing repository, with explicit history import and automatic upload
+  choices. `project sync` retries synchronization, `project status` reports local
+  results, and `project unbind` pauses project capture. Codex and Claude Code hooks
+  preserve existing session claims and enforce the current project policy before
+  publishing.
+
+### Fixed
+
+- Repeated Remote Control history reads reuse bounded, authenticated secret
+  dictionary records and compiled protection patterns. Changed ciphertext,
+  keys, or protection rules invalidate the corresponding cached state.
+- Release builds optimize for runtime speed to reduce history projection and
+  secret scanning latency.
+- Remote Control retries failed local session saves while idle, without requiring
+  another user turn to resume archiving.
+- Push uses authenticated remote history to avoid rescanning already-published
+  objects, while continuing to inspect new objects and their selected LFS payloads.
+  Use `--audit` when a complete history review is needed.
+- Native history reads take authenticated, bounded dictionary snapshots without
+  waiting for a dictionary writer. Conservative pattern filtering avoids scanning
+  history for secret patterns that cannot occur while preserving redaction rules.
+- Compatible Cloud servers can read native history through a scoped project
+  controller without opening a separate session controller. Project controllers
+  remain read-only and cannot subscribe to or change a conversation.
+- Completed RC turns retain durable archive jobs until protected publication has
+  a receipt. A daemon restart retries pending jobs without starting the model or
+  requiring a viewer to open the conversation.
+- Settlement subprocesses retry temporary executable-busy failures within a
+  bounded window while retaining the current authority lease.
+
 ## [0.2.13] - 2026-09-30
 
 ### Changed

package/package.json

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