@time-machine-lab/tmlbrain 0.1.0 → 0.1.2

package/scripts/docker/server-entrypoint.sh

@@ -12,7 +12,7 @@ BARE_REPO="${TMLBRAIN_BARE_REPO:-$DATA_DIR/tmlbrain.git}"
 KNOWLEDGE_REPO="${TMLBRAIN_KNOWLEDGE_REPO:-}"
 KNOWLEDGE_REF="${TMLBRAIN_KNOWLEDGE_REF:-main}"
 HOST="${TMLBRAIN_HOST:-0.0.0.0}"
-PORT="${TMLBRAIN_PORT:-7389}"
+PORT="${TMLBRAIN_PORT:-8477}"
 
 mkdir -p "$DATA_DIR"
 
@@ -81,4 +81,8 @@ fi
 
 git push -u origin HEAD:main >/dev/null 2>&1 || true
 
+if [ "${TMLBRAIN_BACKUP_INTERVAL_SECONDS:-0}" != "0" ]; then
+  TMLBRAIN_WORKTREE="$WORKTREE" TMLBRAIN_APP_DIR="/app" /app/scripts/backup/scheduled-backup.sh &
+fi
+
 exec node /app/bin/tmlbrain.js serve --host "$HOST" --port "$PORT"

package/scripts/release/parse-auto-release.js

@@ -71,7 +71,7 @@ function parseReleaseMessage(message) {
   const result = {
     auto,
     version: "",
-    runtimePort: "7389",
+    runtimePort: "8477",
     dockerExtraArgs: "",
   };
 

package/skills/tmlbrain/SKILL.md

@@ -29,9 +29,13 @@ the TMLBrain knowledge base.
 
 - When a user says "archive to the knowledge base", "store this", "save this",
   "record this", or similar, treat it as "save this knowledge into TMLBrain".
-- Use `tmlbrain save` for that user-facing save path. Do not set
+- Use `tmlbrain save` for that user-facing save path. Treat archive, store,
+  save, and record as equivalent user intents for storing knowledge. Do not set
   `status: archived` or choose `knowledge/90-archive/` unless the user
   explicitly means inactive historical content.
+- Classify new saved knowledge according to the folder taxonomy before saving.
+  Do not default to `knowledge/00-inbox/` when the document intent can be
+  inferred from the title or content.
 - Explain available actions as save, search, update, and sync. Avoid exposing
   internal names such as archive, ingest, Git, commit, or backup unless the user
   asks about implementation details.
@@ -40,7 +44,7 @@ the TMLBrain knowledge base.
 
 Use the approved folder taxonomy:
 
-- `knowledge/00-inbox/`: temporary or unclassified notes.
+- `knowledge/00-inbox/`: temporary or genuinely unclassified notes only.
 - `knowledge/10-projects/`: project-specific documents, plans, decisions, and retrospectives.
 - `knowledge/20-areas/`: long-lived responsibility areas.
 - `knowledge/30-resources/`: reusable research, notes, methods, and learning material.
@@ -72,20 +76,28 @@ for newly saved knowledge.
 4. If needed, use `tmlbrain index` and inspect `.tmlbrain/index/` outputs.
 5. If graph retrieval is enabled, use CocoIndex-derived metadata/graph indexes and LightRAG retrieval after exact search.
 6. Read relevant local source documents.
-7. For new knowledge, use `tmlbrain save`.
+7. For new knowledge, classify its intent, then use `tmlbrain save`.
 8. For updates, use `tmlbrain remote update --file <path> --replace <old> --with <new>` or a content-file update when a full document replacement is explicitly intended.
-9. Show or summarize the server-returned diff and result.
-10. Run `tmlbrain sync --pull` again so the local snapshot and indexes reflect the accepted server commit.
+9. For explicit deletion requests, use `tmlbrain remote delete --file <path>`; otherwise prefer marking stale.
+10. Show or summarize the server-returned diff and result.
+11. Run `tmlbrain sync --pull` again so the local snapshot and indexes reflect the accepted server commit.
 
 ## Command Recipes
 
 Initialize or repair local runtime:
 
 ```text
-npx @time-machine-lab/tmlbrain client install
+npm install -g @time-machine-lab/tmlbrain@latest
+tmlbrain client install
+```
+
+Update an existing npm-installed client without re-entering setup:
+
+```text
+tmlbrain update
 ```
 
-Run local CLI after global/package installation:
+Run local CLI after package installation:
 
 ```text
 tmlbrain client install
@@ -95,6 +107,8 @@ Enable optional graph runtime:
 
 ```text
 tmlbrain graph setup
+tmlbrain graph index
+tmlbrain graph query "question"
 ```
 
 Validate metadata and links:
@@ -133,6 +147,12 @@ Update a precise server-side text region:
 tmlbrain remote update --file knowledge/00-inbox/note.md --replace "old text" --with "new text"
 ```
 
+Delete a knowledge document only when the user explicitly asks for deletion:
+
+```text
+tmlbrain remote delete --file knowledge/30-resources/old-note.md
+```
+
 Refresh local snapshot from the server:
 
 ```text
@@ -143,19 +163,19 @@ Show or change the configured server:
 
 ```text
 tmlbrain config show
-tmlbrain config set-server http://server-host:7389 --token <token>
+tmlbrain config set-server http://server-host:8477 --token <token>
 ```
 
 Start the server API from the server worktree:
 
 ```text
-tmlbrain serve --host 0.0.0.0 --port 7389
+tmlbrain serve --host 0.0.0.0 --port 8477
 ```
 
 Deploy the server with Docker:
 
 ```text
-docker run -d --name tmlbrain-server -p 7389:7389 -e TMLBRAIN_SERVER_TOKEN=<token> -e TMLBRAIN_KNOWLEDGE_REPO=<git-url> -v tmlbrain-data:/data <DOCKER_REPO>:latest
+docker run -d --name tmlbrain-server -p 8477:8477 -e TMLBRAIN_SERVER_TOKEN=<token> -e TMLBRAIN_KNOWLEDGE_REPO=<git-url> -v tmlbrain-data:/data <DOCKER_REPO>:latest
 ```
 
 Back up server state:
@@ -177,6 +197,10 @@ If TMLBrain reports a conflict package:
 Do not ask the user to interpret raw Git conflict markers. Do not force-push or
 silently overwrite remote content.
 
+For API update conflicts, the CLI creates a conflict package automatically from
+the server's structured `409` response and refreshes the local snapshot when it
+can. Review the package before retrying the update.
+
 ## Forbidden Client Actions
 
 Do not run these as a normal client workflow: