@nowcrew/daemon 0.6.6 → 0.6.7

package/README.md

@@ -392,37 +392,45 @@ control frames.
 
 ## Optional TencentDB Agent Memory Bridge
 
-Execution protocol v1 can opt one local NowWork Agent into the private TencentDB Agent Memory Panel.
+Execution protocol v1 can opt NowWork Agents into the private TencentDB Agent Memory Panel.
 This is an external context backend, not a replacement for NowWork messages, tasks, workspace memory,
 or server authorization. It is disabled unless every required variable is present:
 
 ```text
 CREW_AGENT_MEMORY_URL=https://memory.example/path
-CREW_AGENT_MEMORY_INSTANCE_ID=default
-CREW_AGENT_MEMORY_USER_KEY=<load from a secret store>
-CREW_AGENT_MEMORY_USER_ID=<external user id>
-CREW_AGENT_MEMORY_TEAM_ID=<external team id>
-CREW_AGENT_MEMORY_AGENT_ID=<external agent id>
-CREW_AGENT_MEMORY_AGENT_HANDLE=<one local NowWork handle>
+CREW_AGENT_MEMORY_INSTANCE_ID=nowwork
+CREW_AGENT_MEMORY_USER_KEY=<load the external Agent owner's key from a secret store>
+CREW_AGENT_MEMORY_USER_ID=<external Agent owner user id>
+CREW_AGENT_MEMORY_TEAM_ID=team-ueasyuv7sx
+# Legacy single-Agent fallback during rolling upgrades:
+CREW_AGENT_MEMORY_AGENT_ID=agt-vmszw3z170
+CREW_AGENT_MEMORY_AGENT_HANDLE=cindy
 CREW_AGENT_MEMORY_TIMEOUT_MS=3000
 CREW_AGENT_MEMORY_RECALL_LIMIT=8
 ```
 
-The handle is mandatory: one external Agent must not silently aggregate multiple NowWork Agents. To
-enable another handle, create a separate external Agent and configure the daemon that runs that handle.
-Partial configuration fails startup. Removing all `CREW_AGENT_MEMORY_*` variables and restarting the
-daemon is the complete rollback.
+The Agent configuration page owns each non-secret external Agent ID. Turn on `Use long-term memory`,
+enter the matching `agt-*` ID, and save. The server carries that mapping in execution protocol v1; the
+daemon combines it with the configured instance, user key, and team. Different NowWork Agents must use
+different external Agent IDs. `CREW_AGENT_MEMORY_AGENT_ID` and `CREW_AGENT_MEMORY_AGENT_HANDLE` remain
+required as a compatibility fallback for older server records during rolling upgrades. Partial daemon
+configuration fails startup. Removing all `CREW_AGENT_MEMORY_*` variables and restarting the daemon is
+the complete rollback.
 
-On macOS, keep the one-time key in Keychain and resolve it only into the daemon startup environment. For
-the private exploratory deployment, the dedicated records use account `nowwork` and these service names:
+The user key must be able to access the selected external Agent's chat-memory asset. Team membership by
+itself is insufficient for another owner's private asset: the Panel API returns `ASSET_NOT_ACCESSIBLE`.
+Use a key issued to that Agent's owner, or create a dedicated external Agent owned by the daemon account.
+
+On macOS, keep the one-time key in Keychain and resolve it only into the daemon startup environment. Use
+a dedicated service name for the `nowwork` instance; do not reuse a key issued by the `default` instance:
 
 ```bash
 export CREW_AGENT_MEMORY_USER_KEY="$(security find-generic-password \
-  -a nowwork -s nowwork-agent-memory-default -w)"
-export CREW_AGENT_MEMORY_TEAM_ID="$(security find-generic-password \
-  -a nowwork -s nowwork-agent-memory-team-id -w)"
-export CREW_AGENT_MEMORY_AGENT_ID="$(security find-generic-password \
-  -a nowwork -s nowwork-agent-memory-agent-id -w)"
+  -a zuosong -s nowwork-agent-memory-nowwork -w)"
+export CREW_AGENT_MEMORY_USER_ID=usr-uebdjxnkbh
+export CREW_AGENT_MEMORY_TEAM_ID=team-ueasyuv7sx
+export CREW_AGENT_MEMORY_AGENT_ID=agt-vmszw3z170
+export CREW_AGENT_MEMORY_AGENT_HANDLE=cindy
 ```
 
 Do not place the key in a tracked `.env`, shell history, command argument, service description, or log.

package/dist/agent-memory/bridge.js

@@ -12,11 +12,12 @@ function safeReport(report, eventType, message, fields) {
 export function createAgentMemoryBridge(config, dependencies = {}) {
     const client = dependencies.client ?? createAgentMemoryClient(config);
     const report = dependencies.report ?? dslog;
-    const blockId = `chat_memory-${config.teamId}-${config.agentId}`;
+    const resolveAgentId = (agentHandle, agentId) => agentId ?? (agentHandle === config.agentHandle ? config.agentId : null);
     return {
-        recall: async (agentHandle, wakePrompt, executionId) => {
+        recall: async (agentHandle, wakePrompt, executionId, agentId) => {
             const startedAt = Date.now();
-            if (agentHandle !== config.agentHandle) {
+            const externalAgentId = resolveAgentId(agentHandle, agentId ?? null);
+            if (externalAgentId === null) {
                 safeReport(report, "external_agent_memory.recall_observed", "外部 Agent Memory recall 已跳过", {
                     execution_id: executionId,
                     agent_handle: agentHandle,
@@ -26,6 +27,7 @@ export function createAgentMemoryBridge(config, dependencies = {}) {
                 });
                 return "";
             }
+            const blockId = `chat_memory-${config.teamId}-${externalAgentId}`;
             const incoming = extractIncomingMessage(wakePrompt);
             if (incoming === null) {
                 safeReport(report, "external_agent_memory.recall_observed", "外部 Agent Memory recall 已跳过", {
@@ -68,9 +70,10 @@ export function createAgentMemoryBridge(config, dependencies = {}) {
                 return "";
             }
         },
-        capture: async (agentHandle, executionId, wakePrompt, finalText) => {
+        capture: async (agentHandle, executionId, wakePrompt, finalText, agentId) => {
             const startedAt = Date.now();
-            if (agentHandle !== config.agentHandle) {
+            const externalAgentId = resolveAgentId(agentHandle, agentId ?? null);
+            if (externalAgentId === null) {
                 safeReport(report, "external_agent_memory.capture_observed", "外部 Agent Memory capture 已跳过", {
                     execution_id: executionId,
                     agent_handle: agentHandle,
@@ -103,7 +106,7 @@ export function createAgentMemoryBridge(config, dependencies = {}) {
                 return;
             }
             try {
-                const result = await client.importConversation(`nowwork-${executionId}`, messages);
+                const result = await client.importConversation(externalAgentId, `nowwork-${executionId}`, messages);
                 safeReport(report, "external_agent_memory.capture_observed", "外部 Agent Memory capture 已完成", {
                     execution_id: executionId,
                     agent_handle: agentHandle,

package/dist/agent-memory/client.js

@@ -79,10 +79,10 @@ export function createAgentMemoryClient(config, dependencies = {}) {
                 ...(item.created_at === undefined ? {} : { createdAt: item.created_at }),
             }));
         },
-        importConversation: async (sessionId, messages) => {
+        importConversation: async (agentId, sessionId, messages) => {
             const parsed = ImportDataSchema.safeParse(await post("import", {
                 team_id: config.teamId,
-                agent_id: config.agentId,
+                agent_id: agentId,
                 session_id: sessionId,
                 messages,
             }));

package/dist/computer-service.js

@@ -7,9 +7,17 @@ import { dirname, resolve } from "node:path";
 const execFileAsync = promisify(execFile);
 const WINDOWS_STOP_TIMEOUT_MS = 5_000;
 const WINDOWS_STOP_POLL_MS = 100;
+/** Windows cannot spawn .cmd/.bat shims directly with shell:false; route them through cmd.exe explicitly. */
+export function systemCommandInvocation(command, args, platform = process.platform, comSpec = process.env.ComSpec ?? process.env.COMSPEC ?? "cmd.exe") {
+    if (platform === "win32" && /\.(?:cmd|bat)$/iu.test(command)) {
+        return { command: comSpec, args: ["/d", "/s", "/c", command, ...args] };
+    }
+    return { command, args: [...args] };
+}
 export const systemCommandRunner = async (command, args) => {
     try {
-        const result = await execFileAsync(command, [...args], { encoding: "utf8" });
+        const invocation = systemCommandInvocation(command, args);
+        const result = await execFileAsync(invocation.command, [...invocation.args], { encoding: "utf8" });
         return { exitCode: 0, stdout: result.stdout, stderr: result.stderr };
     }
     catch (error) {

package/dist/execution-protocol.js

@@ -115,6 +115,7 @@ export const ExecutionStartSchema = z.object({
         id: z.string().min(1),
         handle: AgentHandleSchema,
         memoryEnabled: z.boolean().optional(),
+        memoryAgentId: z.string().regex(/^agt-[A-Za-z0-9_-]+$/).max(100).optional(),
         projectSkills: z.array(ProjectSkillRefSchema).max(MAX_AGENT_PROJECT_SKILL_BINDINGS).optional(),
         abilityRelease: AbilityReleaseSnapshotSchema.optional(),
     }).strict(),

package/dist/execution-runner.js

@@ -415,7 +415,7 @@ export async function runExecution(config, input, dependencies) {
         let recalledMemory = "";
         if (spec.agent.memoryEnabled === true && dependencies.agentMemory !== undefined) {
             try {
-                recalledMemory = await cancellable(dependencies.agentMemory.recall(spec.agent.handle, spec.instructions.wakePrompt, spec.executionId), dependencies.cancellation);
+                recalledMemory = await cancellable(dependencies.agentMemory.recall(spec.agent.handle, spec.instructions.wakePrompt, spec.executionId, spec.agent.memoryAgentId ?? null), dependencies.cancellation);
             }
             catch (error) {
                 if (error instanceof ExecutionCancelledError)
@@ -720,7 +720,7 @@ export async function runExecution(config, input, dependencies) {
         && memoryCaptureFinalText !== null
         && dependencies.agentMemory !== undefined) {
         try {
-            await dependencies.agentMemory.capture(spec.agent.handle, spec.executionId, spec.instructions.wakePrompt, memoryCaptureFinalText);
+            await dependencies.agentMemory.capture(spec.agent.handle, spec.executionId, spec.instructions.wakePrompt, memoryCaptureFinalText, spec.agent.memoryAgentId ?? null);
         }
         catch {
             // External memory is optional and must never alter the durable execution outcome.

package/dist/machine-info.js

@@ -31,6 +31,7 @@ export const DAEMON_CAPABILITIES = [
     "execution_answer_stream_v1",
     "execution_machine_queue_v1",
     "execution_agent_memory_policy_v1",
+    "execution_agent_memory_mapping_v1",
     "project_skills_v1",
     RUNTIME_HEALTH_PROBE_CAPABILITY,
     "agent_ability_release_v1",

package/dist/prompt.js

@@ -29,7 +29,7 @@ export function capWorkLogForInject(workLog, cap = WORKLOG_INJECT_CAP) {
 }
 export function capMemoryForInject(memory, cap = MEMORY_INJECT_CAP) {
     return memory.length > cap
-        ? `${memory.slice(0, cap)}\n…(MEMORY.md 过长已截断,详情用 Read 读 $CREW_HOME/MEMORY.md 或 notes/)`
+        ? `${memory.slice(0, cap)}\n…(MEMORY.md 过长已截断,详情用 Read 读 $CREW_HOME/MEMORY.md;功能明细仅按索引中的 file 读取)`
         : memory;
 }
 export function buildSystemPrompt(ctx) {
@@ -59,7 +59,7 @@ export function buildSystemPrompt(ctx) {
     // scheduled 换成静默版,不出现任何"先确认/先回复"的措辞。
     const startupSequence = alwaysReport
         ? `## 启动序列(每轮汇报定时任务)
-1. 读 cwd 下的 MEMORY.md,以及处理本轮所需的其它笔记。
+1. 使用本提示词末尾已注入的 MEMORY.md 索引;命中相关条目时,再按索引中的 file 从 $CREW_HOME 读取明细。
 2. 执行唤醒提示词里给出的定时指令。
 3. Return exactly one self-contained final report as your runtime final response.
 4. Do not call crew message send; the daemon delivers the final response.
@@ -67,14 +67,14 @@ export function buildSystemPrompt(ctx) {
 6. 只有存在需要后续跟进的具体事项时,才用 \`crew task create\` 创建任务。`
         : scheduled
             ? `## 启动序列(静默定时任务)
-1. 读 cwd 下的 MEMORY.md,以及处理本轮所需的其它笔记。
+1. 使用本提示词末尾已注入的 MEMORY.md 索引;命中相关条目时,再按索引中的 file 从 $CREW_HOME 读取明细。
 2. 执行唤醒提示词里给出的定时指令。**默认零输出**:不判断"是否需要先确认/声明接手",本轮没有人在等你回复。
 3. 只有发现异常、需要人处理、或指令明确要求汇报时,才用 \`crew message send --send-draft\` 输出到频道(用法见上面"通信"一节)。
 4. 只有存在需要后续跟进的具体事项时,才用 \`crew task create\` 创建任务。
 5. 无异常时直接结束,不需要任何输出,不必读频道历史(除非指令要求)。`
             : `## 启动序列
 1. 若本轮来信可以直接回答,不要先发确认消息;处理完后只发一条完整回复。只有需要澄清、调用工具、协调他人或较长时间处理时,才先发有信息量的确认/进度消息。
-2. 读 cwd 下的 MEMORY.md,以及处理本轮所需的其它笔记。
+2. 使用本提示词末尾已注入的 MEMORY.md 索引;命中相关条目时,再按索引中的 file 从 $CREW_HOME 读取明细。
 3. 若本轮只有"有未读"的 inbox notice、没有正文:notice 表示存在你尚未看到的消息(正文被暂时省略以免刷屏,不是没有内容)。是否读、何时读由你判断,可用 \`crew message check\` / \`crew message read\` 拉取。**绝不能仅凭一条 content-free notice 就断定"没有工作"**;若选择暂不读,要诚实当作 defer。
 4. 收到消息就处理,并用 \`crew message send\` 回复。
 5. **做完你负责的所有事再停。** 多步任务(调研/改码/测试)要全部完成、汇报结果后再停。新消息会在你存活期间自动送达,无需轮询等待。`;
@@ -235,7 +235,7 @@ ${taskAndScheduleCommands}`;
 ## 并行与记忆(CRITICAL — 防冲突 + 防上下文膨胀)
 你**可能同时在处理多个任务**(你自己的多个并行进程)。为避免互相覆盖、并保持上下文精简,严格遵守:
 - **只写两处**:① 本任务的隔离 cwd(代码/草稿);② 本任务的工作日志 **\`$CREW_TASK_LOG\`**(每任务一份,别人不会碰)。在工作日志里记:当前阶段 / 下一步 / 卡在谁 / 关键结论(每条尽量 ≤3 行)。
-- **任务进行中不要改 \`$CREW_HOME/MEMORY.md\` 或 notes/**(那是共享文件,多个并行运行同时写会冲突)。这些只读参考;沉淀经验留到任务关闭时由系统触发的收尾来做。
+- **普通任务进行中不要改 \`$CREW_HOME/MEMORY.md\` 或 notes/**(那是共享文件,多个并行运行同时写会冲突)。这些只读参考;任务 done/closed 后的专门收尾执行才按收尾指令写入功能明细和索引。
 - **跨任务协调看实时清单**:用 \`crew task list --mine\` 查你当前所有任务及其状态(谁在排队、谁在评审)。例:你一次只能测一个页面时,据此判断"正在测 #1、#2 排队",在 #2 的工作日志里标注"等 #1 完成"。
 - 需要更多背景时再 \`Read $CREW_HOME/notes/<topic>.md\`;不要一次把所有笔记读进上下文。
 
@@ -259,14 +259,19 @@ ${actionRule}
 ${interactiveTaskRules}${freshnessRule}${externalReplyRule}${collaborationEtiquette}${humanLanguageSection}${communicationStyle}${skillIntentRule}
 
 ## Workspace 与分层记忆(CRITICAL — 索引+按需,配合上面的并行规则)
-你的持久记忆在 \`$CREW_HOME\`(跨你所有任务共享),分三层:
-1. **MEMORY.md = 索引 + 角色**:指向你全部知识的目录。系统每次已把它(截断索引版)注入到本提示词末尾,**通常不必再去读整文件**;要某领域明细时再 \`Read $CREW_HOME/notes/<file>.md\`。别一次把所有 notes 读进上下文。
-2. **notes/<domain>.md = 明细**:领域知识、用户偏好、频道说明、经验教训(\`notes/lessons.md\`)。**任务进行中只读不写**(多个并行运行同时写会冲突)。
+你的持久记忆在 \`$CREW_HOME\`(跨你所有任务共享),按“常驻索引 + 功能明细 + 当前工作”分层:
+1. **MEMORY.md = 常驻索引 + 角色**:系统每次已把它(截断索引版)注入本提示词末尾。索引条目包含 \`file/type/scope/summary/triggers/priority/updated\`,其中 file 是相对于 \`$CREW_HOME\` 的路径(例如 \`notes/testing.md\`),先用这些字段判断当前问题是否相关;通常不必再读整份 MEMORY.md。
+2. **notes/<topic>.md = 功能明细**:按用户偏好、项目规则、测试、调试、Git、事故复盘等主题拆分。优先读取与当前任务匹配的文件;\`notes/lessons.md\` 只保留未分类经验和历史兼容内容,不是所有新经验的默认目的地。**普通任务进行中只读不写**(多个并行运行同时写会冲突);任务结束后的专门收尾执行按收尾指令写入。
+   - 对旧版 MEMORY.md,如果条目没有完整结构化字段但明确指向 \`notes/<file>.md\`,把它视为 legacy 索引;仍需结合条目标题/链接和当前请求判断相关性,不要因为缺少 summary/triggers 就假定正文已注入。
 3. **本任务 work-log = \`$CREW_TASK_LOG\`**:每任务一份(别的运行不会碰),记当前阶段/下一步/卡点/关键结论。系统已把它的当前内容注入末尾让你续上;有进展就更新它——这是你**唯一**该在任务中持续写的记忆文件。**work-log 是现状快照,不是流水账**:保持 ≤100 行,更新时重写全文替换过时内容,不要无限追加(过长会被注入截断)。
 
-**沉淀与瘦身由系统触发,不要平时做**:任务被改为 done/closed 时,系统会单独唤醒你收尾——那时才把可复用经验从 work-log 提炼进 \`notes/lessons.md\`、更新 MEMORY.md 索引、并清掉该任务的 work-log。平时别动 MEMORY.md/notes,既防并行冲突,也防 MEMORY.md 膨胀。
+**按需读取规则(提示词引导,不是 Daemon 自动召回保证)**:
+- 当前请求命中 MEMORY.md 某条目的 \`summary\` 或 \`triggers\`,或用户明确询问历史经验/偏好时,在最终回答或执行动作前用 \`Read $CREW_HOME/<file>\` 读取对应明细;不要再次拼接 \`notes/\`。
+- 未命中时不要为了“保险”读取全部 notes;只读取能直接影响当前任务的文件。MEMORY.md 注入的是索引,不会自动让 note 正文可用。
 
-**为什么(CRITICAL)**:上下文会被周期压缩;你的恢复力来自——注入的 MEMORY.md 索引(始终精简)+ 本任务 work-log + 按需读 notes,而**不是**把一切堆进 MEMORY.md。
+**沉淀与瘦身由系统触发,不要平时做**:任务被改为 done/closed 时,系统会单独唤醒你收尾——那时按功能分类把可复用经验提炼进合适的 \`notes/<topic>.md\`,更新 MEMORY.md 索引。收尾只有三种清理结果:有内容且明细与索引全部写入成功后清空 work-log;无可留存内容时直接清空;任一记忆写入失败则保留 work-log、停止并报告失败,不得继续清空。不要默认全部写入 \`notes/lessons.md\`。平时别动 MEMORY.md/notes,既防并行冲突,也防 MEMORY.md 膨胀。
+
+**为什么(CRITICAL)**:上下文会被周期压缩;你的恢复力来自——注入的 MEMORY.md 索引(始终精简)+ 本任务 work-log + 按需读相关 notes,而**不是**把一切堆进 MEMORY.md 或一次性加载所有明细。
 ${ctx.memory ? `\n## [注入] 你的 MEMORY.md(索引,只读参考)\n${ctx.memory}` : ""}${ctx.workLog ? `\n## [注入] 本任务 work-log(续上进度;更新写到 $CREW_TASK_LOG)\n${ctx.workLog}` : ""}`;
 }
 /** 静默定时任务的唤醒提示词:不注入协作礼仪/线程提示;默认零输出(设计文档 §5.4)。

package/dist/workspace.js

@@ -2,6 +2,7 @@
  * 准备 agent 在本机的工作区:
  *   <agentsRoot>/<handle>/
  *     ├── MEMORY.md                     长期记忆/角色 (首次创建种子)
+ *     ├── notes/                         按功能拆分的长期记忆明细
  *     ├── .crew/prompts/<execution>.md  按 execution 隔离的系统提示词
  *     └── .crew/crew                    注入 PATH 的 CLI wrapper (0755)
  *
@@ -37,7 +38,9 @@ export async function prepareWorkspace(input) {
     const dir = join(input.agentsRoot, input.handle);
     const crewDir = join(dir, ".crew");
     await mkdir(crewDir, { recursive: true });
-    // MEMORY.md:首次创建"索引 + Active Context"骨架,之后由 agent 自己维护
+    // 预先创建明细目录,让收尾流程可以按功能创建 notes/<topic>.md。
+    await mkdir(join(dir, "notes"), { recursive: true });
+    // MEMORY.md:首次创建"持久身份 + 知识索引"骨架,之后由 agent 自己维护
     const memoryPath = join(dir, "MEMORY.md");
     const memorySeedCreated = !(await exists(memoryPath));
     if (memorySeedCreated) {
@@ -144,7 +147,7 @@ export async function rotateAgentSession(sessionDir) {
     return id;
 }
 /**
- * MEMORY.md 种子骨架:分层记忆的"索引 + Active Context"结构。
+ * MEMORY.md 种子骨架:分层记忆的"持久身份 + 知识索引"结构。
  * 第一次准备工作区时写入;之后 agent 自己维护(系统提示词里有协议)。
  * 建 agent 时填了 description,则用它种子化 ## Role(否则留占位符,由 agent 自填)。
  */
@@ -161,19 +164,33 @@ ${role}
 (What you optimize for.)
 
 ## Knowledge Index
-<!-- The map to your detailed notes. Add a line here whenever you create a note. -->
-<!-- e.g. - [Channels](notes/channels.md) — what each channel is for -->
-<!-- e.g. - [User Preferences](notes/user-preferences.md) — conventions to follow -->
+<!-- The map to your detailed notes. Keep one structured entry per durable note. -->
+<!-- Use this shape:
+### [Topic label]
+- file: notes/<topic>.md
+- type: procedural | semantic | episodic | preference
+- scope: agent_global
+- summary: what this note contains and when it matters
+- triggers: comma-separated topics, commands, or scenarios
+- priority: high | medium | low
+- updated: YYYY-MM-DD
+-->
+<!-- Example:
+### Testing practices
+- file: notes/testing.md
+- type: procedural
+- scope: agent_global
+- summary: Test strategy, regression coverage, and defect-prevention practices.
+- triggers: test, testing, regression, quality, bug, automation
+- priority: high
+- updated: YYYY-MM-DD
+-->
 
-## Active Context
-<!-- Running log of what you're doing now: in-progress tasks, next steps, what you owe whom.
-     Write an entry here BEFORE a long task so you can resume after sleep/compaction. -->
-
----
 How to maintain this file:
 - This is the FIRST file read on every startup (including after context compaction).
-- Keep it self-sufficient: reading only this file should tell you who you are, what you
-  know (and which note to read for detail), what you're working on, and what you owe.
-- Put details in notes/<topic>.md; keep this file an index + active context.
+- Keep durable identity, goals, and the Knowledge Index here; current task progress belongs in $CREW_TASK_LOG.
+- Put details in functional notes/<topic>.md files; keep this file focused on durable identity and the index.
+- Every note index entry must include file, type, scope, summary, triggers, priority, and updated.
+- Keep notes/lessons.md as an uncategorized compatibility area, not the default destination for all lessons.
 `;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nowcrew/daemon",
-  "version": "0.6.6",
+  "version": "0.6.7",
   "type": "module",
   "description": "crew daemon — 运行在用户机器:拉起/管理 agent 进程,注入 crew CLI,归一化 runtime 事件",
   "license": "Apache-2.0",
@@ -16,13 +16,6 @@
   "publishConfig": {
     "access": "public"
   },
-  "scripts": {
-    "daemon": "pnpm --filter @nowcrew/cli build && tsx src/main.ts",
-    "build": "tsc -p tsconfig.json",
-    "prepublishOnly": "pnpm build && node ../scripts/daemon-release-artifact.mjs --strict-registry",
-    "test": "vitest run",
-    "typecheck": "tsc --noEmit"
-  },
   "dependencies": {
     "@agentclientprotocol/sdk": "1.2.1",
     "@nowcrew/cli": "^0.4.13",
@@ -41,5 +34,11 @@
     "tsx": "^4.19.0",
     "typescript": "^5.6.0",
     "vitest": "^2.1.0"
+  },
+  "scripts": {
+    "daemon": "pnpm --filter @nowcrew/cli build && tsx src/main.ts",
+    "build": "tsc -p tsconfig.json",
+    "test": "vitest run",
+    "typecheck": "tsc --noEmit"
   }
-}
+}