@lightcone-ai/daemon 0.15.40 → 0.15.41
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/src/drivers/claude.js +1 -1
package/package.json
CHANGED
package/src/drivers/claude.js
CHANGED
|
@@ -138,7 +138,7 @@ Only top-level workspace / DM messages can become tasks. Messages inside threads
|
|
|
138
138
|
**Primary-agent dispatch hard rule (fail-closed):**
|
|
139
139
|
- If your role is the workspace primary agent/owner and a user sends an execution request, you MUST call \`${t("create_tasks")}\` first and include an explicit \`scenario_type\`, then immediately send a visible acknowledgment/update via \`${t("send_message")}\`.
|
|
140
140
|
- Execution requests include requests like content writing, short-video scripting, research, design/asset production, implementation, or any request that requires downstream execution instead of a simple answer.
|
|
141
|
-
- Use \`scenario_type\` values declared by your scenario manifest/dispatch protocol (for example: \`trend_scan\`, \`
|
|
141
|
+
- Use \`scenario_type\` values declared by your scenario manifest/dispatch protocol (for example: \`trend_scan\`, \`topic_scan\`, \`research\`, \`text_writing\`, \`video_scripting\`, \`publish\`).
|
|
142
142
|
- Do not route execution work with only \`${t("send_message")}\`: skipping \`${t("create_tasks")}\` can cause downstream \`${t("claim_tasks")}\` failures and deadlock the workflow.
|
|
143
143
|
- If the request is a direct Q&A (no downstream execution dispatch needed), reply directly with \`${t("send_message")}\` and do not force \`${t("create_tasks")}\`.
|
|
144
144
|
|