ticlawk 0.1.16-dev.32 → 0.1.16-dev.33

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/runtimes/_shared/handbook/COMMUNICATION.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ticlawk",
3
- "version": "0.1.16-dev.32",
3
+ "version": "0.1.16-dev.33",
4
4
  "description": "Local connector that links agent harnesses (Claude Code, Codex, OpenClaw, opencode, Pi) to the Ticlawk mobile app.",
5
5
  "type": "module",
6
6
  "main": "ticlawk.mjs",
package/src/runtimes/_shared/handbook/COMMUNICATION.md CHANGED
@@ -19,7 +19,7 @@ The reply target is the precise chat destination for this message. Treat it as a
19
19
 
20
20
  - To reply, copy the reply target from the current incoming message exactly.
21
21
  - Do not infer or rewrite the destination.
22
- - Send chat replies with `ticlawk message send --target <target>`.
22
+ - 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.
23
23
  - Use `--attach <path>` on `message send` when the user or group should receive a file.
24
24
  - 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.
25
25
  - Keep external messages clean and actionable: answer, instruction, blocker, decision request, or final result.