pi-beyin 0.1.4 → 0.1.6

package/README.md

@@ -10,7 +10,7 @@ Codex/Claude/OpenCode hooks, plus a CommandCode classifier bridge and the projec
 | `extensions/context.ts` | Injects relevant vault notes into every request and reminds the agent to write a receipt when a turn edited files without recording. Registers the `beyin_jev_memory` / `beyin_jev_review` / `beyin_jev_answer` advisor tools. |
 | `extensions/damitma.ts` | At the end of a turn, if the vault was written but nothing was distilled into `knowledge/`, offers **distillation candidates** (never writes on its own). `/damitma`. |
 | `extensions/jev.ts` | Registers CommandCode's `typesafe/jev` decision model as a pi classifier. `/jev-test`. |
-| `skills/` | `experiment-record`, `journal`, `literature`, `maintenance` — project-memory procedures driven by `<project>/.pi/beyin-project.json` (see [`skills/_shared/project-profile.md`](skills/_shared/project-profile.md)). |
+| `skills/` | `brain` (vault memory work), `brain-doctor` (health), `brain-update` (upgrades), `source-distillation` (external sources → concept notes), and the project-memory procedures `experiment-record`, `journal`, `literature`, `maintenance` driven by `<project>/.pi/beyin-project.json` (see [`skills/_shared/project-profile.md`](skills/_shared/project-profile.md)). |
 | `tools/pi-harness-patch.py` | Makes a beyin vault treat `pi` as a first-class harness (`receipt --harness pi`). Idempotent; the extension re-applies it after beyin updates. |
 
 Everything is **fail-open**: an error never breaks the turn, that turn's contribution is just
@@ -79,8 +79,14 @@ A vault whose `beyin.py` does not accept `--harness pi` needs `tools/pi-harness-
 
 ## Project memory skills
 
-The four skills read `<project>/.pi/beyin-project.json` for paths and scopes; without a profile they
-fall back to `logs/`, `journal/`, `literature/`. The profile schema and the safety rules (source ≠
+Skill descriptions carry bilingual trigger phrases (English + Turkish) on purpose: a description is a
+**routing surface**, not output — it is the text the model uses to pick the skill, so it quotes how the
+user actually speaks. Keep the lists short: every description is in the system prompt on every turn.
+
+The skills are written in English; what they produce is not. Every skill writes in the user's language
+and reuses the target file's headings — existing headings are never translated. The project-memory skills
+read `<project>/.pi/beyin-project.json` for paths and scopes; without a profile they fall back to `logs/`,
+`journal/`, `literature/`. The profile schema and the safety rules (source ≠
 derived report, never delete, secrets are never read or copied) are in
 [`skills/_shared/project-profile.md`](skills/_shared/project-profile.md).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-beyin",
-  "version": "0.1.4",
+  "version": "0.1.6",
   "description": "pi-native bridge for the beyin second brain: context injection, distillation reminders, and Jev advisor tools.",
   "keywords": [
     "pi-package",

package/skills/_shared/project-profile.md

@@ -1,6 +1,6 @@
 # Project Profile Schema (`<project>/.pi/beyin-project.json`)
 
-The portable skills (`experiment-record`, `journal`, `literature`, `maintenance`) read their paths from this file, so the
+The portable skills (`experiment-record`, `journal`, `literature`, `maintenance`, and the beyin workflow skills) read their paths from this file, so the
 same skill writes into each project's own directories.
 
 ## Schema

package/skills/{beyin → brain}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: beyin
-description: Vault memory procedure — find knowledge, write notes and tasks, record finished work with its sources, and keep companion notes current. Use for requests like "hatırla", "bunu kaydet", "not al", "hafızama bak", "görevi güncelle", "ne yapmıştık", "oturumu kapat", "beyne yaz", "remember this", "save this to memory", "note this down", "update the task", "what did we do", "close the session". Runs against the vault root that holds beyin.py. Also covers the optional Jev advisor and the consumption/auto-check preferences.
+name: brain
+description: Vault memory procedure — find knowledge, write notes and tasks, record finished work with its sources, and keep companion notes current. Use for requests like "hatırla", "bunu kaydet", "ne yapmıştık", "remember this", "save this to memory", "what did we do". Runs against the vault root that holds beyin.py. Also covers the Jev advisor and the consumption/auto-check preferences.
 ---
 
 # Beyin
@@ -245,7 +245,7 @@ model runner or a new dependency without being asked.
 
 V3.1: the `updates` section inside `doctor` shows the latest version check; a network error does not prove being
 up to date. Use `beyin.py update --check --metadata-only` only for a version question. Route an update request to
-the `beyin-update` skill.
+the `brain-update` skill.
 
 ## Optional Jev and source-backed decision review
 

package/skills/{beyin-doctor → brain-doctor}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: beyin-doctor
-description: Health check for the beyin installation — does memory actually work, are sources indexed, are hook/worker, skills and updates healthy. Use for requests like "beyin doktor", "hafıza çalışıyor mu", "sağlık kontrolü", "doctor çalıştır", "neden hatırlamıyor", "hook çalışmıyor", "skill çakışması", "run a health check", "is the memory working", "why doesn't it remember", "check the hook". Never turns an indicator green by deleting data.
+name: brain-doctor
+description: Health check for the beyin installation — is memory indexed, are sources synced, are skills and updates healthy. Use for requests like "beyin doktor", "hafıza çalışıyor mu", "neden hatırlamıyor", "run a health check", "why doesn't it remember". Never turns an indicator green by deleting data.
 ---
 
 # Beyin doctor
@@ -16,7 +16,7 @@ logs or private notes into the chat, explain the fault and the smallest fix.
 
 If a source change isn't indexed, `python3 beyin.py sync`; if skill files differ, reconcile deliberately with
 `python3 beyin.py skill-sync`. If both sides changed, keep the files and say which version has to be chosen. If an
-update was left half-done, use the `beyin-update` path; never turn a health indicator green by deleting the runtime
+update was left half-done, use the `brain-update` path; never turn a health indicator green by deleting the runtime
 database or the user's files.
 
 When the client connection has to be verified, use a probe note that contains no private data. In a new real
@@ -66,7 +66,7 @@ ask again for nothing.
 
 V3.1: the `updates` section inside `doctor` shows the latest version check; a network error does not prove being up
 to date. Use `beyin.py update --check --metadata-only` only for a version question. Route an update request to the
-`beyin-update` skill.
+`brain-update` skill.
 
 **Structural auditing is not `doctor`'s job.** Note/task/link graph, single-ownership violations, broken links,
 traces of dead claims → delegate to a read-only vault-audit sub-agent: it returns evidenced findings plus a

package/skills/{beyin-update → brain-update}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: beyin-update
-description: Update an existing beyin installation to the new official version, check the version, or roll back a failed upgrade. Use for requests like "beynimi güncelle", "yeni sürüm var mı", "sürümü kontrol et", "güncelleme kaldı", "geri dön", "rollback", "update beyin", "is there a new version", "check the version", "undo the update". One tool only — beyin.py update.
+name: brain-update
+description: Update an existing beyin installation to the new official version, check the version, or roll back a failed upgrade. Use for requests like "beynimi güncelle", "yeni sürüm var mı", "geri dön", "update beyin", "rollback". One tool only — beyin.py update.
 ---
 
 # Update beyin

package/skills/experiment-record/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: experiment-record
-description: Experiment and decision record standard (project memory). Use for requests like "memory", "deney kaydet", "log tut", "bu denemeyi yaz", "record this run", "sonuçları kaydet", "config/seed not al", "note the config/seed", "deney geçmişine bak", "ne denemiştim", "logs'a bak", "check the logs". Records model training, fine-tuning, ablations, dataset experiments and debugging sessions, plus decisions that must persist, in a reproducible form. Paths and scope come from the project profile (.pi/beyin-project.json).
+description: Experiment and decision record standard (project memory). Use for requests like "deney kaydet", "bu denemeyi yaz", "logs'a bak", "record this run", "check the logs". Records training, fine-tuning, ablations, dataset experiments, debugging sessions and decisions that must persist, in a reproducible form. Paths and scope come from .pi/beyin-project.json.
 ---
 
 # Experiment Record — Experiment and Decision Log

package/skills/journal/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: journal
-description: Daily journal (raw narrative) recording procedure. Use for requests like "günlük", "bugün ne yaptık", "günlüğe ekle", "bugünü kaydet", "gün sonu", "oturumu yaz", "dün ne yapmıştık", "günlüklerime bak", "journal this", "log today", "what did we do yesterday". Detects the system date, opens `YYYY-MM-DD.md` in the journal directory (creating it if absent) and adds what was done that day — including work done through conversation — as prose. The journal is the raw narrative layer; reports/summaries are derived from it. Path and scope come from the project profile.
+description: Daily journal (raw narrative) procedure. Use for requests like "günlüğe ekle", "gün sonu", "dün ne yapmıştık", "journal this", "what did we do yesterday". Opens YYYY-MM-DD.md in the journal directory (creating it if absent) and adds that day's work — including work done through conversation — as prose. The journal is the raw layer; reports derive from it. Path from the project profile.
 ---
 
 # Journal — Raw Narrative Layer

package/skills/literature/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: literature
-description: Literature/paper reading-task assignment and note-taking procedure. Use for requests like "literatür", "makale oku", "paper oku", "şu makaleyi oku", "okuma görevi ver", "not ekle", "şunu okudum anlatayım", "teori çalış", "read this paper", "give me a reading task", "add a note". Assigns reading tasks with focus questions; when the user explains what they read, writes an ordered note into the literature directory. Applies the "concept before tool" principle. Paths come from the project profile.
+description: Literature/paper reading-task assignment and note-taking procedure. Use for requests like "makale oku", "okuma görevi ver", "şunu okudum anlatayım", "read this paper", "give me a reading task". Assigns reading tasks with focus questions; writes an ordered note when the user explains what they read. Concept before tool. Paths from the project profile.
 ---
 
 # Literature — Task Assignment and Note-Taking

package/skills/maintenance/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: maintenance
-description: System maintenance / garbage-collection PROPOSAL procedure. Use for requests like "temizlik", "bakım", "sistemi toparla", "çöplükleri temizle", "clean up", "tidy the repo", "oturumu kapat", "yeni oturuma geçmeden temizle", "kompakte et", "compact the state". Also PROPOSE maintenance to the user at natural moments such as session close or phase transition. IMPORTANT — never runs on its own or on a schedule; it only proposes, and acts after user approval. Paths come from the project profile.
+description: System maintenance / garbage-collection PROPOSAL procedure. Use for requests like "temizlik", "sistemi toparla", "kompakte et", "clean up", "compact the state". Also propose maintenance at natural moments such as session close. IMPORTANT — never runs on its own or on a schedule; it only proposes, and acts after user approval. Paths from the project profile.
 ---
 
 # Maintenance — Garbage Collection PROPOSAL (runs on approval)

package/skills/source-distillation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: source-distillation
-description: Capture an external source (web doc, arXiv/paper, local PDF archive, bookmark export) and distill it into a high-quality concept note in the vault. Use for requests like "şu siteyi vault'a al", "dokümanları damıt", "makale arşivini işle", "pdf'lerden not çıkar", "bookmarklarımı damıt", "şu URL'leri tara", "distill these docs", "turn this into notes", "process the paper archive". The quality wall and the secret/privacy gate are mandatory. Raw source paths come from the project profile.
+description: Capture an external source (web doc, arXiv/paper, local PDF archive, bookmark export) and distill it into a source-linked concept note in the vault. Use for requests like "dokümanları damıt", "makale arşivini işle", "bookmarklarımı damıt", "distill these docs", "process the paper archive". The quality wall and the secret/privacy gate are mandatory. Raw source paths come from the project profile.
 ---
 
 # Source distillation (external source → vault)
@@ -9,7 +9,7 @@ Language: write in the user's language and reuse the target file's headings —
 
 Distill transferable knowledge from an **external source** the user gives (web, paper, local PDF, bookmark) into
 the vault. Not copying raw text: **source ≠ derived**. The raw source stays outside the vault; the vault holds only
-the distilled, source-linked note. Related: `../beyin/SKILL.md`.
+the distilled, source-linked note. Related: `../brain/SKILL.md`.
 
 ## Paths (from the project profile)
 `<project root>/.pi/beyin-project.json` → `sources` (optional; fallback `sources/` under the project root),