pi-beyin 0.1.1 → 0.1.3

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/` | `deney-kaydi`, `gunluk`, `literatur`, `bakim` — project-memory procedures driven by `<project>/.pi/beyin-project.json` (see [`skills/_ortak/proje-profili.md`](skills/_ortak/proje-profili.md)). |
+| `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)). |
 | `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
@@ -82,7 +82,7 @@ A vault whose `beyin.py` does not accept `--harness pi` needs `tools/pi-harness-
 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 ≠
 derived report, never delete, secrets are never read or copied) are in
-[`skills/_ortak/proje-profili.md`](skills/_ortak/proje-profili.md).
+[`skills/_shared/project-profile.md`](skills/_shared/project-profile.md).
 
 ## Development
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-beyin",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "pi-native bridge for the beyin second brain: context injection, distillation reminders, and Jev advisor tools.",
   "keywords": [
     "pi-package",
@@ -24,6 +24,9 @@
       "./extensions/context.ts",
       "./extensions/damitma.ts",
       "./extensions/jev.ts"
+    ],
+    "skills": [
+      "./skills"
     ]
   },
   "files": [

package/skills/{_ortak/proje-profili.md → _shared/project-profile.md}

@@ -1,6 +1,6 @@
 # Project Profile Schema (`<project>/.pi/beyin-project.json`)
 
-The portable skills (`deney-kaydi`, `gunluk`, `literatur`, `bakim`) read their paths from this file, so the
+The portable skills (`experiment-record`, `journal`, `literature`, `maintenance`) read their paths from this file, so the
 same skill writes into each project's own directories.
 
 ## Schema
@@ -45,5 +45,5 @@ same skill writes into each project's own directories.
 - Nothing under `secret_dirs` is read or copied; it never enters a report.
 - `close_steps` commands run from the project root and must be **idempotent** and **derived-only**
   (they do not touch source data or human effort, and contain no delete/move). Being defined in the profile is
-  pre-approval; the `bakim` skill runs them at close and reports their output. Destructive/deleting work is
+  pre-approval; the `maintenance` skill runs them at close and reports their output. Destructive/deleting work is
   **never** written here.

package/skills/{deney-kaydi → experiment-record}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: deney-kaydi
+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).
 ---
 
@@ -26,7 +26,7 @@ First read `<project root>/.pi/beyin-project.json`. Fields:
 ```
 
 No profile → default: records in `logs/`, index `logs/index.md`. If unsure, ask the user.
-Full schema and field table: `../_ortak/proje-profili.md`.
+Full schema and field table: `../_shared/project-profile.md`.
 Nothing under `secret_dirs` is read, copied or versioned.
 
 ## Why

package/skills/{gunluk → journal}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: gunluk
+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.
 ---
 
@@ -8,7 +8,7 @@ description: Daily journal (raw narrative) recording procedure. Use for requests
 ## Paths (from the project profile)
 `<project root>/.pi/beyin-project.json` → `journal` (default `journal/`), `logs`, `state`, `progress`,
 `scopes`, `report_dir`. No profile → journal in `journal/`, template `journal/_template.md`.
-File: `<journal>/YYYY-MM-DD.md` (one file per day). Schema: `../_ortak/proje-profili.md`.
+File: `<journal>/YYYY-MM-DD.md` (one file per day). Schema: `../_shared/project-profile.md`.
 
 ## Purpose
 Keep what was done that day as **prose**. The flowing narrative that makes tomorrow-you say "right, that".
@@ -39,7 +39,7 @@ log number next to it.
 
 ## Auto-triggering
 - End-of-day/session signal ("that's it for today", "continue tomorrow") → update the journal.
-- If the profile defines `close_steps` after the journal is written → trigger the `bakim` skill's close steps
+- If the profile defines `close_steps` after the journal is written → trigger the `maintenance` skill's close steps
   (idempotent/derived commands run, e.g. refreshing a dated index).
 - If a new log was produced that day and no journal entry exists → offer to create it.
 - If unsure, ask: "Shall I add today to the journal?"

package/skills/{literatur → literature}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: literatur
+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.
 ---
 
@@ -8,7 +8,7 @@ description: Literature/paper reading-task assignment and note-taking procedure.
 ## Paths (from the project profile)
 `<project root>/.pi/beyin-project.json` → `literature` (default `literature/`).
 Plan: `<literature>/plan.md` · Notes: `<literature>/NN-topic.md` · Template: `<literature>/_note-template.md`.
-Schema: `../_ortak/proje-profili.md`.
+Schema: `../_shared/project-profile.md`.
 
 ## Purpose
 **Concept before tool.** Before producing code/output, establish *why* the models in use work.

package/skills/{bakim → maintenance}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bakim
+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.
 ---
 
@@ -7,7 +7,7 @@ description: System maintenance / garbage-collection PROPOSAL procedure. Use for
 
 ## Paths
 `<project root>/.pi/beyin-project.json` → `logs`, `log_index`, `state`, `progress`, `journal`, `scopes`,
-`close_steps` (idempotent/derived commands run at close — see `../_ortak/proje-profili.md`).
+`close_steps` (idempotent/derived commands run at close — see `../_shared/project-profile.md`).
 No profile → default `logs/`, `journal/`.
 
 ## Core rule: PROPOSE, don't run