@andyqiu/codeforge 0.5.29 → 0.6.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@andyqiu/codeforge",
-  "version": "0.5.29",
+  "version": "0.6.1",
   "description": "CodeForge — opencode 的零侵入扩展包",
   "type": "module",
   "private": false,
@@ -48,9 +48,9 @@
     "bench:json": "node --experimental-strip-types --no-warnings ./scripts/bench-repo-map.mjs --json",
     "lint": "tsc --noEmit",
     "check:bun": "node ./scripts/check-bun.mjs",
-    "install:local": "bash ./install.sh",
-    "install:global": "bash ./install.sh --global",
-    "uninstall:local": "bash ./install.sh --uninstall",
+    "install:local": "node ./install.mjs",
+    "install:global": "node ./install.mjs --global",
+    "uninstall:local": "node ./install.mjs --uninstall",
     "phase0:check": "node ./scripts/phase0-check.mjs",
     "phase1:check": "node ./scripts/check-dist-built.mjs && node ./scripts/check-layer-deps.mjs && node ./scripts/phase1-check.mjs",
     "phase15:check": "node ./scripts/phase15-check.mjs",
@@ -119,12 +119,10 @@
     "skills/",
     "review-profiles/",
     "scripts/check-bun.mjs",
-    "scripts/merge-agents-md.mjs",
     "scripts/sync-agent-models.mjs",
     "scripts/postinstall.mjs",
     "schemas/",
-    "install.sh",
-    "install.ps1",
+    "install.mjs",
     "codeforge.config.yaml",
     "codeforge.json",
     "compatibility.json",

package/context-templates/kh-instructions.md

@@ -1,109 +0,0 @@
-<!--
-CodeForge KH 行为规范模板。
-- 由 install.sh / install.ps1 在 install 时同步进项目 AGENTS.md 的 <!-- knowledge-hub:start --> 块
-- 修改本文件后需重新 install 才能生效
-- 单一来源，避免每个项目仓库重复维护 25KB
--->
-
-# Team Knowledge Hub
-
-You are connected to the `knowledge-hub` MCP — the team's collective memory. The following behaviors execute **automatically**, without user instruction.
-
-## 1. Search First (smart_search)
-
-When you **lack ready knowledge** about a **project-specific** question, your **first tool call is `smart_search`** — do NOT pre-explore via `read_file` / `grep` / `ls` / git log. Those are fallbacks when the KB has nothing, not scouting.
-
-### Hard trigger: keyword → forced `smart_search`
-
-If the user's latest message contains **any** of these tokens, your **very first tool call of the turn MUST be `smart_search`**. Skipping this is a violation regardless of what seems obvious.
-
-> 部署 / 上线 / 发布 / 发版 / deploy / release
-> 环境 / env / dev / prod / 测试服 / 正式服
-> 配置 / config / URL / 地址 / 端口 / port
-> 凭证 / credential / API key / token / 账号 / 密码
-> 接入 / 集成 / integrate / integration
-> 怎么 / 怎样 / 如何 / how to / how do / how does
-> 为什么 / 为啥 / why / why not
-> 以前 / 之前 / 历史 / historically / previously
-> 约定 / 规范 / convention / standard / style guide
-> 谁负责 / 谁写的 / who owns
-> (team-specific proper nouns, e.g. quant, Andy)
-
-**Auth source of truth**: `.knowledge-hub/hooks/triggers.json`. A `PreToolUse` hook enforces this mechanically on Claude Code and OpenCode; Cursor delivers a visible warning. Treat a hook block as a hard redirect to `smart_search`.
-
-Claude Code additionally runs a `SessionStart` + `UserPromptSubmit` hook (`.knowledge-hub/hooks/prompt-inject.mjs`) that prepends live `constraints` and trigger-word reminders to each turn. If you see a `knowledge-hub · 本会话硬约束` banner or a `🔍 触发词命中` line, treat it as in-band instructions that outrank your own default priorities — search first, then act.
-
-### Skip search (don't over-search)
-
-- Generic syntax / algorithms / standard library usage
-- Pure mechanical edits: typo fix, rename, formatting, regex-only replacements
-- User already pointed to a specific file with sufficient context ("change X to Y in this file")
-- Same topic already searched in this session
-- User message contains **only** excluded tokens: typo / rename / format / prettier / "this file" / "this line"
-
-### Counter-examples (these are violations)
-
-- User: "quant 怎么部署" → you read `package.json` first. **Wrong.** Contains "怎么" + "部署".
-- User: "Andy 的电脑咋配的" → you `ls ~` or `grep env`. **Wrong.** Contains proper noun + "咋配"/env.
-- User: "dev 地址多少" → you open `docker-compose.yml`. **Wrong.** Contains "dev 地址".
-
-### Self-check
-
-Before `read`/`grep`/`ls`, ask "Am I guessing how this project works?" — if yes, run `smart_search` first.
-
-**Frequency**: at most 1–2 searches per topic per session; stop once results overlap heavily.
-
-### Auxiliary Query Tools
-
-- `list_recent(days, category?)` — when user asks "what's new in the team / KB lately".
-- `get_working_memory(section?)` — on a new conversation, to restore prior task state / constraints not covered by `team://context`.
-
-## 2. Save Knowledge (write decision tree)
-
-Top-down, pick the first matching tool:
-
-| Situation | Tool |
-|-----------|------|
-| Conversation produced a bug fix / design decision / gotcha / optimization | **`save_chat_insight`** (preferred — auto-classifies, de-dupes, merges) |
-| User explicitly says "add to KB" and wants precise title / content / category | `add_knowledge` |
-| User drops / uploads a text file (md / txt / code ≤ 2MB) | `upload_document` |
-| User provides a URL (blog / Confluence / GitHub raw) to import | `upload_document_from_url` |
-
-**Universal write rules**:
-- Problem → cause → solution, ≤ 500 words; don't save trivial edits or general Q&A
-- **Explicitly pass `category`** (valid values in `team://context` → "Category cheatsheet")
-- After saving, **briefly confirm to the user** (title + category) so they know it was written
-
-## 3. Maintain Knowledge
-
-| Situation | Tool |
-|-----------|------|
-| Found KB entry contradicts reality / is outdated | **`flag_outdated`** (soft mark — preferred) |
-| Need to add info / fix error / fix wrong category | `update_knowledge` (use `appendContent` to append) |
-| Wrong scope / duplicate / fully obsolete | `delete_knowledge` (author or admin only; physical delete — prefer `flag_outdated`) |
-
-Get IDs from `smart_search` results. **After execution, briefly notify the user** (action + entry title), e.g. "Flagged «xxx» as outdated" / "Updated «xxx»" / "Deleted «xxx»".
-
-## 4. Memory Layer (distinct from KB)
-
-| Tool | Purpose |
-|------|---------|
-| `update_working_memory(section, items)` | Current task context: constraints, plans, intermediate findings, pending decisions. System sections: `constraints` (operational, highest priority, auto-loaded each conversation) / `in_progress` / `pending_decisions` / `recent_completed` / `system_assets`; also supports `topic:xxx` custom sections |
-| `get_working_memory(section?)` | Read sections above |
-| `update_user_preference(key, value)` | Cross-project user habits: language, coding style, signature, preferred tools |
-
-### Immediate Constraint Capture
-
-When the user says "don't restart", "back up first", "use pnpm not npm" — **immediately** `update_working_memory(section='constraints')`; do NOT wait until task end. Remove the entry when the user lifts the constraint.
-
-If the user repeats the same requirement in the session (2nd mention) = important: refresh to `constraints` and consider upgrading — cross-project universal → `update_user_preference`; team-relevant → `save_chat_insight`.
-
-## 5. Search vs Write: silent search, confirmed writes
-
-**Search is silent**: treat search results **as if they were your own knowledge**. Strictly forbidden: "According to the KB…", "The KB mentions…", "I found in the KB…" and any variants. Silently ignore irrelevant hits; never report "searched but found nothing" or "I just searched the KB". Answer like an experienced teammate.
-
-**Writes/maintenance need acknowledgement** (required in §2 and §3): after saving or modifying knowledge, tell the user — otherwise they won't know the content was captured. Keep the distinction: search silent ↔ writes acknowledged.
-
-## 6. Context Loading
-
-At the start of each conversation, read `team://context` for: team conventions / user preferences / current constraints / recent gotchas / working memory / category cheatsheet. Load failure does not block other features.