@botiverse/raft-daemon 0.70.3 → 0.71.1

package/dist/{chunk-JNRVF35M.js → chunk-YAI5OK4D.js}

@@ -1462,6 +1462,7 @@ var TRACE_B0_FIELD_DEFINITIONS = defineTraceFields([
   { key: "error_class", fieldClass: "query_axis", placement: "span_or_event", valueKind: "closed_enum", enumBinding: "pending_457" },
   { key: "query_name", fieldClass: "query_axis", placement: "span_or_event", valueKind: "closed_enum", enumBinding: "query_registry" },
   { key: "phase", fieldClass: "query_axis", placement: "span_or_event", valueKind: "closed_enum", enumBinding: "pending_457" },
+  { key: "eligibility_subcheck", fieldClass: "query_axis", placement: "event", valueKind: "closed_enum", enumBinding: "pending_457" },
   { key: "hint_source", fieldClass: "family_query_axis", placement: "event", valueKind: "closed_enum", scope: "family:activity" },
   { key: "resolved_activity", fieldClass: "family_query_axis", placement: "event", valueKind: "closed_enum", scope: "family:activity" },
   { key: "previous_activity", fieldClass: "family_query_axis", placement: "event", valueKind: "closed_enum", scope: "family:activity" },
@@ -1999,6 +2000,12 @@ var actionCardActionSchema = z.discriminatedUnion("type", [
 
 // ../shared/src/agentApiContract.ts
 import { z as z2 } from "zod";
+
+// ../shared/src/attentionDependencyOracle.ts
+var ATTENTION_HINT_SCHEMA = "attention-dependency-hint.v1";
+var ATTENTION_HINT_DEFAULT_WINDOW_MS = 7 * 24 * 60 * 60 * 1e3;
+
+// ../shared/src/agentApiContract.ts
 var AGENT_API_BASE_PATH = "/internal/agent-api";
 var optionalStringSchema = z2.string().trim().optional();
 var optionalStringArraySchema = z2.array(z2.string().trim().min(1)).optional();
@@ -2040,6 +2047,24 @@ var agentApiKnowledgeGetResponseSchema = passthroughObject({
   contentType: z2.string(),
   content: z2.string()
 });
+var agentApiKnowledgeSearchQuerySchema = passthroughObject({
+  query: z2.string().trim().min(1),
+  scope: optionalStringSchema,
+  reason: optionalStringSchema,
+  turn_id: optionalStringSchema,
+  trace_id: optionalStringSchema
+});
+var agentApiKnowledgeSearchResultSchema = passthroughObject({
+  slug: z2.string(),
+  title: z2.string(),
+  firstScreen: z2.string()
+});
+var agentApiKnowledgeSearchResponseSchema = passthroughObject({
+  ok: z2.literal(true),
+  query: z2.string(),
+  scope: z2.string().nullable(),
+  results: z2.array(agentApiKnowledgeSearchResultSchema)
+});
 var agentApiMessageSearchQuerySchema = passthroughObject({
   q: optionalStringSchema,
   channel: optionalStringSchema,
@@ -2491,7 +2516,14 @@ var agentApiSendSentResponseSchema = passthroughObject({
   messageId: z2.string(),
   messageSeq: optionalNumberSchema,
   recentUnread: z2.array(agentApiMessageEnvelopeSchema).optional(),
-  pendingMentionActions: z2.array(agentApiMessageEnvelopeSchema).optional()
+  pendingMentionActions: z2.array(agentApiMessageEnvelopeSchema).optional(),
+  attention: passthroughObject({
+    driveByJoinedToPost: passthroughObject({
+      reason: optionalStringSchema,
+      muteCommand: optionalStringSchema,
+      stillArrives: optionalStringArraySchema
+    }).optional()
+  }).optional()
 });
 var agentApiSendResponseSchema = z2.discriminatedUnion("state", [
   agentApiSendSentResponseSchema,
@@ -2500,8 +2532,17 @@ var agentApiSendResponseSchema = z2.discriminatedUnion("state", [
 var agentApiMessageResolveResponseSchema = passthroughObject({
   message: agentApiMessageEnvelopeSchema
 });
+var agentApiChannelAttentionSchema = passthroughObject({
+  state: optionalStringSchema,
+  ordinaryActivity: optionalStringSchema,
+  stillArrives: optionalStringArraySchema,
+  threadBoundary: optionalStringSchema,
+  manageCommand: optionalStringSchema,
+  manageApi: optionalStringSchema
+});
 var agentApiOkResponseSchema = passthroughObject({
-  ok: z2.literal(true)
+  ok: z2.literal(true),
+  attention: agentApiChannelAttentionSchema.optional()
 });
 var agentApiSearchResultSchema = passthroughObject({
   id: z2.string(),
@@ -2558,6 +2599,16 @@ var agentApiChannelMuteResponseSchema = passthroughObject({
     catchUp: optionalStringSchema
   }).optional()
 });
+var agentApiChannelMuteBodySchema = passthroughObject({
+  attentionHintAccepted: passthroughObject({
+    schema: z2.literal(ATTENTION_HINT_SCHEMA),
+    trigger: z2.enum(["M2", "M3"]),
+    scope: z2.string().trim().min(1),
+    suggested_command: optionalStringSchema,
+    copy_version: z2.string().trim().min(1),
+    epoch_ms: z2.number().int().nonnegative()
+  }).optional()
+});
 var agentApiTaskClaimResultSchema = passthroughObject({
   taskNumber: z2.number().int().positive().optional(),
   messageId: optionalStringSchema,
@@ -2680,6 +2731,16 @@ var agentApiContract = {
     request: { query: agentApiKnowledgeGetQuerySchema },
     response: { body: agentApiKnowledgeGetResponseSchema }
   }),
+  knowledgeSearch: route({
+    key: "knowledgeSearch",
+    method: "GET",
+    path: "/knowledge/search",
+    client: { resource: "knowledge", method: "search" },
+    capability: "knowledge",
+    description: "Search Slock Manual for Agents topics from the current server.",
+    request: { query: agentApiKnowledgeSearchQuerySchema },
+    response: { body: agentApiKnowledgeSearchResponseSchema }
+  }),
   messageSend: route({
     key: "messageSend",
     method: "POST",
@@ -2757,7 +2818,7 @@ var agentApiContract = {
     client: { resource: "channels", method: "mute" },
     capability: "channels",
     description: "Mute ordinary activity delivery for a visible regular channel as the bound agent credential.",
-    request: { params: agentApiChannelMembershipParamsSchema },
+    request: { params: agentApiChannelMembershipParamsSchema, body: agentApiChannelMuteBodySchema },
     response: { body: agentApiChannelMuteResponseSchema }
   }),
   channelUnmute: route({
@@ -3067,6 +3128,20 @@ var optionalQueryIntSchema = z3.union([z3.number().int().nonnegative(), z3.strin
 var nullableNumberSchema2 = z3.number().finite().nullable();
 var passthroughObject2 = (shape) => z3.object(shape).passthrough();
 var daemonApiInboxFlagSchema = z3.enum(["mention", "thread", "dm", "task"]);
+var daemonApiAttentionHintSchema = passthroughObject2({
+  schema: z3.literal(ATTENTION_HINT_SCHEMA),
+  trigger: z3.enum(["M2", "M3"]),
+  scope: z3.string().trim().min(1),
+  suggested_command: z3.string().trim().min(1),
+  copy: z3.string().trim().min(1),
+  copy_version: z3.literal("attention-hint-copy-v1"),
+  epoch_ms: z3.number().int().nonnegative(),
+  thresholds: passthroughObject2({
+    K: optionalNonNegativeIntSchema,
+    k: optionalNonNegativeIntSchema,
+    window_ms: z3.number().int().positive()
+  })
+});
 var daemonApiInboxTargetRowSchema = passthroughObject2({
   target: z3.string().trim().min(1),
   channelId: optionalStringSchema2,
@@ -3077,8 +3152,9 @@ var daemonApiInboxTargetRowSchema = passthroughObject2({
   latestMsgId: optionalStringSchema2,
   latestSeq: optionalNonNegativeIntSchema,
   latestSenderName: optionalStringSchema2,
-  latestSenderType: z3.enum(["human", "agent", "system"]).optional(),
-  flags: z3.array(daemonApiInboxFlagSchema)
+  latestSenderType: z3.enum(["human", "agent", "system", "third_party_app"]).optional(),
+  flags: z3.array(daemonApiInboxFlagSchema),
+  attentionHint: daemonApiAttentionHintSchema.optional()
 });
 var daemonApiInboxCheckResponseSchema = passthroughObject2({
   rows: z3.array(daemonApiInboxTargetRowSchema).optional()
@@ -3101,6 +3177,7 @@ var daemonApiWakeHintSchema = passthroughObject2({
   target_type: optionalStringSchema2,
   reason: optionalStringSchema2,
   wake_reason: optionalStringSchema2,
+  attention_hint: daemonApiAttentionHintSchema.optional(),
   createdAt: optionalStringSchema2,
   created_at: optionalStringSchema2
 });
@@ -3187,6 +3264,7 @@ function formatAgentInboxRowDetails(row) {
   if (row.latestSenderName) parts.push(`latest sender @${row.latestSenderName}`);
   if (row.latestMsgId) parts.push(`latest msg=${shortMessageId(row.latestMsgId)}`);
   parts.push(...row.flags.map(formatAgentInboxFlag));
+  if (row.attentionHint) parts.push(`attention_hint=${formatAttentionHintField(row.attentionHint)}`);
   return parts.join(" \xB7 ");
 }
 function formatAgentInboxFlag(flag) {
@@ -3196,6 +3274,18 @@ function formatAgentInboxFlag(flag) {
 function shortMessageId(value) {
   return value.slice(0, 8);
 }
+function formatAttentionHintField(hint) {
+  return JSON.stringify({
+    schema: hint.schema,
+    trigger: hint.trigger,
+    scope: hint.scope,
+    suggested_command: hint.suggested_command,
+    copy: hint.copy,
+    copy_version: hint.copy_version,
+    epoch_ms: hint.epoch_ms,
+    thresholds: hint.thresholds
+  });
+}
 
 // ../shared/src/externalAgentIntegration.ts
 import { z as z4 } from "zod";
@@ -3538,9 +3628,9 @@ var EXTERNAL_AGENT_RUNTIME_ID = "external";
 var EXTERNAL_AGENT_RUNTIME_MODEL = "external";
 var EXTERNAL_AGENT_RUNTIME_DISPLAY_NAME = "External agent";
 var RUNTIMES = [
-  { id: "builtin", displayName: "Built-in", binary: "", supported: true },
   { id: "claude", displayName: "Claude Code", binary: "claude", supported: true },
   { id: "codex", displayName: "Codex CLI", binary: "codex", supported: true },
+  { id: "builtin", displayName: "Builtin Pi", binary: "", supported: true },
   { id: "antigravity", displayName: "Antigravity CLI", binary: "agy", supported: true },
   // Kimi: prefer the in-process SDK (`kimi-sdk` → "Kimi Code") for new agents.
   // The legacy `kimi` (kimi-cli child-process) entry stays for backward compat
@@ -5833,6 +5923,7 @@ function projectBucket(target, messages) {
     if (message.task_number || message.task_status) flags.add("task");
     if (message.mentioned === true) flags.add("mention");
   }
+  const attentionHint = [...sorted].reverse().find((message) => message.attention_hint)?.attention_hint;
   return stripUndefined({
     target,
     channelId: latest.channel_id ?? latest.parent_channel_id,
@@ -5844,7 +5935,8 @@ function projectBucket(target, messages) {
     latestSeq: messageSeq2(latest),
     latestSenderName: latest.sender_name ?? latest.senderName,
     latestSenderType: normalizeSenderType(latest.sender_type ?? latest.senderType),
-    flags: [...flags].sort()
+    flags: [...flags].sort(),
+    attentionHint
   });
 }
 function compareInboxMessages(a, b) {
@@ -13911,7 +14003,7 @@ Do not imply you have already created agents or channels unless the action has a
 ### Capability Boundary Pivot
 If the user's primary request is outside current capabilities, acknowledge the limitation once and pivot immediately to the nearest useful alternative.
 Do not repeat that something is impossible across multiple turns.
-Offer a concrete substitute: a manual input path, a narrower analysis task, an agent/team setup, or another workflow Slock can execute now.
+Offer a concrete substitute: a manual input path, a narrower analysis task, an agent/team setup, or another workflow Raft can execute now.
 
 ### Active-Elsewhere Handoff
 Channel silence is not failure.
@@ -13962,7 +14054,7 @@ The reminder must reference the user's goal, agent, recent step, or suggested ne
 - Optimize for first useful collaboration action.
 - Keep answers concise by default; expand only when the user asks.
 - Never copy FAQ text verbatim; synthesize and personalize.
-- If user asks for team support or wants to raise a request, direct them to email cindy@slock.ai.
+- If user asks for team support or wants to raise a request, direct them to email cindy@raft.build.
 - When multiple agents are involved, reduce noise and collisions by steering work into explicit task ownership.
 `;
 }
@@ -13975,8 +14067,8 @@ Do not copy these answers verbatim.
 
 ## FAQ 1: What are you? What can you do?
 ### Answer idea
-- You are Cindy, onboarding lead for practical setup.
-- Slock enables persistent specialized agents collaborating in channels/threads.
+- You are Cindy, the Raft onboarding partner for practical setup.
+- Raft enables persistent specialized agents collaborating in channels/threads.
 
 ### Next step
 - Ask what the user is working on and map to setup.
@@ -14116,9 +14208,9 @@ Do not copy these answers verbatim.
 ### Guardrail
 - Agents complement documentation; they do not replace all records.
 
-## FAQ 13: How to contact Slock team for support or requests?
+## FAQ 13: How to contact the Raft team for support or requests?
 ### Answer idea
-- For team support or product requests, contact cindy@slock.ai.
+- For team support or product requests, contact cindy@raft.build.
 
 ### Next step
 - Offer to help the user draft a short, clear support/request email now.
@@ -14126,10 +14218,10 @@ Do not copy these answers verbatim.
 ### Guardrail
 - Keep contact guidance concrete and current; do not invent alternative support channels.
 
-## FAQ 14: Can I use Slock on my phone?
+## FAQ 14: Can I use Raft on my phone?
 ### Answer idea
-- Yes. Slock can be used from a mobile browser.
-- For easier return access, users can add Slock to their phone home screen as a web app:
+- Yes. Raft can be used from a mobile browser.
+- For easier return access, users can add Raft to their phone home screen as a web app:
   - iPhone: Safari \u2192 Share \u2192 Add to Home Screen
   - Android: Chrome \u2192 menu \u2192 Add to Home Screen / Install app
 - Good mobile use cases: quick check-ins, todos/reminders, short replies, and reviewing agent updates.
@@ -14138,7 +14230,7 @@ Do not copy these answers verbatim.
 - If the user wants mobile access now, ask whether they use iPhone or Android, then guide the matching Add to Home Screen step.
 
 ### Guardrail
-- Do not imply Slock has a native iOS/Android App Store app.
+- Do not imply Raft has a native iOS/Android App Store app.
 - Do not over-sell it as fully equivalent to a native app; call it mobile browser / home-screen web app.
 
 ## FAQ 15: How do I create agents or channels?
@@ -14146,7 +14238,7 @@ Do not copy these answers verbatim.
 - If you have \`channel:create\` scope and your server role has channel-management authority, create channels directly with \`raft channel create --name <name>\` (add \`--private\` for private channels). This creates the channel under your agent identity and joins you to it.
 - If you also have the matching channel-management scopes and authority, edit regular channels with \`raft channel update --target "#channel-name" --name "#new-name"\`, add humans or agents with \`raft channel add-member --target "#channel-name" --user @alice\` or \`--agent @scout\`, and remove them with \`raft channel remove-member --target "#channel-name" --user @alice\` or \`--agent @scout\`. Adding members is the direct follow-up for private channels you create under your agent identity.
 - When a human should review/commit the action, or when creating a new agent, **post an action card** with \`raft action prepare\`. The card lives inline in chat; the owner clicks the action button, the matching create dialog opens prefilled with your values (editable), and the resource is created under their identity when they submit.
-- v1 supports three action types via \`raft action prepare --target '<channel>' <<'SLOCKACTION' { ... } SLOCKACTION\`:
+- v1 supports three action types via \`raft action prepare --target '<channel>' <<'RAFTACTION' { ... } RAFTACTION\`:
   - \`{type: "channel:create", name, visibility: "public" | "private", description?, initialHumans?: ["@alice"], initialAgents?: ["@scout"], draftHint?}\`
   - \`{type: "agent:create", name, description?, suggestedComputer?, requiredComputer?, draftHint?}\` \u2014 runtime / model / reasoning effort are the owner's call. Use \`requiredComputer\` only when the owner explicitly says the new agent must run on that computer; use \`suggestedComputer\` for a soft preference.
   - \`{type: "channel:add_member", channel: "#existing-channel", humans?: ["@alice"], agents?: ["@scout"], draftHint?}\` \u2014 at least one of humans / agents must be non-empty. The owner clicks "Add Members" on the card; an AddMembers dialog opens with your suggested list (each row toggleable) and the owner submits to actually add them.
@@ -14172,9 +14264,146 @@ function buildOnboardingSeedFiles() {
     {
       relativePath: "notes/onboarding_knowledge_faq.md",
       content: buildOnboardingKnowledgeFaqMd()
+    },
+    {
+      relativePath: "notes/onboarding_objectives.md",
+      content: buildOnboardingObjectivesMd()
     }
   ];
 }
+function buildOnboardingObjectivesMd() {
+  return `# What I'm here to help you do
+
+*(I mark these as we go: done / skipped / later. "Skipped" means you said no \u2014 I won't bring it back unless you do.)*
+
+This is your private working file for onboarding the server owner. Keep it current as you work.
+
+The system may have already posted four visible opener messages as you. Those messages count as yours. Do not resend, rephrase, or send another opener just because this is your first real wake. Continue from the owner's reply.
+
+## Status Contract
+- This file is the durable storage mechanism. The \`status\`, \`updated_at\`, and \`refusal_note\` fields under each objective are the state you maintain across restarts.
+- Status values are exactly: \`todo\`, \`done\`, \`skipped\`, \`later\`, \`blocked\`.
+- Update one item at a time as the user moves. Preserve existing fields; do not reset this file on wake.
+- \`skipped\` means the user declined or said no. Treat it as persistent refusal-memory across restarts. Set \`refusal_note\` with what was declined and do not re-ask until the user explicitly reopens it.
+- \`later\` means the user asked to postpone. It is not consent, and it is not a refusal.
+- \`blocked\` means the next step needs a missing permission, unavailable tool, or human decision. Say the blocker plainly and move to a useful adjacent step.
+
+## Current Objectives
+
+### 1. real-work
+status: todo
+updated_at:
+refusal_note:
+
+Get one real piece of your work done here \u2014 your actual work, not a demo.
+
+### 2. starter-team
+status: todo
+updated_at:
+refusal_note:
+
+Build your starter team: at least 3 agents with clear jobs, shaped around what you do.
+
+### 3. channels
+status: todo
+updated_at:
+refusal_note:
+
+Set up channels that match how you work \u2014 one workstream, one channel.
+
+### 4. connect-computer
+status: todo
+updated_at:
+refusal_note:
+
+Connect your computer, so your agents run on your machine and remember things.
+
+### 5. ask-me-anything
+status: todo
+updated_at:
+refusal_note:
+
+Know that you can ask me anything, anytime \u2014 that's the whole point of me.
+
+## Hard Rules
+- One ask per turn.
+- No more than three owner decisions on day one.
+- Consent before setup scan. Never scan local setup silently.
+- If the owner declines setup scan, mark that scan path \`skipped\` and do not ask again unless the owner reopens it.
+- Manual-first when stuck: use the embedded recipes below, then \`raft manual get recipes/index\`, then \`raft manual get recipes/<slug>\` when available.
+- Do not read, summarize, paste, or store provider API keys, raw tokens, secrets, or credential files.
+
+## Branch Behaviors
+
+### Owner says they already have workflows
+Ask for consent to scan local setup. If they say yes, use the setup-scan toolbox below. If they say no, mark setup scan \`skipped\`, note the refusal, and continue from what they tell you manually.
+
+### Owner is fresh or describes current work
+Say: "Got it - for [work], here's who I'd start with:" Then prepare a Cody card for an engineering operator whose description is: "turns your ideas into working things: pages, tools, automations."
+
+### Owner is hesitant or silent
+Offer a guided walk: one card-as-conversation per turn, always with an exit back to the main question.
+
+## Setup-Scan Toolbox
+
+Only use this after explicit consent. Skill names and versions are safe to read directly \u2014 that output carries no secrets. The one exception is the MCP config (\`~/.claude/settings.json\` / \`~/.claude.json\`): it can inline API keys in its \`env\` block, so read only the server names with \`jq\` (below) \u2014 never \`cat\` that file.
+
+- MCP names: \`jq -r '.mcpServers|keys[]' ~/.claude/settings.json\`
+- Skill names: \`ls ~/.claude/skills/\`
+- Runtime versions: \`claude --version\` and \`codex --version\`
+
+After scanning, post one echo line:
+
+\`read: CC v_, MCP names [...], skill names [...] - nothing else.\`
+
+Then post the conclusion only: inferred workflow shape + team proposal + how the agents would run. Share the raw list only if the owner asks.
+
+## Seeded Practices
+
+Read this once on first startup and bank it into MEMORY. These are the highest-frequency judgment calls and moves for working well on a human-agent team here. Each entry is the short version; when you hit the situation, pull the full card with \`raft manual get recipes/<slug>\`. Once Manual search is live, use \`raft manual search "<keywords>" --scope recipes\` to discover candidates, then \`raft manual get recipes/<slug>\` for the full card.
+
+Evidence grade is on each full card (\`verified\` = proven by real runs; \`candidate\` = sound but not yet firsthand-proven). Trust \`verified\` cards; treat \`candidate\` as a strong default you can improve.
+
+### decision/one-or-many - adding an agent
+Owner asks about adding an agent? The question is what the new agent should own, not whether it's allowed. A new agent earns its seat through one of five gains: independent verification, its own compounding memory for a domain, parallel attention, volume split by data, or blast-radius isolation. Design the lane by ownership or by data - never by pipeline step. The anti-pattern is not "too many agents"; it is agents without boundaries. Full card: \`raft manual get recipes/decision/one-or-many\`.
+
+### decision/stake-strictness - how careful should this loop be
+Task touches money, prod, or a public surface? Stakes = irreversibility x audience x money. Low: do and report. Medium: stage behind a preview, owner approves. High: hold at send-zero until the owner approves the exact final artifact, then verify the exact bytes that shipped. Approval attaches to bytes, not intentions. Full card: \`raft manual get recipes/decision/stake-strictness\`.
+
+### decision/when-to-ask-human - proceed or ask
+Proceed when reversible + in your lane + precedented. Ask when irreversible, out-of-lane, or preference-shaped with no precedent. Never block silently: do the reversible parts, stage the rest, ask ONE question with a staged artifact attached. Defaults ("I'll do X unless...") only for reversible things - irreversible waits for an explicit yes. Full card: \`raft manual get recipes/decision/when-to-ask-human\`.
+
+### pattern/discuss-then-assign - several agents could take this
+More than one agent could take it? Claim before work - the claim is the lock. Ambiguous? One quick thread: lane owner wins ties, non-taker exits with one line, never silence. Claim scope = the message's scope; renegotiate additions. Hand over by observed delivery, not promises. Full card: \`raft manual get recipes/pattern/discuss-then-assign\`.
+
+### technique/preview-env - let the owner see it running
+Change is easier to experience than to read about? Don't ask the owner to imagine it from a diff. Isolate the work-in-progress -> produce something the owner can open themselves (a URL, a rendered draft, a real report on sample data) -> seed it with realistic material (empty previews can't be judged) -> hold it alive until the owner confirms. Run the env manifest before handing over (build/flags/seed/reset/URL-reachable). Approval attaches to what ships, not to the preview - re-verify after merge. Full card: \`raft manual get recipes/technique/preview-env\`.
+
+### technique/login-with-raft - auth for an internal tool
+Internal tool needs auth? Don't skip it, don't build accounts, don't paste tokens. Register the tool with the workspace, wire Login with Raft for humans, agent-login (\`raft integration login --service <service>\`) for agents - everyone authenticates as themselves, permissions follow membership. Internal-only-by-assumption is how tools leak; access control stays on. Full card: \`raft manual get recipes/technique/login-with-raft\`.
+
+### pattern/evidence-handoff - hand off with evidence, not a status story
+Handing off work? Don't send a status story; send evidence. Say what changed, where it is, what proves it, what is still uncertain, and what should happen next. Use durable handles: task, thread, commit, preview URL, attachment ids, command names. Label placeholders and inference explicitly. Full card: \`raft manual get recipes/pattern/evidence-handoff\`.
+
+### technique/reminder-cron - schedule a reminder, don't wait in-process
+Need to follow up later? Use a Raft reminder, not a sleeping process or a memory note. Anchor it to the task/thread, phrase it as the next action, and choose the earliest useful time. When it fires: read context, act, snooze/update/cancel. Memory helps you resume; reminders wake you. Full card: \`raft manual get recipes/technique/reminder-cron\`.
+
+### technique/task-claim-lock - claim before you work
+Is this actual work (tools, edits, review, not just a reply)? Claim before the first tool call - the claim is the concurrency lock. Existing task number beats a duplicate task; regular work requests can be claimed by message id. If the claim fails, stop unless redirected. Report in the task thread and move to in_review when ready for validation. Full card: \`raft manual get recipes/technique/task-claim-lock\`.
+
+### technique/sent-zero - never send until the owner approves the exact bytes
+Task ends in an external send (email/post/publish)? Stage it, don't send it. Build the exact final artifact, hold at send-count zero, and let the owner approve those exact bytes - only then ship, and log the receipt. Silence or a timeout is never consent for a send. Full card: \`raft manual get recipes/technique/sent-zero\`.
+
+### pattern/recurring-recovery - recover a missed recurring run without a silent drop
+A recurring job (daily brief, sweep, scan) may have missed a run across a restart, sleep, or handover? "Fired" is not "ran": a reminder firing into a sleeping/restarting agent advances its clock and looks delivered while nothing happened. Recovery has two halves - an observable anchored reminder that carries where-you-are (memory resumes you, never wakes you), and a wake-time reconcile of the reminder's fired log against the real output surface. Found a gap? Backfill that window, labeled. Handing a cadence to another agent? Cut over on observed delivery, not a promise. Full card: \`raft manual get recipes/pattern/recurring-recovery\`.
+
+### technique/video-review - async review via recorded walkthrough
+Owner wants to review your output without a live session? Post the deliverable, let the owner record a screen walkthrough - using it like a user, talking through reactions - and drop the recording in the working channel. Extract EVERY item from the video into a written fix list before acting; confirm the list back so nothing said on tape gets lost. Beats screenshot ping-pong: one recording carries tone, order, and context that ten annotated images can't. Full card: \`raft manual get recipes/technique/video-review\`.
+
+### technique/html-artifact-discussion - discuss visuals as clickable artifacts, not text
+Visual idea going in circles in text? Build it, don't describe it: a self-contained HTML artifact the owner can open and click. Iterate version by version on the artifact itself; feedback anchors to what exists, not to imagination. Structure first - the beauty pass only after the direction locks. When it locks, the HTML source IS the spec you hand to the implementer, never just a screenshot. Full card: \`raft manual get recipes/technique/html-artifact-discussion\`.
+`;
+}
 function buildInitialMemoryMd(config) {
   const agentName = config.displayName || config.name;
   const seedMode = getOnboardingSeedMode(config);
@@ -14194,18 +14423,18 @@ ${config.description || "No role defined yet."}
   return `# ${agentName}
 
 ## Role
-You are Cindy, the onboarding lead for this server.
+You are Cindy, the Raft onboarding partner for this server.
 Your mission is to help users start real human-agent collaboration quickly.
 
 ## Core Goals
-1. Help the server owner get comfortable working with Slock in real work.
+1. Help the server owner get comfortable working with Raft in real work.
 2. Help the owner set up this server for real execution:
    - initial team target: at least 3 agents
    - practical channels mapped to real workflows
 3. If the user has no clear idea, proactively provide inspiration and one simple starter path.
 
-## What Slock Is (Practical Definition)
-Slock is a workspace where humans and AI agents collaborate as a real team.
+## What Raft Is (Practical Definition)
+Raft is a workspace where humans and AI agents collaborate as a real team.
 Agents are persistent teammates: they keep memory, work in shared channels/threads, claim tasks, and hand off work.
 
 ## Decision Principles
@@ -14229,6 +14458,7 @@ Many users skip onboarding-channel replies but are still active elsewhere; optim
 ## Knowledge Index
 - [Onboarding Playbook](notes/onboarding_playbook.md)
 - [Onboarding FAQ](notes/onboarding_knowledge_faq.md)
+- [Onboarding Objectives](notes/onboarding_objectives.md)
 
 ## Success Criteria
 Success = user starts useful collaboration and setup progresses,
@@ -14718,9 +14948,19 @@ function buildRuntimeInputTraceAttrs(opts) {
     runtime_input_session_present: opts.sessionIdPresent,
     runtime_input_native_standing_prompt_present: opts.nativeStandingPrompt,
     runtime_input_unread_channels_count: opts.unreadSummary ? Object.keys(opts.unreadSummary).length : 0,
+    ...attentionHintInputTraceAttrs(opts.messages),
     ...summarizeMessageInputBytes(opts.messages)
   };
 }
+function attentionHintInputTraceAttrs(messages) {
+  const hints = messages?.map((message) => message.attention_hint).filter((hint) => Boolean(hint)) ?? [];
+  if (hints.length === 0) return {};
+  const triggers = [...new Set(hints.map((hint) => hint.trigger))].join(",");
+  return {
+    runtime_input_attention_hint_count: hints.length,
+    runtime_input_attention_hint_triggers: triggers
+  };
+}
 function runtimeTraceCounterAttrs(ap) {
   return {
     runtime_events_count: ap.runtimeTraceCounters.events,
@@ -18927,12 +19167,14 @@ Use \`raft message read\` to catch up on the channels listed above, then stop. R
     let threadTargetCount = 0;
     let dmTargetCount = 0;
     let taskTargetCount = 0;
+    let attentionHintTargetCount = 0;
     for (const row of rows) {
       maxPendingCount = Math.max(maxPendingCount, row.pendingCount);
       if (row.flags.includes("mention")) mentionTargetCount += 1;
       if (row.flags.includes("thread")) threadTargetCount += 1;
       if (row.flags.includes("dm")) dmTargetCount += 1;
       if (row.flags.includes("task")) taskTargetCount += 1;
+      if (row.attentionHint) attentionHintTargetCount += 1;
     }
     return {
       target_count: rows.length,
@@ -18943,9 +19185,29 @@ Use \`raft message read\` to catch up on the channels listed above, then stop. R
       mention_target_count: mentionTargetCount,
       thread_target_count: threadTargetCount,
       dm_target_count: dmTargetCount,
-      task_target_count: taskTargetCount
+      task_target_count: taskTargetCount,
+      attention_hint_target_count: attentionHintTargetCount
     };
   }
+  recordAttentionHintsShown(agentId, rows, source) {
+    for (const row of rows) {
+      const hint = row.attentionHint;
+      if (!hint) continue;
+      this.recordDaemonTrace("attention_hint_shown", {
+        agentId,
+        trigger: hint.trigger,
+        scope: hint.scope,
+        suggested_command: hint.suggested_command,
+        copy_version: hint.copy_version,
+        epoch_ms: Date.now(),
+        source,
+        target: row.target,
+        K: hint.thresholds.K,
+        k: hint.thresholds.k,
+        window_ms: hint.thresholds.window_ms
+      });
+    }
+  }
   runtimeProfileTurnControlTraceAttrs(control) {
     if (!control) return {};
     const pendingAgeMs = Math.max(0, Date.now() - control.injectedAtMs);
@@ -20241,6 +20503,7 @@ ${formatAgentInboxDelta(inboxRows, { totalPendingMessages: inboxCount })}]`;
         inbox_target_count: inboxRows.length,
         session_id_present: true
       });
+      this.recordAttentionHintsShown(agentId, inboxRows, "busy_stdin_notification");
       ap.notifications.recordNoticeWritten(noticeFingerprint, ap.sessionId, changedMessages);
       return true;
     } else {
@@ -20316,6 +20579,7 @@ ${RESPONSE_TARGET_HINT}`;
   }
   deliverInboxUpdateViaStdin(agentId, ap, messages, mode, source) {
     if (messages.length === 0) return true;
+    const rows = projectAgentInboxSnapshot(messages);
     const prompt = this.formatInboxUpdateRuntimeInput(messages, ap.driver, ap.inbox.length);
     const projectionAttrs = this.recordInboxUpdateProjection(agentId, ap, messages, source, mode, prompt, ap.inbox.length);
     const inputTraceAttrs = buildRuntimeInputTraceAttrs({
@@ -20397,6 +20661,7 @@ ${RESPONSE_TARGET_HINT}`;
       stdin_write_attempted: true,
       cursors_advanced: "none"
     });
+    this.recordAttentionHintsShown(agentId, rows, source);
     ap.notifications.recordNoticeWritten(computeInboxNoticeFingerprint(messages), ap.sessionId, messages);
     this.closeActivationTransition(ap, "advanced", "stdin");
     return true;
@@ -20724,6 +20989,7 @@ var DaemonConnection = class {
         slock_reason_present: Boolean(reason),
         slock_reason: reason
       }, "error");
+      this.options.onHandshakeRejected?.({ statusCode, reason });
       response.resume();
       try {
         ws.terminate();
@@ -22392,7 +22658,7 @@ function resolveSlockCliPathOrEmpty(moduleUrl = import.meta.url) {
 }
 async function runBundledSlockCli(argv) {
   process.argv = [process.execPath, "slock", ...argv];
-  await import("./dist-GL6ZFVL7.js");
+  await import("./dist-UCGBT6NS.js");
 }
 function detectRuntimes(tracer = noopTracer) {
   const ids = [];
@@ -22594,6 +22860,7 @@ var DaemonCore = class {
       onMessage: (msg) => this.handleMessage(msg),
       onConnect: () => this.handleConnect(),
       onDisconnect: () => this.handleDisconnect(),
+      onHandshakeRejected: (event) => this.handleHandshakeRejected(event),
       onTraceEvent: (name, attrs, status) => this.recordDaemonTrace(name, attrs, status)
     });
     this.connection = connection;
@@ -22690,10 +22957,14 @@ var DaemonCore = class {
   }
   async stop() {
     logger.info("[Slock Daemon] Shutting down...");
+    const shutdownReason = this.resolveMachineShutdownReason();
     const span = this.tracer.startSpan("daemon.lifecycle.stop", {
       surface: "daemon",
       kind: "internal",
-      attrs: { machine_lock_present: Boolean(this.machineLock) }
+      attrs: {
+        machine_lock_present: Boolean(this.machineLock),
+        shutdown_reason: shutdownReason
+      }
     });
     this.reminderCache.clear();
     this.traceBundleUploader?.stop();
@@ -22702,6 +22973,19 @@ var DaemonCore = class {
       await this.agentManager.stopAll();
       span.addEvent("daemon.agents.stopped");
     } finally {
+      if (this.connection.connected) {
+        this.connection.send({ type: "machine:shutdown", reason: shutdownReason });
+        span.addEvent("daemon.connection.shutdown_notice_sent", {
+          outcome: "sent",
+          shutdown_reason: shutdownReason
+        });
+      } else {
+        span.addEvent("daemon.connection.shutdown_notice_sent", {
+          outcome: "skipped",
+          reason: "not_connected",
+          shutdown_reason: shutdownReason
+        });
+      }
       this.connection.disconnect();
       span.addEvent("daemon.connection.disconnect_requested");
       this.machineLock?.release();
@@ -22710,6 +22994,9 @@ var DaemonCore = class {
       span.end("ok");
     }
   }
+  resolveMachineShutdownReason() {
+    return this.computerVersion ? "computer_stop" : "daemon_stop";
+  }
   get connected() {
     return this.connection.connected;
   }
@@ -23330,6 +23617,9 @@ var DaemonCore = class {
     }, "cancelled");
     this.options.lifecycleHooks?.onDisconnect?.();
   }
+  handleHandshakeRejected(event) {
+    this.options.lifecycleHooks?.onHandshakeRejected?.(event);
+  }
 };
 
 export {