@vaur94/agz-memory 0.5.1 → 0.5.2

package/ARCHITECTURE.md

@@ -1,6 +1,6 @@
 # AGZ Memory Architecture
 
-This document describes the `0.5.1` runtime and SQLite schema v11.
+This document describes the `0.5.2` runtime and SQLite schema v11.
 
 ## System Boundaries
 
@@ -20,7 +20,7 @@ OpenCode V2 beta-18743
 
 SQLite outbox
   -> optional derived retrieval backend
-      -> disabled in 0.5.1; backend = none
+      -> disabled in 0.5.2; backend = none
 ```
 
 The MCP adapter owns tool schemas, annotations, and result envelopes. The core
@@ -98,7 +98,10 @@ Capture requires all of these gates:
 
 1. The plugin version and running OpenCode beta match exactly.
 2. Mode is not `off`, capture is enabled, and exactly one explicit binding
-   matches project ID, workspace ID, and canonical directory.
+   matches project ID, workspace ID, and canonical directory. A linked Git
+   worktree may match its main checkout only after reciprocal worktree metadata
+   proves that both use the same common Git directory; persisted binding paths
+   are not rewritten.
 3. Only terminal user/assistant text or terminal tool status is projected.
 4. Credential and private-key patterns are removed or quarantined.
 5. The strict `CaptureEventV2` parser enforces UTF-8 size, kind-specific source identity, event
@@ -133,7 +136,7 @@ original OpenCode context unchanged.
 
 Semantic providers implement an optional backend contract: project-filtered
 query, idempotent upsert, deterministic delete, full project purge, and health.
-No provider is enabled in `0.5.1`. The SQLite lexical/graph path remains fully
+No provider is enabled in `0.5.2`. The SQLite lexical/graph path remains fully
 functional without one.
 
 ## Derived Index Outbox

package/CHANGELOG.md

@@ -3,9 +3,24 @@
 All notable changes to AGZ Memory are recorded here. The project follows
 [Semantic Versioning](https://semver.org/).
 
-## [0.5.1] - 2026-09-04
+## [0.5.2] - 2026-09-04
+
+### Changed
+
+- Updated linked Git worktree guidance so a main checkout and its linked
+  worktrees safely reuse the same `memoryProjectID` after Git metadata confirms
+  the shared common directory.
+- Preserved persisted binding path and key compatibility while allowing distinct
+  OpenCode project/workspace identities to map to that shared memory project.
+- Aligned release metadata, package examples, and bilingual operational guidance
+  with the 0.5.2 release surface.
 
-> Candidate metadata only; no npm publication, Git tag, or merge is claimed.
+### Compatibility
+
+- Retained SQLite schema 11, the exact nine-tool MCP contract, and inert plugin
+  defaults across the worktree identity guidance change.
+
+## [0.5.1] - 2026-09-04
 
 ### Changed
 

package/README.md

@@ -10,8 +10,8 @@ as two independently usable packages that advance at the same version:
 - `@vaur94/agz-memory-plugin`: an optional OpenCode V2 adapter for bounded
   retrieval and deliberately staged automatic capture.
 
-**0.5.1 status:** This repository documents a candidate only. It does not claim
-npm publication, a Git tag, or a merge.
+**0.5.2 status:** This repository documents the 0.5.2 release surface and
+compatibility contract; npm publication and Git hosting state are tracked separately.
 
 The MCP server is ready for normal use. The plugin starts inert: no project is
 created, no session is captured, and no context is injected until an explicit
@@ -35,8 +35,8 @@ binding and rollout mode are configured.
 
 | Component | Supported version |
 |---|---|
-| Core and MCP | `0.5.1` |
-| OpenCode plugin | `0.5.1` |
+| Core and MCP | `0.5.2` |
+| OpenCode plugin | `0.5.2` |
 | OpenCode V2 | `0.0.0-beta-18743` |
 | `@opencode-ai/plugin` | `0.0.0-beta-18743` |
 | Bun | `>=1.3.14` |
@@ -50,7 +50,7 @@ itself unless the running OpenCode version exactly matches the supported beta.
 Run the server directly:
 
 ```sh
-bunx @vaur94/agz-memory@0.5.1
+bunx @vaur94/agz-memory@0.5.2
 ```
 
 Or register it in OpenCode V2 under `mcp.servers`:
@@ -58,13 +58,13 @@ Or register it in OpenCode V2 under `mcp.servers`:
 ```jsonc
 {
   "skills": [
-    "https://raw.githubusercontent.com/ugur-murat-alt/agz-memory/v0.5.1/skills/"
+    "https://raw.githubusercontent.com/ugur-murat-alt/agz-memory/v0.5.2/skills/"
   ],
   "mcp": {
     "servers": {
       "agz-memory": {
         "type": "local",
-        "command": ["bunx", "@vaur94/agz-memory@0.5.1"],
+        "command": ["bunx", "@vaur94/agz-memory@0.5.2"],
         "environment": {
           "OPENCODE_MEMORY_DATABASE_PATH": "{env:OPENCODE_MEMORY_DATABASE_PATH}"
         },
@@ -114,7 +114,8 @@ OpenCode exposes the tools with the configured server prefix, for example
 Recommended sequence:
 
 1. Call `project_list` and reuse an existing project when it represents the
-   same durable workspace.
+   same durable workspace. Git linked worktrees are separate checkouts of that
+   workspace and must reuse its `projectID`.
 2. Call `project_create` only when no matching project exists.
 3. Keep the returned `projectID`; names can change, UUIDs cannot.
 4. Call `memory_recall` before relying on historical decisions.
@@ -133,7 +134,7 @@ options:
 {
   "plugins": [
     {
-      "package": "@vaur94/agz-memory-plugin@0.5.1",
+      "package": "@vaur94/agz-memory-plugin@0.5.2",
       "options": {
         "mode": "off",
         "autoCreateProjects": false,
@@ -174,9 +175,13 @@ an OpenCode project/workspace/location to an existing AGZ Memory project:
 ```
 
 `memoryProjectID` must come from `project_list`. The directory is resolved with
-the filesystem and compared with the active OpenCode location. Only a hash of
-that canonical path is persisted. A mismatched location or duplicate mapping
-disables the plugin rather than selecting a project heuristically.
+the filesystem and compared with the active OpenCode location. A main checkout
+and a linked Git worktree are accepted as the same repository only when their
+Git metadata confirms the shared common directory. Configure each distinct
+OpenCode project/workspace identity explicitly, but reuse the same
+`memoryProjectID`; the configured canonical path and its persisted hash remain
+unchanged. An unrelated or unverifiable location and a duplicate mapping disable
+the plugin rather than selecting a project heuristically.
 
 ## Roll Out Safely
 
@@ -206,11 +211,11 @@ quality, and latency gates.
 The admin CLI reads the same `OPENCODE_MEMORY_DATABASE_PATH`:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin doctor
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin backup
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin upgrade --to 11
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin capture status
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin outbox status
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin doctor
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin backup
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin upgrade --to 11
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin capture status
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin outbox status
 ```
 
 Upgrades take an exclusive migration lock and create a verified backup before
@@ -219,7 +224,7 @@ restore. Restore and backup deletion use dry-run output plus explicit
 confirmation values; never guess them.
 
 Use [the backup and restore runbook](docs/backup-restore-runbook.md) for a full
-rehearsal. Final `0.5.1` backup manifests use `agz-memory-backup/1`; prerelease
+rehearsal. The `0.5.2` backup manifests use `agz-memory-backup/1`; prerelease
 manifests must be handled by the prerelease that created them.
 
 ## Security Model

package/README.tr.md

@@ -10,8 +10,8 @@ Aynı sürümde ilerleyen, birbirinden bağımsız kullanılabilen iki paket sun
 - `@vaur94/agz-memory-plugin`: sınırlı geri çağırma ve bilinçli olarak aşamalı
   otomatik yakalama için isteğe bağlı OpenCode V2 bağdaştırıcısı.
 
-**0.5.1 durumu:** Bu depo yalnızca aday sürüm metadata'sını belgeler; npm
-yayımlama, Git etiketi veya birleştirme iddiası içermez.
+**0.5.2 durumu:** Bu depo 0.5.2 sürüm yüzeyini ve uyumluluk sözleşmesini
+belgeler; npm yayımlama ve Git barındırma durumu ayrı olarak izlenir.
 
 MCP sunucusu normal kullanım için hazırdır. Eklenti hareketsiz başlar: açık bir
 eşleme ve devreye alma modu verilene kadar proje oluşturmaz, oturum yakalamaz ve
@@ -35,8 +35,8 @@ bağlam eklemez.
 
 | Bileşen | Desteklenen sürüm |
 |---|---|
-| Çekirdek ve MCP | `0.5.1` |
-| OpenCode eklentisi | `0.5.1` |
+| Çekirdek ve MCP | `0.5.2` |
+| OpenCode eklentisi | `0.5.2` |
 | OpenCode V2 | `0.0.0-beta-18743` |
 | `@opencode-ai/plugin` | `0.0.0-beta-18743` |
 | Bun | `>=1.3.14` |
@@ -50,7 +50,7 @@ MCP sunucusu bir OpenCode beta sürümüne bağlı değildir. İsteğe bağlı e
 Sunucuyu doğrudan çalıştırın:
 
 ```sh
-bunx @vaur94/agz-memory@0.5.1
+bunx @vaur94/agz-memory@0.5.2
 ```
 
 Ya da OpenCode V2 içinde `mcp.servers` altına kaydedin:
@@ -58,13 +58,13 @@ Ya da OpenCode V2 içinde `mcp.servers` altına kaydedin:
 ```jsonc
 {
   "skills": [
-    "https://raw.githubusercontent.com/ugur-murat-alt/agz-memory/v0.5.1/skills/"
+    "https://raw.githubusercontent.com/ugur-murat-alt/agz-memory/v0.5.2/skills/"
   ],
   "mcp": {
     "servers": {
       "agz-memory": {
         "type": "local",
-        "command": ["bunx", "@vaur94/agz-memory@0.5.1"],
+        "command": ["bunx", "@vaur94/agz-memory@0.5.2"],
         "environment": {
           "OPENCODE_MEMORY_DATABASE_PATH": "{env:OPENCODE_MEMORY_DATABASE_PATH}"
         },
@@ -115,7 +115,8 @@ OpenCode araçları yapılandırılan sunucu önekiyle gösterir; örneğin
 Önerilen sıra:
 
 1. `project_list` çağırın ve aynı kalıcı çalışma alanını temsil eden mevcut
-   projeyi yeniden kullanın.
+   projeyi yeniden kullanın. Git bağlantılı çalışma ağaçları bu çalışma alanının
+   ayrı kod kopyalarıdır ve aynı `projectID` değerini kullanmalıdır.
 2. Yalnız eşleşen proje yoksa `project_create` çağırın.
 3. Dönen `projectID` değerini saklayın; ad değişebilir, UUID değişmez.
 4. Geçmiş kararlara dayanmadan önce `memory_recall` çağırın.
@@ -135,7 +136,7 @@ ayarlarla ekleyin:
 {
   "plugins": [
     {
-      "package": "@vaur94/agz-memory-plugin@0.5.1",
+      "package": "@vaur94/agz-memory-plugin@0.5.2",
       "options": {
         "mode": "off",
         "autoCreateProjects": false,
@@ -176,9 +177,13 @@ OpenCode proje/çalışma alanı/konumunu mevcut AGZ Memory projesine bağlar:
 ```
 
 `memoryProjectID`, `project_list` sonucundan gelmelidir. Dizin gerçek dosya
-sistemi yoluna çözülür ve etkin OpenCode konumuyla karşılaştırılır. Yalnız bu
-kanonik yolun özeti veritabanına yazılır. Yanlış konum veya çift eşleme,
-sezgisel proje seçmek yerine eklentiyi kapatır.
+sistemi yoluna çözülür ve etkin OpenCode konumuyla karşılaştırılır. Ana kod
+kopyası ile bağlantılı Git çalışma ağacı, yalnız Git metadata'sı ortak dizini
+doğruladığında aynı depo kabul edilir. Her farklı OpenCode proje/çalışma alanı
+kimliğini açıkça eşleyin, fakat aynı `memoryProjectID` değerini yeniden kullanın;
+yapılandırılmış kanonik yol ve veritabanındaki özeti değişmez. İlişkisiz veya
+doğrulanamayan konum ya da çift eşleme, sezgisel proje seçmek yerine eklentiyi
+kapatır.
 
 ## Güvenli Devreye Alma
 
@@ -208,11 +213,11 @@ kapılarından geçene kadar `semanticBackend` değeri `none` olmalıdır.
 Yönetim aracı aynı `OPENCODE_MEMORY_DATABASE_PATH` değerini okur:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin doctor
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin backup
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin upgrade --to 11
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin capture status
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin outbox status
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin doctor
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin backup
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin upgrade --to 11
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin capture status
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin outbox status
 ```
 
 Yükseltmeler özel bir geçiş kilidi alır ve veritabanını değiştirmeden önce
@@ -221,7 +226,7 @@ dener. Geri yükleme ve yedek silme işlemleri önce deneme çıktısı, sonra a
 onay değerleri ister; bu değerleri tahmin etmeyin.
 
 Tam prova için [yedekleme ve geri yükleme runbook'unu](docs/backup-restore-runbook.tr.md)
-kullanın. Final `0.5.1` yedek manifestleri `agz-memory-backup/1` kullanır;
+kullanın. `0.5.2` yedek manifestleri `agz-memory-backup/1` kullanır;
 ön sürüm manifestleri onları oluşturan ön sürümle işlenmelidir.
 
 ## Güvenlik Modeli

package/dist/admin.js

@@ -3421,7 +3421,7 @@ function migrateV9ToV10(db) {
 }
 
 // src/version.ts
-var PRODUCT_VERSION = "0.5.1";
+var PRODUCT_VERSION = "0.5.2";
 
 // src/db.ts
 var DDL = `

package/dist/core.js

@@ -3378,7 +3378,7 @@ function migrateV9ToV10(db) {
 }
 
 // src/version.ts
-var PRODUCT_VERSION = "0.5.1";
+var PRODUCT_VERSION = "0.5.2";
 
 // src/db.ts
 var DDL = `

package/dist/server.js

@@ -3394,7 +3394,7 @@ function migrateV9ToV10(db) {
 }
 
 // src/version.ts
-var PRODUCT_VERSION = "0.5.1";
+var PRODUCT_VERSION = "0.5.2";
 
 // src/db.ts
 var DDL = `
@@ -4069,7 +4069,7 @@ import { McpServer } from "@modelcontextprotocol/server";
 
 // src/context.ts
 var MEMORY_GUIDANCE = `Use project-scoped memory for durable facts across sessions.
-- Start with project_list. Reuse a project only when it intentionally represents the same durable workspace or product; create one only when no matching project exists. If the listed projects are ambiguous, ask rather than guessing from a directory or session name.
+- Start with project_list. Reuse a project only when it intentionally represents the same durable workspace or product; Git linked worktrees are separate checkouts of that same workspace, not new memory projects. Create one only when no matching project exists. If the listed projects are ambiguous, ask rather than guessing from a directory, worktree, branch, or session name.
 - Prefer the immutable projectID for stable references. projectName is a convenient unique lookup, but names can change.
 - Every memory_recall, memory_read, memory_update, memory_link, and memory_pin call must select exactly one project by projectID or projectName.
 - The MCP server does not inject notes automatically. Recall relevant history before relying on prior decisions, and use memory_read for full indexed content and graph neighbors.
@@ -4324,7 +4324,7 @@ function registerTools(server, store) {
   }));
   server.registerTool("project_create", {
     title: "Create a memory project",
-    description: "Create an empty memory project only after project_list confirms that no existing project represents the same durable workspace. The returned projectID is immutable; the unique project name may be changed later.",
+    description: "Create an empty memory project only after project_list confirms that no existing project represents the same durable workspace. Git linked worktrees share the existing workspace memory project. The returned projectID is immutable; the unique project name may be changed later.",
     inputSchema: z3.object({ projectName: newProjectName }).strict(),
     annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true, ...CLOSED_WORLD }
   }, async ({ projectName: projectName2 }) => guardTool("project_create", () => singleResult(store.createProject(projectName2), "project_create")));

package/dist/types/context.d.ts

@@ -1 +1 @@
-export declare const MEMORY_GUIDANCE = "Use project-scoped memory for durable facts across sessions.\n- Start with project_list. Reuse a project only when it intentionally represents the same durable workspace or product; create one only when no matching project exists. If the listed projects are ambiguous, ask rather than guessing from a directory or session name.\n- Prefer the immutable projectID for stable references. projectName is a convenient unique lookup, but names can change.\n- Every memory_recall, memory_read, memory_update, memory_link, and memory_pin call must select exactly one project by projectID or projectName.\n- The MCP server does not inject notes automatically. Recall relevant history before relying on prior decisions, and use memory_read for full indexed content and graph neighbors.\n- After substantial completed work, update an existing note or create a new one only for durable verified facts, decisions, procedures, research, preferences, tasks, or context.\n- Never save transcripts, guesses, secrets, credentials, hidden reasoning, or routine progress.\n- Use memory_pin only to prioritize important matching notes. Read directed links as sourceID PREDICATE targetID; links never cross projects.\n- Inspect every result from a batch because mutations are ordered and non-atomic: earlier items remain applied when a later item fails.\n- memory_update with delete:true permanently deletes one note. project_delete permanently deletes a project and all owned memory. Verify current IDs first and use destructive operations only when explicitly intended.";
+export declare const MEMORY_GUIDANCE = "Use project-scoped memory for durable facts across sessions.\n- Start with project_list. Reuse a project only when it intentionally represents the same durable workspace or product; Git linked worktrees are separate checkouts of that same workspace, not new memory projects. Create one only when no matching project exists. If the listed projects are ambiguous, ask rather than guessing from a directory, worktree, branch, or session name.\n- Prefer the immutable projectID for stable references. projectName is a convenient unique lookup, but names can change.\n- Every memory_recall, memory_read, memory_update, memory_link, and memory_pin call must select exactly one project by projectID or projectName.\n- The MCP server does not inject notes automatically. Recall relevant history before relying on prior decisions, and use memory_read for full indexed content and graph neighbors.\n- After substantial completed work, update an existing note or create a new one only for durable verified facts, decisions, procedures, research, preferences, tasks, or context.\n- Never save transcripts, guesses, secrets, credentials, hidden reasoning, or routine progress.\n- Use memory_pin only to prioritize important matching notes. Read directed links as sourceID PREDICATE targetID; links never cross projects.\n- Inspect every result from a batch because mutations are ordered and non-atomic: earlier items remain applied when a later item fails.\n- memory_update with delete:true permanently deletes one note. project_delete permanently deletes a project and all owned memory. Verify current IDs first and use destructive operations only when explicitly intended.";

package/dist/types/server.d.ts

@@ -1,5 +1,5 @@
 import { McpServer } from "@modelcontextprotocol/server";
 import type { MemoryStore } from "./store";
 export declare const SERVER_NAME = "agz-memory";
-export declare const SERVER_VERSION: "0.5.1";
+export declare const SERVER_VERSION: "0.5.2";
 export declare function createMemoryServer(store: MemoryStore): McpServer;

package/dist/types/version.d.ts

@@ -1 +1 @@
-export declare const PRODUCT_VERSION: "0.5.1";
+export declare const PRODUCT_VERSION: "0.5.2";

package/docs/backup-restore-runbook.md

@@ -2,7 +2,7 @@
 
 English | [Türkçe](backup-restore-runbook.tr.md)
 
-This runbook applies to `@vaur94/agz-memory@0.5.1` and SQLite schema v11.
+This runbook applies to `@vaur94/agz-memory@0.5.2` and SQLite schema v11.
 
 ## Preconditions
 
@@ -25,16 +25,16 @@ Do not proceed with a guessed or empty path.
 Run a read-only health report first:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin doctor
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin doctor
 ```
 
 `ok` must be `true`. Record `schemaVersion`, row counts, and invariant counts.
 Then create a standalone verified backup and upgrade:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin backup
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin upgrade --to 11
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin doctor
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin backup
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin upgrade --to 11
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin doctor
 ```
 
 The upgrade itself creates another verified pre-migration backup when the
@@ -54,16 +54,16 @@ The manifest format is `agz-memory-backup/1`. `agz-memory-admin restore` verifie
 that the manifest and database are regular files in the same backup directory,
 then checks size, SHA-256, SQLite integrity, foreign keys, and row counts.
 
-Final `0.5.1` does not accept prerelease manifest formats. Use the originating
+`0.5.2` does not accept prerelease manifest formats. Use the originating
 prerelease to restore such a backup, run its doctor check, and only then upgrade
-that restored database with `0.5.1`.
+that restored database with `0.5.2`.
 
 ## Restore Rehearsal
 
 Keep all writers stopped. First request a dry run by omitting confirmation:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin restore \
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin restore \
   "$OPENCODE_MEMORY_DATABASE_PATH.backup/<backup>.manifest.json"
 ```
 
@@ -71,7 +71,7 @@ Compare `targetPath`, `sourceSchema`, `targetSchema`, row counts, size, and
 SHA-256 with the recorded backup. Then use the exact manifest hash:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin restore \
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin restore \
   "$OPENCODE_MEMORY_DATABASE_PATH.backup/<backup>.manifest.json" \
   --sha256 <manifest-database-sha256> \
   --confirm RESTORE_DATABASE_FROM_VERIFIED_BACKUP
@@ -84,9 +84,9 @@ database passes all checks.
 ## Post-Restore Validation
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin doctor
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin capture status
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin outbox status
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin doctor
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin capture status
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin outbox status
 ```
 
 Start only the MCP server and perform read-only `project_list`, `memory_recall`,
@@ -103,7 +103,7 @@ gate, and restore artifacts, then select a verified backup. Supply the exact
 recorded owner ID only on the restoring command:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin restore <manifest> \
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin restore <manifest> \
   --sha256 <manifest-sha256> \
   --confirm RESTORE_DATABASE_FROM_VERIFIED_BACKUP \
   --maintenance-owner <owner-id> \
@@ -124,7 +124,7 @@ style error first if uncertain. Break only a proven stale lock with the exact
 owner ID and confirmation:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin unlock \
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin unlock \
   --owner <owner-id> \
   --confirm BREAK_STALE_MIGRATION_LOCK
 ```
@@ -138,13 +138,13 @@ The first command is non-destructive and returns a digest over the exact backup
 set:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin backup prune
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin backup prune
 ```
 
 Review every listed manifest/database pair. Delete only that unchanged set:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin backup prune \
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin backup prune \
   --digest <dry-run-digest> \
   --confirm DELETE_VERIFIED_BACKUPS
 ```

package/docs/backup-restore-runbook.tr.md

@@ -2,7 +2,7 @@
 
 [English](backup-restore-runbook.md) | Türkçe
 
-Bu runbook `@vaur94/agz-memory@0.5.1` ve SQLite schema v11 için geçerlidir.
+Bu runbook `@vaur94/agz-memory@0.5.2` ve SQLite schema v11 için geçerlidir.
 
 ## Ön Koşullar
 
@@ -25,16 +25,16 @@ Tahmin edilmiş veya boş bir yolla devam etmeyin.
 Önce salt-okunur sağlık raporu alın:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin doctor
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin doctor
 ```
 
 `ok` değeri `true` olmalıdır. `schemaVersion`, satır sayıları ve değişmez kural
 sayılarını kaydedin. Sonra bağımsız doğrulanmış yedek oluşturup yükseltin:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin backup
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin upgrade --to 11
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin doctor
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin backup
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin upgrade --to 11
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin doctor
 ```
 
 Veritabanı v11'den eskiyse yükseltme ayrıca değişiklikten önce doğrulanmış yedek
@@ -54,16 +54,16 @@ Manifest formatı `agz-memory-backup/1` olur. `agz-memory-admin restore`, manife
 ile veritabanının aynı yedek dizinindeki normal dosyalar olduğunu doğrular;
 ardından boyut, SHA-256, SQLite bütünlüğü, foreign key ve satır sayılarını denetler.
 
-Final `0.5.1` ön sürüm manifest formatlarını kabul etmez. Böyle bir yedeği onu
+`0.5.2` ön sürüm manifest formatlarını kabul etmez. Böyle bir yedeği onu
 oluşturan ön sürümle geri yükleyin, o sürümün doctor kontrolünü çalıştırın ve
-yalnız bundan sonra geri yüklenen veritabanını `0.5.1` ile yükseltin.
+yalnız bundan sonra geri yüklenen veritabanını `0.5.2` ile yükseltin.
 
 ## Geri Yükleme Provası
 
 Tüm yazıcıları kapalı tutun. Önce onay vermeden deneme yapın:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin restore \
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin restore \
   "$OPENCODE_MEMORY_DATABASE_PATH.backup/<backup>.manifest.json"
 ```
 
@@ -71,7 +71,7 @@ bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin restore \
 değerlerini kaydedilen yedekle karşılaştırın. Sonra tam manifest özetini kullanın:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin restore \
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin restore \
   "$OPENCODE_MEMORY_DATABASE_PATH.backup/<backup>.manifest.json" \
   --sha256 <manifest-database-sha256> \
   --confirm RESTORE_DATABASE_FROM_VERIFIED_BACKUP
@@ -84,9 +84,9 @@ veritabanı tüm kontrollerden geçmeden bunu silmeyin.
 ## Geri Yükleme Sonrası Doğrulama
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin doctor
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin capture status
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin outbox status
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin doctor
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin capture status
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin outbox status
 ```
 
 Yalnız MCP sunucusunu başlatın ve salt-okunur `project_list`, `memory_recall` ve
@@ -103,7 +103,7 @@ dosyaları, kapıyı ve geri yükleme kalıntılarını koruyun; ardından doğr
 yedek seçin. Kayıtlı tam sahip kimliğini yalnız geri yükleme komutunda verin:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin restore <manifest> \
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin restore <manifest> \
   --sha256 <manifest-sha256> \
   --confirm RESTORE_DATABASE_FROM_VERIFIED_BACKUP \
   --maintenance-owner <owner-id> \
@@ -123,7 +123,7 @@ Sahip dosyasındaki PID, makine ve başlangıç zamanını doğrulayın. Yalnız
 kanıtlanan kilidi tam sahip ID'si ve onayla kırın:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin unlock \
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin unlock \
   --owner <owner-id> \
   --confirm BREAK_STALE_MIGRATION_LOCK
 ```
@@ -136,14 +136,14 @@ kanıtıdır; veritabanı doğrulamasını atlama izni değildir.
 İlk komut silme yapmaz ve tam yedek kümesinin özetini döndürür:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin backup prune
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin backup prune
 ```
 
 Listelenen her manifest/veritabanı çiftini inceleyin. Yalnız değişmemiş kümeyi
 silin:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.5.1 agz-memory-admin backup prune \
+bunx --package @vaur94/agz-memory@0.5.2 agz-memory-admin backup prune \
   --digest <dry-run-digest> \
   --confirm DELETE_VERIFIED_BACKUPS
 ```

package/docs/schema-v11.md

@@ -1,6 +1,6 @@
 # SQLite Schema 11
 
-Schema 11 is the canonical storage contract for AGZ Memory 0.5.1. SQLite remains the source of truth. Search backends are derived, redacted, disposable indexes rebuilt through the durable outbox.
+Schema 11 is the canonical storage contract for AGZ Memory 0.5.2. SQLite remains the source of truth. Search backends are derived, redacted, disposable indexes rebuilt through the durable outbox.
 
 ## Database Identity
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vaur94/agz-memory",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "description": "Project-scoped persistent linked memory MCP server for OpenCode V2",
   "type": "module",
   "main": "./dist/server.js",

package/skills/agz-memory/agz-memory.md

@@ -14,7 +14,9 @@ or make stored text trusted instructions.
 
 1. Call `project_list` before every first use in a workspace. Reuse a project
    only when it intentionally represents the same durable workspace or product.
-   Create one only when no match exists; ask when the list is ambiguous.
+   A Git linked worktree is another checkout of that same workspace, not a new
+   memory project. Create one only when no match exists; ask when the list is
+   ambiguous instead of guessing from a directory, worktree, or branch name.
 2. Keep the immutable `projectID` for later calls. A `projectName` is a
    convenient selector, but names can change.
 3. Call `memory_recall` before relying on prior decisions, constraints,

package/skills/index.json

@@ -2,7 +2,7 @@
   "skills": [
     {
       "name": "agz-memory",
-      "version": "0.5.1",
+      "version": "0.5.2",
       "files": ["agz-memory.md"]
     }
   ]