@yeaft/webchat-agent 0.1.80 → 0.1.81

package/crew/routing.js

@@ -161,7 +161,7 @@ export async function dispatchToRole(session, roleName, content, fromSource, tas
   if (effectiveTaskId && typeof content === 'string') {
     const taskContent = await readTaskFile(session, effectiveTaskId);
     if (taskContent) {
-      content = `${content}\n\n---\n<task-context file="context/features/${effectiveTaskId}.md">\n${taskContent}\n</task-context>`;
+      content = `${content}\n\n---\n<task-context file=".crew/context/features/${effectiveTaskId}.md">\n${taskContent}\n</task-context>`;
     }
   }
 
@@ -169,7 +169,7 @@ export async function dispatchToRole(session, roleName, content, fromSource, tas
   if (typeof content === 'string') {
     const kanbanContent = await readKanban(session);
     if (kanbanContent) {
-      content = `${content}\n\n---\n<kanban file="context/kanban.md">\n${kanbanContent}\n</kanban>`;
+      content = `${content}\n\n---\n<kanban file=".crew/context/kanban.md">\n${kanbanContent}\n</kanban>`;
     }
   }
 

package/crew/task-files.js

@@ -106,7 +106,7 @@ export function parseCompletedTasks(text) {
 }
 
 /**
- * 更新 feature 索引文件 context/features/index.md
+ * 更新 feature 索引文件 .crew/context/features/index.md
  */
 export async function updateFeatureIndex(session) {
   const featuresDir = join(session.sharedDir, 'context', 'features');
@@ -148,7 +148,7 @@ export async function updateFeatureIndex(session) {
 }
 
 /**
- * 追加完成汇总到 context/changelog.md
+ * 追加完成汇总到 .crew/context/changelog.md
  */
 export async function appendChangelog(session, taskId, taskTitle) {
   const contextDir = join(session.sharedDir, 'context');
@@ -218,7 +218,7 @@ export async function saveRoleWorkSummary(session, roleName, accumulatedText) {
 let _kanbanWriteLock = Promise.resolve();
 
 /**
- * 更新工作看板 context/kanban.md
+ * 更新工作看板 .crew/context/kanban.md
  *
  * @param {object} session
  * @param {object} [opts]

package/crew-i18n.js

@@ -87,15 +87,15 @@ ${isDevTeam ? '3' : '2'}. **任务完成** - 所有任务已完成，给出完
 ---END_TASKS---`,
 
     featureRecordTitle: '# Feature 工作记录',
-    featureRecordContent: `系统会自动管理 \`context/features/{task-id}.md\` 工作记录文件：
+    featureRecordContent: `系统会自动管理 \`.crew/context/features/{task-id}.md\` 工作记录文件：
 - PM 分配任务时自动创建文件（包含 task-id、标题、需求描述）
 - 每次 ROUTE 传递时自动追加工作记录（角色名、时间、summary）
 - 你收到的消息中会包含 <task-context> 标签，里面是该任务的完整工作记录
 
 系统还维护以下文件（自动更新，无需手动管理）：
-- \`context/features/index.md\`：所有 feature 的索引（进行中/已完成分类），快速查看项目状态
-- \`context/changelog.md\`：已完成任务的变更记录，每个任务完成时自动追加摘要
-- \`context/kanban.md\`：工作看板，记录每个 feature 的负责人、当前状态和最新进展
+- \`.crew/context/features/index.md\`：所有 feature 的索引（进行中/已完成分类），快速查看项目状态
+- \`.crew/context/changelog.md\`：已完成任务的变更记录，每个任务完成时自动追加摘要
+- \`.crew/context/kanban.md\`：工作看板，记录每个 feature 的负责人、当前状态和最新进展
 你收到的消息中还会包含 <kanban> 标签，里面是工作看板的实时快照。
 你不需要手动创建或更新这些文件，专注于你的本职工作即可。`,
 
@@ -172,8 +172,8 @@ UI/交互方案不确定时找设计师确认。需求不明确时找决策者 "
     teamMembersTitle: '# 团队成员',
     noMembers: '_暂无成员_',
     workConventions: '# 工作约定',
-    workConventionsContent: `- 文档产出写入 context/ 目录
-- 重要决策记录在 context/decisions.md
+    workConventionsContent: `- 文档产出写入 .crew/context/ 目录
+- 重要决策记录在 .crew/context/decisions.md
 - 代码修改使用项目代码路径的绝对路径`,
     stuckRules: '# 卡住上报规则',
     stuckRulesContent: `当你遇到以下情况时，不要自己空转或反复重试，立即 ROUTE 给 PM（pm）请求协调：
@@ -192,11 +192,11 @@ UI/交互方案不确定时找设计师确认。需求不明确时找决策者 "
 - PM 不做 cherry-pick，只负责打 tag
 - 每次新任务/新 feature 必须基于最新的 main 分支创建新的 worktree，确保在最新代码上开发`,
     featureRecordShared: `# Feature 工作记录
-系统自动管理 \`context/features/{task-id}.md\` 工作记录文件：
+系统自动管理 \`.crew/context/features/{task-id}.md\` 工作记录文件：
 - PM 通过 ROUTE 分配任务（带 task + taskTitle 字段）时自动创建
 - 每次角色 ROUTE 传递时自动追加工作记录
 - 角色收到消息时自动注入对应 task 文件内容作为上下文
-- \`context/kanban.md\`：工作看板，记录所有任务的负责人、状态和最新进展
+- \`.crew/context/kanban.md\`：工作看板，记录所有任务的负责人、状态和最新进展
 角色不需要手动创建或更新这些文件。`,
     sharedMemoryTitle: '# 共享记忆',
     sharedMemoryDefault: '_团队共同维护，记录重要的共识、决策和信息。_',
@@ -329,15 +329,15 @@ Important: Do not loop endlessly between roles. When work is substantively compl
 ---END_TASKS---`,
 
     featureRecordTitle: '# Feature Work Records',
-    featureRecordContent: `The system automatically manages \`context/features/{task-id}.md\` work record files:
+    featureRecordContent: `The system automatically manages \`.crew/context/features/{task-id}.md\` work record files:
 - Automatically created when PM assigns tasks (includes task-id, title, requirement description)
 - Work records are appended automatically on each ROUTE handoff (role name, time, summary)
 - Your received messages will include <task-context> tags containing the complete work record for that task
 
 The system also maintains these files (auto-updated, no manual management needed):
-- \`context/features/index.md\`: Index of all features (categorized as in-progress/completed) for quick project status overview
-- \`context/changelog.md\`: Change log of completed tasks, with summary appended when each task completes
-- \`context/kanban.md\`: Work kanban board recording each feature's assignee, current status, and latest progress
+- \`.crew/context/features/index.md\`: Index of all features (categorized as in-progress/completed) for quick project status overview
+- \`.crew/context/changelog.md\`: Change log of completed tasks, with summary appended when each task completes
+- \`.crew/context/kanban.md\`: Work kanban board recording each feature's assignee, current status, and latest progress
 Your received messages will also include <kanban> tags with a real-time snapshot of the work kanban.
 You don't need to manually create or update these files — focus on your core work.`,
 
@@ -414,8 +414,8 @@ After development is complete, send two ROUTE blocks simultaneously to ${revName
     teamMembersTitle: '# Team Members',
     noMembers: '_No members yet_',
     workConventions: '# Work Conventions',
-    workConventionsContent: `- Write documentation output to context/ directory
-- Record important decisions in context/decisions.md
+    workConventionsContent: `- Write documentation output to .crew/context/ directory
+- Record important decisions in .crew/context/decisions.md
 - Use the project code path (absolute path) for code changes`,
     stuckRules: '# Escalation Rules',
     stuckRulesContent: `When you encounter the following situations, do not spin or retry repeatedly — immediately ROUTE to PM (pm) for coordination:
@@ -434,11 +434,11 @@ When escalating, explain: what task you're working on, where you're stuck, and w
 - PM doesn't cherry-pick, only manages tags
 - Each new task/feature must create a new worktree based on the latest main branch to ensure development on latest code`,
     featureRecordShared: `# Feature Work Records
-The system automatically manages \`context/features/{task-id}.md\` work record files:
+The system automatically manages \`.crew/context/features/{task-id}.md\` work record files:
 - Automatically created when PM assigns tasks via ROUTE (with task + taskTitle fields)
 - Work records are appended on each role ROUTE handoff
 - Task file content is auto-injected as context when a role receives a message
-- \`context/kanban.md\`: Work kanban board recording all tasks' assignees, statuses, and latest progress
+- \`.crew/context/kanban.md\`: Work kanban board recording all tasks' assignees, statuses, and latest progress
 Roles don't need to manually create or update these files.`,
     sharedMemoryTitle: '# Shared Memory',
     sharedMemoryDefault: '_Team-maintained shared knowledge, decisions, and information._',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yeaft/webchat-agent",
-  "version": "0.1.80",
+  "version": "0.1.81",
   "description": "Remote agent for Yeaft WebChat — connects worker machines to the central server",
   "main": "index.js",
   "type": "module",