ticlawk 0.1.16-dev.33 → 0.1.16-dev.35

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticlawk",
-  "version": "0.1.16-dev.33",
+  "version": "0.1.16-dev.35",
   "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/handbook/COMMUNICATION.md

@@ -19,12 +19,16 @@ The reply target is the precise chat destination for this message. Treat it as a
 
 - To reply, copy the reply target from the current incoming message exactly.
 - Do not infer or rewrite the destination.
-- Send chat replies with `ticlawk message send --target <target>`. Write the message body in natural language with normal paragraph breaks; do not use Markdown formatting.
+- Send chat messages with `ticlawk message send --target <target>`.
+  Message body rules:
+  - Write in natural language with normal paragraph breaks; do not use Markdown formatting.
+  - For an immediate reply or a quick update during longer work, keep the body short.
+  - When the work is complete or blocked, send a concise final message.
+  - If you send more than one message in the same turn, do not repeat content already sent.
 - Use `--attach <path>` on `message send` when the user or group should receive a file.
 - When reporting a result to a human, first decide whether the result itself is a file or artifact. If it is, attach it. If it is not, but a visualization would make the result substantially easier to understand, create a concise HTML artifact with `/vibeshare generate` and attach that. Do not create artifacts for ordinary text answers.
 - Keep external messages clean and actionable: answer, instruction, blocker, decision request, or final result.
 - Do not send private scratchpad unless the owner explicitly asks for that analysis.
-- When the work is complete or blocked, send one concise final recipient-facing summary through `ticlawk message send --target <target>`.
 - After that final send succeeds, output exactly `<turn_end>` in normal assistant output and stop. Do not emit any further commentary, status, tool calls, or tokens after `<turn_end>`.
 
 ## Reading Context

package/src/runtimes/_shared/handbook/GOAL_AUTHORITY.md

@@ -8,6 +8,8 @@ Use this in DMs, and in groups where your conversation role is admin or owner.
 
 - You are responsible for driving the conversation toward its goal, not only replying to isolated messages.
 - Maintain or infer the current goal from the direct ask, charter, dashboard/briefing quote, task board, and conversation context.
+- Each turn, first handle the incoming message: reply to the user and do what it asks, sending the result. That is not the end of the turn — then run the goal loop, even if the message was only a quick question.
+- If a goal exists, run the loop and drive any gap (see Goal Loop and Gap States); if none exists, decide whether this message warrants setting one (see Goal Setup When No Specific Goal Exists). The turn ends only when the loop reaches `no_gap` or `wait`.
 
 ## Goal Setup When No Specific Goal Exists
 

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

@@ -82,19 +82,43 @@ function buildCurrentConversationGuide(ctx = {}) {
   return lines.join('\n');
 }
 
+const FILE_DESCRIPTIONS = {
+  'MEMORY.md': 'your durable memory.',
+  'GOAL_AUTHORITY.md': 'it covers our goal-driven loop: what to do whether you have a goal, have none, or got a quick question.',
+  'BASICS.md': 'workspace and work basics.',
+  'COMMUNICATION.md': 'replying via the ticlawk CLI.',
+  'COLLABORATION.md': 'DM/group conduct.',
+  'GOAL_TASK_CORE.md': 'goal/task concepts.',
+  'DM_SCOPE.md': 'DM goal scope.',
+  'SURFACES.md': 'dashboards, briefings, shared tools.',
+  'GROUP_ADMIN_SCOPE.md': 'group admin scope.',
+  'GROUP_MEMBER_SCOPE.md': 'group member scope.',
+  'TASK_WORKER.md': 'executing assigned tasks.',
+};
+
+// Files re-read at the start of every turn, not just once per session.
+// MEMORY.md for continuity; GOAL_AUTHORITY.md so the goal loop runs each turn
+// (it only appears in goal-authority scopes).
+const EVERY_TURN_FILES = new Set(['MEMORY.md', 'GOAL_AUTHORITY.md']);
+
+function describeFile(name) {
+  const desc = FILE_DESCRIPTIONS[name];
+  return desc ? `\`${name}\` — ${desc}` : `\`${name}\``;
+}
+
 function buildReadInstructions(ctx = {}) {
   const files = buildReadFileNames(ctx);
-  const memoryFiles = files.filter((name) => name === 'MEMORY.md');
-  const handbookFiles = files.filter((name) => name !== 'MEMORY.md');
-  const memoryList = memoryFiles.map((name, index) => `${index + 1}. \`${name}\``).join('\n');
-  const handbookList = handbookFiles.map((name, index) => `${index + 1}. \`${name}\``).join('\n');
+  const everyTurn = files.filter((name) => EVERY_TURN_FILES.has(name));
+  const once = files.filter((name) => !EVERY_TURN_FILES.has(name));
+  const everyTurnList = everyTurn.map((name, index) => `${index + 1}. ${describeFile(name)}`).join('\n');
+  const onceList = once.map((name, index) => `${index + 1}. ${describeFile(name)}`).join('\n');
   return `To reply to the user or group, use \`ticlawk message send --target <target>\`. Normal assistant output is private and is not sent to the user. Details are in \`COMMUNICATION.md\`.
 
-Read this file every time before acting because it may be updated:
-${memoryList}
+Read these every turn before acting (they may have changed):
+${everyTurnList}
 
-Read these files if you haven't already. Otherwise, skip:
-${handbookList}`;
+Read these once if you haven't this session. Otherwise skip:
+${onceList}`;
 }
 
 function buildReadFileNames(ctx = {}) {