@vaur94/agz-memory 0.4.1 → 0.5.0

package/ARCHITECTURE.md

@@ -1,6 +1,6 @@
 # AGZ Memory Architecture
 
-This document describes the `0.4.1` runtime and SQLite schema v10.
+This document describes the `0.5.0` runtime and SQLite schema v11.
 
 ## System Boundaries
 
@@ -9,7 +9,7 @@ OpenCode MCP client
   -> agz-memory stdio server
      -> nine-tool MCP adapter
         -> memory core
-           -> SQLite schema v10 (canonical)
+            -> SQLite schema v11 (canonical)
 
 OpenCode V2 beta-18743
   -> @vaur94/agz-memory-plugin
@@ -20,7 +20,7 @@ OpenCode V2 beta-18743
 
 SQLite outbox
   -> optional derived retrieval backend
-     -> disabled in 0.4.1; backend = none
+      -> disabled in 0.5.0; backend = none
 ```
 
 The MCP adapter owns tool schemas, annotations, and result envelopes. The core
@@ -42,7 +42,7 @@ current name, and fixed confirmation phrase.
 
 ## Canonical Schema
 
-SQLite schema v10 contains:
+SQLite schema v11 contains:
 
 | Table | Responsibility |
 |---|---|
@@ -50,19 +50,21 @@ SQLite schema v10 contains:
 | `notes` | Current note state, status, subject key, revision, and content hash. |
 | `note_edges` | Typed same-project graph relations. |
 | `notes_fts` | Trigger-maintained FTS5 projection of current note text. |
-| `project_bindings` | Explicit OpenCode-to-memory mapping with canonical path hash. |
-| `capture_checkpoints` | Bounded reconciliation progress without transcript text. |
-| `capture_events` | Redacted, idempotent capture audit under `agz-memory.capture/1`. |
+| `project_bindings` | Explicit OpenCode-to-memory mapping with a v2 tuple-hashed canonical path. |
+| `capture_checkpoints` | Binding-scoped reconciliation progress without transcript text. |
+| `capture_events` | Redacted, idempotent capture audit under `agz-memory.capture/2`. |
 | `note_provenance` | Source identity, extractor/redaction versions, and confidence. |
 | `note_revisions` | Immutable snapshot for each committed note revision. |
-| `index_outbox` | Payload-free queue for replaceable derived indexes. |
+| `index_outbox` | Payload-free, generation- and fence-aware queue for replaceable indexes. |
+| `agz_meta` | Database UUID, product, schema, fingerprint, and hash policy identity. |
 | `schema_state` | The single current schema version. |
 
-The v10 migration changes product-owned persisted identities. Existing v9
-capture rows are copied with the final capture contract; all other data remains
-in place. Migration runs with foreign keys temporarily disabled inside one
-transaction, reenables them, then requires integrity and foreign-key checks to
-pass.
+The v11 migration replaces delimiter-joined hashes with domain-separated,
+length-prefixed v2 tuple hashes. It validates and deterministically maps every
+schema 10 note, binding, capture, checkpoint, and outbox row. Composite foreign
+keys enforce project ownership. Migration publishes schema 11 only after row
+counts, revisions, hashes, FTS, foreign keys, database identity, and the exact
+schema fingerprint pass.
 
 ## Note Lifecycle
 
@@ -72,7 +74,7 @@ Manual MCP writes and automatic writes use the same invariants:
 2. Calculate the canonical content SHA-256.
 3. Commit the note mutation and its provenance/revision in one transaction.
 4. Maintain supersession status and the `SUPERSEDES` edge when applicable.
-5. Enqueue identity-only derived-index operations for configured backends.
+5. Enqueue required identity-only derived-index operations in the same commit.
 6. Let SQLite triggers update FTS5 for insert, update, and delete.
 
 Only active notes are returned by normal recall. Superseded and archived state
@@ -99,9 +101,10 @@ Capture requires all of these gates:
    matches project ID, workspace ID, and canonical directory.
 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 `CaptureEventV1` parser enforces size, source identity, event
+5. The strict `CaptureEventV2` parser enforces UTF-8 size, kind-specific source identity, event
    kind, and redaction metadata.
-6. A deterministic SHA-256 idempotency key prevents replay duplicates.
+6. A v2 tuple-hashed idempotency key prevents replay duplicates and rejects
+   mismatched reuse as an idempotency conflict.
 7. Shadow modes stop at the audit event. `auto-write` continues only for an
    allowed kind, explicit durable evidence, supported intent, and confidence at
    or above policy.
@@ -116,9 +119,11 @@ stopped at the deadline, overdue work is drained on the next MCP or plugin start
 ## Retrieval Pipeline
 
 Retrieval starts with project-filtered lexical FTS5 results. Same-project graph
-neighbors can be added with bounded fan-out. A reciprocal-rank fusion step
-deduplicates candidates and returns at most eight cards within the configured
-deadline.
+neighbors can be added with bounded fan-out. Optional backend responses are
+strictly parsed, validated against current canonical rows in bounded batch SQL,
+and discarded when project, revision, or derived hash differs. A deterministic
+reciprocal-rank fusion step deduplicates candidates and returns at most eight
+cards within one deadline for the complete pipeline.
 
 The plugin formats cards inside an escaped
 `<agz-memory-context trust="untrusted">` envelope capped at 4,800 characters.
@@ -128,7 +133,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.4.1`. The SQLite lexical/graph path remains fully
+No provider is enabled in `0.5.0`. The SQLite lexical/graph path remains fully
 functional without one.
 
 ## Derived Index Outbox
@@ -138,15 +143,26 @@ content hash. It never stores note text. Workers lease rows, derive content
 from the canonical database at execution time, and acknowledge success only
 after the backend call completes.
 
-Leases are reclaimable after expiry. Retries use bounded exponential backoff;
+Leases heartbeat while work runs and every completion is conditional on the
+lease owner, generation, and monotonic fence. Backend calls have a hard timeout
+even when they ignore `AbortSignal`. Retries use bounded exponential backoff;
 terminal failures become `dead` and are visible through the admin CLI. Project
-purge is a first-class operation so a derived backend cannot retain deleted
-project content by omission.
+purge is a first-class operation, and each reindex generation queues a purge
+before a transactional snapshot of active-note upserts.
+
+Outbox adapters must declare `agz-memory-outbox/1` and atomically reject an
+operation context older than the greatest `(sequence, fence)` already applied
+for that backend and project. `sequence` orders distinct queue rows while
+`fence` orders competing leases for one row; `operationKey` makes an accepted
+attempt idempotent. An adapter that cannot enforce this protocol is not eligible
+for outbox registration.
 
 ## Backup, Migration, And Restore
 
-Database upgrades are serialized by a filesystem migration-lock directory with
-an owner record. Before the first schema mutation, AGZ Memory checkpoints WAL,
+Every normal database handle publishes a lifetime lease. Migration, restore,
+backup publication, and prune acquire an exclusive filesystem maintenance gate
+and refuse to proceed while an active or unverifiable lease exists. Before the
+first schema mutation, AGZ Memory checkpoints WAL,
 creates a SQLite-consistent copy with `VACUUM INTO`, verifies integrity and row
 counts, hashes the bytes, and atomically publishes both database and
 `agz-memory-backup/1` manifest.

package/CHANGELOG.md

@@ -3,6 +3,63 @@
 All notable changes to AGZ Memory are recorded here. The project follows
 [Semantic Versioning](https://semver.org/).
 
+## [0.5.0] - 2026-09-02
+
+### Added
+
+- Added SQLite schema 11 database identity, exact schema fingerprinting,
+  domain-separated length-prefixed hash tuples, composite tenant foreign keys,
+  and a deterministic lossless schema-10 migration.
+- Added a cross-process maintenance gate with lifetime database leases,
+  no-symlink path checks, streaming verified restore, rollback verification,
+  and deep doctor invariants.
+- Added generated reindex operations with purge-first snapshots, fenced and
+  heartbeat-protected outbox leases, hard backend timeouts, and explicit retry.
+- Added Linux minimum/current Bun, macOS, Windows, property, stress, restore,
+  benchmark, package-install, CodeQL, and dependency-review CI gates.
+
+### Changed
+
+- Advanced capture to `agz-memory.capture/2` with strict kind-specific source
+  identities, UTF-8 byte limits, fail-closed redaction, and idempotency conflict
+  detection.
+- Made canonical note, revision, provenance, supersession, and required outbox
+  mutations share immediate transactions with optimistic revision checks.
+- Bounded plugin reconciliation and history/context probes, preserved turn
+  opt-out across hook order and restart, kept prompt capture from advancing the
+  reconciliation watermark, validated every event against the full binding,
+  and made shutdown independent of hung OpenCode calls.
+- Hardened retrieval with one end-to-end deadline, strict backend parsing,
+  batched canonical validation, deterministic fusion, directed graph handling,
+  and Unicode-safe context limits.
+
+### Security
+
+- Preserved exactly nine MCP tools, fail-closed project isolation, untrusted
+  context envelopes, inert plugin defaults, and semantic backend `none`.
+- Added the complete [AGZ-001 through AGZ-068 resolution record](docs/review-resolution.md).
+- Rejects unsupported databases before permission or journal mutation and
+  serializes administrative backup/prune with active database handles.
+
+## [0.4.2] - 2026-09-02
+
+### Added
+
+- Added a versioned `agz-memory` OpenCode skill catalog to the core npm package
+  and documented the explicit immutable skill source used for discovery.
+
+### Changed
+
+- Expanded MCP `initialize` guidance so an unfamiliar agent reuses the correct
+  durable project, recalls before relying on history, records only verified
+  outcomes, and handles non-atomic or destructive mutations safely.
+- Added field-level descriptions to the nine tool schemas, including directed
+  link semantics, note content behavior, batch ordering, and selector roles.
+- Corrected MCP tool annotations for closed-world operation, destructive
+  rename/unpin behavior, and safe idempotent retries.
+- Documented that npm installation does not itself activate a skill and that
+  installers must not modify the user's ambient global `AGENTS.md` policy.
+
 ## [0.4.1] - 2026-09-01
 
 ### Fixed
@@ -74,6 +131,8 @@ All notable changes to AGZ Memory are recorded here. The project follows
 - Preserved the nine-tool MCP interface and project-isolation guarantees while
   establishing the AGZ Memory public packages and repository.
 
+[0.5.0]: https://github.com/ugur-murat-alt/agz-memory/releases/tag/v0.5.0
+[0.4.2]: https://github.com/ugur-murat-alt/agz-memory/releases/tag/v0.4.2
 [0.4.1]: https://github.com/ugur-murat-alt/agz-memory/releases/tag/v0.4.1
 [0.4.0]: https://github.com/ugur-murat-alt/agz-memory/releases/tag/v0.4.0
 [0.4.0-beta.1]: https://github.com/ugur-murat-alt/agz-memory/releases/tag/v0.4.0-beta.1

package/README.md

@@ -20,7 +20,7 @@ binding and rollout mode are configured.
   project name.
 - Notes can be pinned, linked, superseded, revised, searched, and inspected
   without mixing projects.
-- SQLite schema v10 is the canonical source of truth; optional semantic indexes
+- SQLite schema v11 is the canonical source of truth; optional semantic indexes
   are replaceable derivatives.
 - Destructive project deletion requires the immutable ID, exact current name,
   and a fixed confirmation phrase.
@@ -32,12 +32,12 @@ binding and rollout mode are configured.
 
 | Component | Supported version |
 |---|---|
-| Core and MCP | `0.4.1` |
-| OpenCode plugin | `0.4.1` |
+| Core and MCP | `0.5.0` |
+| OpenCode plugin | `0.5.0` |
 | OpenCode V2 | `0.0.0-beta-18743` |
 | `@opencode-ai/plugin` | `0.0.0-beta-18743` |
 | Bun | `>=1.3.14` |
-| SQLite schema | `10` |
+| SQLite schema | `11` |
 
 The MCP server is not tied to an OpenCode beta. The optional plugin disables
 itself unless the running OpenCode version exactly matches the supported beta.
@@ -47,18 +47,21 @@ itself unless the running OpenCode version exactly matches the supported beta.
 Run the server directly:
 
 ```sh
-bunx @vaur94/agz-memory@0.4.1
+bunx @vaur94/agz-memory@0.5.0
 ```
 
 Or register it in OpenCode V2 under `mcp.servers`:
 
 ```jsonc
 {
+  "skills": [
+    "https://raw.githubusercontent.com/ugur-murat-alt/agz-memory/v0.5.0/skills/"
+  ],
   "mcp": {
     "servers": {
       "agz-memory": {
         "type": "local",
-        "command": ["bunx", "@vaur94/agz-memory@0.4.1"],
+        "command": ["bunx", "@vaur94/agz-memory@0.5.0"],
         "environment": {
           "OPENCODE_MEMORY_DATABASE_PATH": "{env:OPENCODE_MEMORY_DATABASE_PATH}"
         },
@@ -69,6 +72,20 @@ Or register it in OpenCode V2 under `mcp.servers`:
 }
 ```
 
+The npm package contains the versioned `agz-memory` skill catalog, but npm
+installation alone does not make a skill discoverable. The explicit `skills`
+entry above lets OpenCode download and advertise the same workflow lazily. The
+MCP remains fully usable without it because the server supplies concise
+`initialize` instructions and complete tool schemas on every connection.
+
+Installation must not edit `~/.config/opencode/AGENTS.md`. That file is
+user-owned, ambient policy for every project, not an extension installation
+surface. Teams may maintain their own memory policy there, but AGZ Memory does
+not require one. `codemode: false` is intentional for this small fixed catalog:
+it exposes all nine tools directly. If Code Mode is enabled instead, the server
+instructions, tool descriptions, and optional skill still describe the same
+workflow.
+
 The default database is
 `~/.local/share/opencode-memory/memory.sqlite`. Set
 `OPENCODE_MEMORY_DATABASE_PATH` before OpenCode starts to use another path.
@@ -113,7 +130,7 @@ options:
 {
   "plugins": [
     {
-      "package": "@vaur94/agz-memory-plugin@0.4.1",
+      "package": "@vaur94/agz-memory-plugin@0.5.0",
       "options": {
         "mode": "off",
         "autoCreateProjects": false,
@@ -186,11 +203,11 @@ quality, and latency gates.
 The admin CLI reads the same `OPENCODE_MEMORY_DATABASE_PATH`:
 
 ```sh
-bunx --package @vaur94/agz-memory@0.4.1 agz-memory-admin doctor
-bunx --package @vaur94/agz-memory@0.4.1 agz-memory-admin backup
-bunx --package @vaur94/agz-memory@0.4.1 agz-memory-admin upgrade --to 10
-bunx --package @vaur94/agz-memory@0.4.1 agz-memory-admin capture status
-bunx --package @vaur94/agz-memory@0.4.1 agz-memory-admin outbox status
+bunx --package @vaur94/agz-memory@0.5.0 agz-memory-admin doctor
+bunx --package @vaur94/agz-memory@0.5.0 agz-memory-admin backup
+bunx --package @vaur94/agz-memory@0.5.0 agz-memory-admin upgrade --to 11
+bunx --package @vaur94/agz-memory@0.5.0 agz-memory-admin capture status
+bunx --package @vaur94/agz-memory@0.5.0 agz-memory-admin outbox status
 ```
 
 Upgrades take an exclusive migration lock and create a verified backup before
@@ -199,7 +216,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.4.1` backup manifests use `agz-memory-backup/1`; prerelease
+rehearsal. Final `0.5.0` backup manifests use `agz-memory-backup/1`; prerelease
 manifests must be handled by the prerelease that created them.
 
 ## Security Model
@@ -224,15 +241,19 @@ Report vulnerabilities privately as described in [SECURITY.md](SECURITY.md).
 ```sh
 bun install --frozen-lockfile
 bun run release:verify
-bun test
 bun run check
+bun test
+bun run test:property
+bun run test:stress
+bun run test:restore
+bun run benchmark:gate
 bun run build
-bun run benchmark 10000 100
 npm pack --dry-run --json
 ```
 
 `release:verify` rejects package-version drift, mismatched bilingual sections,
-stale beta pins, and any tracked reintroduction of the retired project name.
+stale release pins, an incomplete AGZ-001 through AGZ-068 resolution table, and
+any tracked reintroduction of the retired project name.
 The test suite covers project isolation, destructive confirmation, migration,
 backup/restore, capture safety, revisions, provenance, FTS, retrieval, outbox,
 and the exact nine-tool MCP surface.
@@ -242,6 +263,8 @@ and the exact nine-tool MCP surface.
 - [Architecture](ARCHITECTURE.md)
 - [Changelog](CHANGELOG.md)
 - [Backup and restore runbook](docs/backup-restore-runbook.md)
+- [Schema 11 contract](docs/schema-v11.md)
+- [Review resolution](docs/review-resolution.md)
 - [Contributing](CONTRIBUTING.md)
 - [Security policy](SECURITY.md)
 - [GitHub repository](https://github.com/ugur-murat-alt/agz-memory)

package/README.tr.md

@@ -20,7 +20,7 @@ bağlam eklemez.
   sınırlandırılır.
 - Notlar projeler karışmadan sabitlenebilir, bağlanabilir, hükümsüz bırakılabilir,
   sürümlenebilir, aranabilir ve incelenebilir.
-- SQLite schema v10 tek yetkili veri kaynağıdır; isteğe bağlı anlamsal indeksler
+- SQLite schema v11 tek yetkili veri kaynağıdır; isteğe bağlı anlamsal indeksler
   yeniden üretilebilir türevlerdir.
 - Yıkıcı proje silme işlemi değişmez ID, güncel ad ve sabit onay ifadesi ister.
 - Yedek manifestleri geri yüklemeden önce satır sayılarını, SQLite bütünlüğünü,
@@ -32,12 +32,12 @@ bağlam eklemez.
 
 | Bileşen | Desteklenen sürüm |
 |---|---|
-| Çekirdek ve MCP | `0.4.1` |
-| OpenCode eklentisi | `0.4.1` |
+| Çekirdek ve MCP | `0.5.0` |
+| OpenCode eklentisi | `0.5.0` |
 | OpenCode V2 | `0.0.0-beta-18743` |
 | `@opencode-ai/plugin` | `0.0.0-beta-18743` |
 | Bun | `>=1.3.14` |
-| SQLite schema | `10` |
+| SQLite schema | `11` |
 
 MCP sunucusu bir OpenCode beta sürümüne bağlı değildir. İsteğe bağlı eklenti,
 çalışan OpenCode sürümü desteklenen beta ile tam eşleşmezse kendini kapatır.
@@ -47,18 +47,21 @@ 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.4.1
+bunx @vaur94/agz-memory@0.5.0
 ```
 
 Ya da OpenCode V2 içinde `mcp.servers` altına kaydedin:
 
 ```jsonc
 {
+  "skills": [
+    "https://raw.githubusercontent.com/ugur-murat-alt/agz-memory/v0.5.0/skills/"
+  ],
   "mcp": {
     "servers": {
       "agz-memory": {
         "type": "local",
-        "command": ["bunx", "@vaur94/agz-memory@0.4.1"],
+        "command": ["bunx", "@vaur94/agz-memory@0.5.0"],
         "environment": {
           "OPENCODE_MEMORY_DATABASE_PATH": "{env:OPENCODE_MEMORY_DATABASE_PATH}"
         },
@@ -69,6 +72,21 @@ Ya da OpenCode V2 içinde `mcp.servers` altına kaydedin:
 }
 ```
 
+npm paketi, sürümlenmiş `agz-memory` skill kataloğunu taşır. Skill, ajanın
+gerektiğinde yüklediği iş akışı talimatıdır; yalnız npm kurulumu onu
+keşfedilebilir yapmaz. Yukarıdaki açık `skills` girdisi OpenCode'un aynı iş
+akışını indirip ajana tanıtmasını sağlar. MCP bu girdi olmadan da tam
+kullanılabilir; sunucu her bağlantıda kısa `initialize` talimatlarını ve eksiksiz
+araç şemalarını sunar.
+
+Kurulum `~/.config/opencode/AGENTS.md` dosyasını değiştirmemelidir. Bu dosya
+eklenti kurulum yüzeyi değil, kullanıcının tüm projeler için sahip olduğu genel
+ajan politikasıdır. Ekipler kendi hafıza politikalarını orada tutabilir, ancak
+AGZ Memory buna ihtiyaç duymaz. `codemode: false`, küçük ve sabit katalog için
+bilinçli seçimdir; dokuz aracın tümünü doğrudan gösterir. Code Mode açılırsa da
+sunucu talimatları, araç açıklamaları ve isteğe bağlı skill aynı iş akışını
+tanımlar.
+
 Varsayılan veritabanı
 `~/.local/share/opencode-memory/memory.sqlite` konumundadır. Başka bir yol için
 OpenCode başlamadan önce `OPENCODE_MEMORY_DATABASE_PATH` ayarlayın. Veritabanı
@@ -114,7 +132,7 @@ ayarlarla ekleyin:
 {
   "plugins": [
     {
-      "package": "@vaur94/agz-memory-plugin@0.4.1",
+      "package": "@vaur94/agz-memory-plugin@0.5.0",
       "options": {
         "mode": "off",
         "autoCreateProjects": false,
@@ -187,11 +205,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.4.1 agz-memory-admin doctor
-bunx --package @vaur94/agz-memory@0.4.1 agz-memory-admin backup
-bunx --package @vaur94/agz-memory@0.4.1 agz-memory-admin upgrade --to 10
-bunx --package @vaur94/agz-memory@0.4.1 agz-memory-admin capture status
-bunx --package @vaur94/agz-memory@0.4.1 agz-memory-admin outbox status
+bunx --package @vaur94/agz-memory@0.5.0 agz-memory-admin doctor
+bunx --package @vaur94/agz-memory@0.5.0 agz-memory-admin backup
+bunx --package @vaur94/agz-memory@0.5.0 agz-memory-admin upgrade --to 11
+bunx --package @vaur94/agz-memory@0.5.0 agz-memory-admin capture status
+bunx --package @vaur94/agz-memory@0.5.0 agz-memory-admin outbox status
 ```
 
 Yükseltmeler özel bir geçiş kilidi alır ve veritabanını değiştirmeden önce
@@ -200,7 +218,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.4.1` yedek manifestleri `agz-memory-backup/1` kullanır;
+kullanın. Final `0.5.0` 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
@@ -225,16 +243,19 @@ Güvenlik açıklarını [SECURITY.md](SECURITY.md) içindeki özel kanaldan bil
 ```sh
 bun install --frozen-lockfile
 bun run release:verify
-bun test
 bun run check
+bun test
+bun run test:property
+bun run test:stress
+bun run test:restore
+bun run benchmark:gate
 bun run build
-bun run benchmark 10000 100
 npm pack --dry-run --json
 ```
 
 `release:verify`; paket sürümü sapmasını, iki dildeki bölüm uyuşmazlığını, eski
-beta pinlerini ve kullanımdan kaldırılan proje adının tracked dosyalara yeniden
-girmesini reddeder. Testler proje izolasyonu, yıkıcı onay, schema geçişi,
+sürüm pinlerini, eksik AGZ-001 ile AGZ-068 çözüm tablosunu ve kullanımdan
+kaldırılan proje adının tracked dosyalara yeniden girmesini reddeder. Testler proje izolasyonu, yıkıcı onay, schema geçişi,
 yedekleme/geri yükleme, yakalama güvenliği, revision, provenance, FTS, geri
 çağırma, outbox ve tam dokuz araçlı MCP yüzeyini kapsar.
 
@@ -243,6 +264,8 @@ yedekleme/geri yükleme, yakalama güvenliği, revision, provenance, FTS, geri
 - [Mimari](ARCHITECTURE.md)
 - [Değişiklik günlüğü](CHANGELOG.md)
 - [Yedekleme ve geri yükleme runbook'u](docs/backup-restore-runbook.tr.md)
+- [Schema 11 sözleşmesi](docs/schema-v11.md)
+- [İnceleme çözümleri](docs/review-resolution.md)
 - [Katkı rehberi](CONTRIBUTING.md)
 - [Güvenlik politikası](SECURITY.md)
 - [GitHub deposu](https://github.com/ugur-murat-alt/agz-memory)