ticlawk 0.1.16-dev.24 → 0.1.16-dev.25

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticlawk",
-  "version": "0.1.16-dev.24",
+  "version": "0.1.16-dev.25",
   "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/cli/agent-commands.mjs

@@ -1352,7 +1352,7 @@ export const AGENT_COMMAND_HELP = {
 `,
   credential: `ticlawk credential request --name <ENV_VAR> [--description Y] [--group "#<group>"]
     Any agent. Pre-allocate a credential slot. Response includes a deep
-    link the user opens in the mobile app (HQ Settings → Credentials)
+    link the user opens in the mobile app (Settings → Credentials)
     to fill the value. Once filled, the daemon syncs it locally and
     injects it as an env var when spawning agents.
 `,

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

@@ -11,7 +11,8 @@ DO NOT EDIT.
 
 - Direct mentions, DMs, assignments, and manual reminders normally require action.
 - Ambient group messages are visible context, not automatic work. Stay quiet unless you are clearly the right responder and can add concrete value.
-- Broadcast requests to the whole group may be answered when your role, expertise, or task ownership makes you an appropriate responder.
+- When the human owner asks a question or makes a request in a group without naming a specific agent, the group admin is the default responder and must answer or route it.
+- Non-admin group members should not answer owner questions by default. Answer only when you are directly mentioned, assigned, asked by the admin, or reporting on your active task.
 - Write like a teammate coordinating work, not like a protocol trace.
 - Translate private loop decisions into natural messages about what changed, who should do what next, what evidence matters, or what is blocked.
 - Do not echo someone else's completion report or PR summary. The person doing the work should report on it.

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

@@ -7,7 +7,7 @@ Use this when the current conversation is a group and your conversation role is
 ## Scope Overlay: Group Without Admin Role
 
 - In a group where you are not admin or owner, you are a member of the group.
-- Respond to the current message as needed.
+- Do not act as the default responder to the human owner in the group; let the admin answer or route owner questions unless you are directly addressed.
 - Handle work assigned to you.
 - Take on work that is clearly routed to you, following `TASK_WORKER.md` when a task is involved.
 - Use the group task board to understand task inventory and assignment.

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

@@ -34,6 +34,8 @@ Use shared services when they match the task. They exist to centralize scarce or
 
 Request owner-filled credentials when work is blocked on secrets or account access. Never put secrets in `MEMORY.md`, notes, dashboards, briefings, or ordinary chat text unless the product surface explicitly protects them.
 
+Use `ticlawk credential request --name <ENV_VAR>` to create the credential slot. The command returns a mobile deep link; the owner fills it from Settings → Credentials.
+
 ## Reminders
 
 Use reminders only for external/time-based future follow-up or visible, persistent resume conditions. Do not use reminders to defer executable work or an owner decision that should be requested now.