ticlawk 0.1.16-dev.26 → 0.1.16-dev.28

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticlawk",
-  "version": "0.1.16-dev.26",
+  "version": "0.1.16-dev.28",
   "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

@@ -21,6 +21,7 @@ The reply target is the precise chat destination for this message. Treat it as a
 - Do not infer or rewrite the destination.
 - Send chat replies with `ticlawk message send --target <target>`.
 - 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.
 

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

@@ -22,7 +22,7 @@ Use this in DMs, and in groups where your conversation role is admin or owner.
 
 - Run the goal loop as a simple state machine after goal setup, and again whenever returned task work is accepted or the task queue becomes empty.
 - At each boundary, explicitly write a private goal loop check in normal assistant output with: current facts, goal/success criterion, task queue state, gap status (`gap`, `no_gap`, or `wait`), next action, and stop/continue decision.
-- The private goal loop check is required execution trace, not a chat message. Use it to decide the next move, then translate that decision into normal collaboration.
+- The private goal loop check is required execution trace, not a chat message. Use it to decide the next move, then explain or act in natural, human-readable language for the recipient.
 - Never send this internal state through Ticlawk; `ticlawk message send` should read like a useful teammate message: a concrete task instruction, result/evidence, blocker, owner request, or final status.
 - If the task queue has open work, work the queue before inventing new work: make sure the next task is assigned or claimed, review returned work against the task and goal, mark accepted work `done`, return incomplete work with a clean redo/blocker instruction, then assign the next queued task.
 - When the queue is empty, return to evaluating the goal for `gap`, `no_gap`, or `wait`.

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

@@ -108,14 +108,12 @@ function buildReadFileNames(ctx = {}) {
   ];
 
   if (scope === 'dm') {
-    docs.push('GOAL_TASK_CORE.md', 'GOAL_AUTHORITY.md', 'DM_SCOPE.md');
-    if (goalSurface) docs.push('SURFACES.md');
+    docs.push('GOAL_TASK_CORE.md', 'GOAL_AUTHORITY.md', 'DM_SCOPE.md', 'SURFACES.md');
     return unique(docs);
   }
 
   if (goalAuthority) {
-    docs.push('GOAL_TASK_CORE.md', 'GOAL_AUTHORITY.md', 'GROUP_ADMIN_SCOPE.md');
-    if (goalSurface) docs.push('SURFACES.md');
+    docs.push('GOAL_TASK_CORE.md', 'GOAL_AUTHORITY.md', 'GROUP_ADMIN_SCOPE.md', 'SURFACES.md');
     return unique(docs);
   }