ticlawk 0.1.17-dev.1 → 0.1.17-dev.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticlawk",
-  "version": "0.1.17-dev.1",
+  "version": "0.1.17-dev.2",
   "description": "Local connector that links agent harnesses (Claude Code, Codex, OpenClaw, opencode, Pi) to the Ticlawk mobile app.",
   "type": "module",
   "main": "ticlawk.mjs",

package/src/runtimes/_shared/standing-prompt.mjs

@@ -20,6 +20,24 @@ ${buildReadInstructions(ctx)}
 Read other local files only when the current work clearly needs them.`;
 }
 
+// A goal-lane turn is a single backend FSM step, not a chat message. Its
+// per-step instructions and exact CLI commands (`goal report`, `task`,
+// `approval request`, `message send`) live in the goal-step (user) prompt
+// built by goal-step-prompt.mjs. The system prompt here therefore stays
+// minimal: identity + the one reply invariant. It deliberately omits the
+// chat-lane role framing and handbook read-list, which would compete with
+// the narrow step instruction and pull the model toward proactive
+// assistant behavior. See system.md "Lane-aware standing prompt".
+function buildGoalLaneStandingPrompt(_ctx = {}) {
+  return `You are executing one backend goal-loop step for this conversation, dispatched by the system — not a message from a person. Do only what this step requires; leave work for other steps to those steps.
+
+Your normal output is private and reaches no one. When the step calls for an owner-facing update, send it with \`ticlawk message send --target <target> --phase progress|final\`. Read \`MEMORY.md\` only if the step needs durable context.`;
+}
+
+function isGoalLane(ctx = {}) {
+  return ctx?.inbound?.lane === 'goal' || readDeliveryReason(ctx) === 'transition';
+}
+
 function getInboundRaw(ctx = {}) {
   return ctx?.inbound?.raw && typeof ctx.inbound.raw === 'object'
     ? ctx.inbound.raw
@@ -144,6 +162,7 @@ function unique(values) {
 }
 
 export function buildStandingPrompt(_ctx = {}) {
+  if (isGoalLane(_ctx)) return promptBlock(buildGoalLaneStandingPrompt(_ctx));
   return promptBlock(buildBaseStandingPrompt(_ctx));
 }