@somacheck/vibecheck 0.6.13 → 0.6.14

package/README.md

@@ -11,7 +11,7 @@ Your agent has your context. It does not have your gut. This is the bridge.
 
 Fair. Here is what you need, without executing anything.
 
-**What the `link` command does.** `npx -y @somacheck/vibecheck@0.6.13 link <CODE> --client <CLIENT>`
+**What the `link` command does.** `npx -y @somacheck/vibecheck@0.6.14 link <CODE> --client <CLIENT>`
 exchanges a short-lived pairing code, generated inside the SomaCheck iOS app, for
 a bearer token. It writes that token to `~/.sensie/config.json` with mode `0600`,
 offers to configure supported agent clients found on the computer, and checks the
@@ -42,8 +42,8 @@ code is not used. Non-interactive implicit selection,
 
 **What the server does once running.** It exposes MCP tools that share bounded,
 user-authorized context summaries, create a statement for the user to test,
-read its outcome, recover recent completed gesture context, and keep a
-three-statement feed stocked. Version 0.6 adds `request_vibecheck` for a
+read its outcome, recover recent completed gesture context, and optionally stock
+up to three feed items when the person asks. Version 0.6 adds `request_vibecheck` for a
 person-approved, immediate phone check-in. That path is deliberately separate
 from the reflection feed.
 
@@ -102,20 +102,20 @@ before the pairing code is redeemed.
 To configure or repair a client later:
 
 ```text
-npx -y @somacheck/vibecheck@0.6.13 setup codex
-npx -y @somacheck/vibecheck@0.6.13 setup claude
-npx -y @somacheck/vibecheck@0.6.13 doctor
+npx -y @somacheck/vibecheck@0.6.14 setup codex
+npx -y @somacheck/vibecheck@0.6.14 setup claude
+npx -y @somacheck/vibecheck@0.6.14 doctor
 ```
 
 Manual Codex registration remains available. Its stdio runtime command is
-`npx -y @somacheck/vibecheck@0.6.13 serve --client codex`:
+`npx -y @somacheck/vibecheck@0.6.14 serve --client codex`:
 
    ```json
    {
      "mcpServers": {
        "vibecheck": {
          "command": "npx",
-        "args": ["-y", "@somacheck/vibecheck@0.6.13", "serve", "--client", "codex"]
+        "args": ["-y", "@somacheck/vibecheck@0.6.14", "serve", "--client", "codex"]
        }
      }
    }
@@ -287,9 +287,9 @@ blocked until the capability and revocation probe in the safety review passes.
 | Tool | What it does |
 |---|---|
 | `get_vibecheck_context` | Read recent completed gestures for this exact agent link without retaining every `request_id`. |
-| `get_vibecheck_status` | Read the live three-proposition cache and how many distinct insights it needs. |
+| `get_vibecheck_status` | Read the three-proposition database cache and its available capacity; this does not verify phone display. |
 | `share_somacheck_context` | Share 1–20 bounded, derived, user-authorized observations; raw conversations and secrets are rejected. |
-| `post_vibecheck_statement` | Add one to three personalized statements without blocking; one may become the current Home vibe check and the rest wait under Vibe Checks without extra pushes. Returns a stable `request_id` for each. |
+| `post_vibecheck_statement` | When the person asks to stock reflections for later or has explicitly authorized scheduled stocking, add one to the reported available maximum without blocking. One may become database-current and the rest queue under Vibe Checks without extra pushes. Returns a stable `request_id` for each created row; it does not verify phone display. |
 | `get_vibecheck_result` | Read that exact proposition once by `request_id`; returns queued, pending, or its terminal result. |
 | `request_vibecheck` | With per-ask consent, send one immediate phone vibecheck, wait boundedly for its exact answer, and retain an opaque `live:<uuid>` fallback handle. |
 
@@ -346,20 +346,26 @@ statement with the same `idempotency_key`.
 
 An immediate vibecheck is not proposition caching. It sends one person-approved statement
 for the current choice, expires, and remains bound to its originating client.
+Handle multiple immediate requests one at a time; do not turn the reflection feed
+into a surrogate queue of immediate asks.
 The reflection feed remains asynchronous and keeps its three-item cache
 behavior. When no immediate Live Ask or delivery test has priority, one current
 feed item may appear on Home. The other items remain visible as **Up next**
 under **Settings → Vibe Checks** and do not generate extra notifications.
 
-The agent maintains three distinct insights. SomaCheck presents one at a time;
-the other two remain cached. After a completed gesture, the next cached insight
+The database feed has capacity for three distinct insights, but capacity is not
+a quota. Stock only the genuinely useful items the person asked to save for later,
+from one up to the available maximum; never invent filler. SomaCheck can present
+one at a time while other created items remain cached. After a completed gesture, the next cached insight
 is promoted and the open slot is marked for replenishment automatically. Cached insights
 expire sooner than a presented check-in so stale context does not masquerade as
 a timely observation.
 
-For a prompt-free loop, run the agent on a background schedule: call
-`get_vibecheck_context`, then `get_vibecheck_status`, and post exactly
-`propositions_needed` distinct statements. MCP supplies the tools and durable
+For a scheduled loop, call `get_vibecheck_context` and `get_vibecheck_status`.
+Only when the person has asked to stock later reflections, post between one and
+the reported `propositions_needed` maximum; it is available capacity, not a
+required count. An explicit, still-active opt-in to scheduled stocking covers
+later scheduled runs without asking again each time. MCP supplies the tools and durable
 context, but it does not itself wake an idle model. Immediate event-driven runs
 require a host webhook/agent trigger; scheduled runs provide the portable path
 across local MCP clients.

package/dist/constants.js

@@ -2,7 +2,7 @@
 export const SUPABASE_URL = "https://pbldcmniommltbdwuykk.supabase.co";
 export const SUPABASE_PUBLISHABLE_KEY = "sb_publishable_af-lUNI2FqEcb-oGy-4uxQ_cnm6kY85";
 export const PACKAGE_NAME = "@somacheck/vibecheck";
-export const PACKAGE_VERSION = "0.6.13";
+export const PACKAGE_VERSION = "0.6.14";
 export const PACKAGE_SPEC = `${PACKAGE_NAME}@${PACKAGE_VERSION}`;
 export const SOMACHECK_SETUP_URL = "https://testflight.apple.com/join/C4mAH3zz";
 export const MCP_SERVER_NAME = "vibecheck";

package/dist/recipes.js

@@ -52,8 +52,8 @@ export const RECIPE_CATALOG = [
             "The product or integration owner has provisioned an organization-authorized Maze connection or partner sandbox at https://connect.maze.co/mcp; running this recipe does not ask the researcher to sign up, upgrade, administer access, or populate Maze data.",
             "The provisioned workspace supplies one named existing study with safe metadata or an aggregate summary; if it does not, the Maze half remains untested and the researcher still receives a copy-ready plan.",
         ],
-        starterPrompt: "Use Maze and SomaCheck to help me reflect on my own interpretation plan for one named Maze study. I am the researcher and I am holding the phone. The study is [STUDY NAME OR ID PROVIDED BY THE WORKSPACE OWNER]. Use only the preconfigured official hosted read-only Maze MCP at https://connect.maze.co/mcp. Read only that study's safe metadata or one aggregate summary. Do not retrieve transcripts, recordings, heatmaps, click maps, mission answers, participant identifiers, contact fields, demographic exports, free text, or row-level data. Label what Maze literally reports separately from your interpretation, then offer two defensible framings. Offer one short first-person proposition about my own interpretation plan and wait for my acceptance before any proactive SomaCheck ask. Treat Aligned or Unaligned plus confidence as context, not truth, diagnosis, authorization, or evidence about a participant. Ask what I choose in words. Keep the proposition, reading, confidence, and confirmation out of Maze. Do not create, edit, publish, delete, archive, export, share, tag, comment, or otherwise write to Maze. If the preconfigured connection or a safe runtime read is absent, label the Maze half untested, return a copy-ready interpretation plan, and tell the integration owner what capability is missing. Do not ask me to sign up, upgrade, administer access, or populate Maze data.",
-        successCondition: "The researcher receives at most one optional signal about their own proposition and states a typed choice after a real metadata or aggregate read from a preconfigured workspace; no participant data or SomaCheck output enters Maze, and the Maze workspace remains unchanged.",
+        starterPrompt: "Use Maze and SomaCheck to help me reflect on my own interpretation plan for one named Maze study. I am the researcher and I am holding the phone. The study is [STUDY NAME OR ID PROVIDED BY THE WORKSPACE OWNER]. Use only the preconfigured official hosted read-only Maze MCP at https://connect.maze.co/mcp. Read only that study's safe metadata or one aggregate summary. Do not retrieve transcripts, recordings, heatmaps, click maps, mission answers, participant identifiers, contact fields, demographic exports, free text, or row-level data. Label what Maze literally reports separately from your interpretation, then offer two defensible framings. Offer one short first-person proposition about my own interpretation plan and wait for my acceptance before any proactive SomaCheck ask. Treat Aligned or Unaligned plus confidence as context, not truth, diagnosis, authorization, or evidence about a participant. Ask what I choose and accept any explicit response available in this interface. Keep the proposition, reading, confidence, and confirmation out of Maze. Do not create, edit, publish, delete, archive, export, share, tag, comment, or otherwise write to Maze. If the preconfigured connection or a safe runtime read is absent, label the Maze half untested, return a copy-ready interpretation plan, and tell the integration owner what capability is missing. Do not ask me to sign up, upgrade, administer access, or populate Maze data.",
+        successCondition: "The researcher receives at most one optional signal about their own proposition and explicitly indicates their choice after a real metadata or aggregate read from a preconfigured workspace; no participant data or SomaCheck output enters Maze, and the Maze workspace remains unchanged.",
     },
     {
         id: "chattermill-research-reflection-v1",
@@ -66,8 +66,8 @@ export const RECIPE_CATALOG = [
             "The product or integration owner has provisioned an organization-authorized Chattermill connection or partner sandbox at https://app.chattermill.com/mcp with mcp:read; running this recipe does not ask the researcher to sign up, purchase access, administer access, or populate Chattermill data.",
             "The provisioned workspace supplies one named existing project for which get_metrics or generate_highlights is sufficient; get_feedback, search_observations, identifier-bearing attributes, and free text remain prohibited.",
         ],
-        starterPrompt: "Use Chattermill and SomaCheck to help me reflect on my own interpretation of one named project's customer-feedback insights. I am the researcher and I am holding the phone. The project is [PROJECT NAME OR ID PROVIDED BY THE WORKSPACE OWNER]. Use only the preconfigured official hosted read-only Chattermill MCP at https://app.chattermill.com/mcp. Read only aggregate metrics with get_metrics or generated highlights with generate_highlights, plus the minimum discovery metadata needed to build that query. Never call get_feedback or search_observations, enumerate identifier-bearing attributes, or surface individual feedback, source quotes, respondent identifiers, contact fields, or free text. Label what the aggregate output literally reports separately from your interpretation, then offer two defensible interpretations. Offer one short first-person proposition about my own interpretation or next step and wait for my acceptance before any proactive SomaCheck ask. Treat Aligned or Unaligned plus confidence as context, not truth, diagnosis, authorization, or evidence about an individual customer. Ask what I choose in words. Keep the proposition, reading, confidence, and confirmation out of Chattermill. Do not create, edit, publish, delete, share, export, tag, comment, or otherwise write to Chattermill. If the preconfigured connection, mcp:read, or a safe aggregate runtime tool is absent, label the Chattermill half untested, return a copy-ready interpretation, and tell the integration owner what capability is missing. Do not ask me to sign up, purchase access, administer access, or populate Chattermill data.",
-        successCondition: "The researcher receives at most one optional signal about their own proposition and states a typed choice after a real aggregate or generated-summary read from a preconfigured workspace; no individual feedback or SomaCheck output enters the cross-MCP flow, and Chattermill remains unchanged.",
+        starterPrompt: "Use Chattermill and SomaCheck to help me reflect on my own interpretation of one named project's customer-feedback insights. I am the researcher and I am holding the phone. The project is [PROJECT NAME OR ID PROVIDED BY THE WORKSPACE OWNER]. Use only the preconfigured official hosted read-only Chattermill MCP at https://app.chattermill.com/mcp. Read only aggregate metrics with get_metrics or generated highlights with generate_highlights, plus the minimum discovery metadata needed to build that query. Never call get_feedback or search_observations, enumerate identifier-bearing attributes, or surface individual feedback, source quotes, respondent identifiers, contact fields, or free text. Label what the aggregate output literally reports separately from your interpretation, then offer two defensible interpretations. Offer one short first-person proposition about my own interpretation or next step and wait for my acceptance before any proactive SomaCheck ask. Treat Aligned or Unaligned plus confidence as context, not truth, diagnosis, authorization, or evidence about an individual customer. Ask what I choose and accept any explicit response available in this interface. Keep the proposition, reading, confidence, and confirmation out of Chattermill. Do not create, edit, publish, delete, share, export, tag, comment, or otherwise write to Chattermill. If the preconfigured connection, mcp:read, or a safe aggregate runtime tool is absent, label the Chattermill half untested, return a copy-ready interpretation, and tell the integration owner what capability is missing. Do not ask me to sign up, purchase access, administer access, or populate Chattermill data.",
+        successCondition: "The researcher receives at most one optional signal about their own proposition and explicitly indicates their choice after a real aggregate or generated-summary read from a preconfigured workspace; no individual feedback or SomaCheck output enters the cross-MCP flow, and Chattermill remains unchanged.",
     },
     {
         id: "user-interviews-research-reflection-v1",
@@ -80,8 +80,8 @@ export const RECIPE_CATALOG = [
             "The planning workflow requires no User Interviews account or connector because it calls no platform data or action tool.",
             "For partner integration validation only, the product or integration owner may supply a preconfigured partner sandbox whose runtime capability list can be inspected without invoking a project, recruitment, participant-data, contact, publication, or spend tool; the researcher is never asked to request access or populate platform data.",
         ],
-        starterPrompt: "Use User Interviews and SomaCheck to help me prepare one clearly named, participant-free test-project plan without changing User Interviews. I am the researcher and I am holding the phone. The study idea is [STUDY IDEA]. Work only from what I provide here. If a product or integration owner has supplied a preconfigured official User Interviews partner sandbox, you may inspect its capability names and schemas, but do not call any platform data or action tool. The planning workflow does not require me to sign up, request access, purchase a plan, or populate User Interviews data. Do not retrieve candidates, participants, screeners, responses, profiles, identifiers, messages, recordings, transcripts, session data, or other workspace data. Propose two neutral study framings and show the exact signal-free project copy. Then offer one short first-person proposition about my own preferred direction and wait for my acceptance before any proactive SomaCheck ask. Treat Aligned or Unaligned plus confidence as context, not truth, diagnosis, authorization, or evidence about another person. Ask what I choose in words. Keep the proposition, reading, confidence, and confirmation out of User Interviews. Return a copy-ready project payload only. Do not create, edit, recruit, invite, message, schedule, screen, launch, publish, attach incentives, spend, read participant data, or call a broader or undocumented tool.",
-        successCondition: "The researcher receives at most one optional signal about their own proposition and states a typed choice; the agent returns a copy-ready signal-free test-project plan, invokes no User Interviews data or action tool, and performs no recruitment, participant read, contact, mutation, launch, publication, incentive, payment, or spend.",
+        starterPrompt: "Use User Interviews and SomaCheck to help me prepare one clearly named, participant-free test-project plan without changing User Interviews. I am the researcher and I am holding the phone. The study idea is [STUDY IDEA]. Work only from what I provide here. If a product or integration owner has supplied a preconfigured official User Interviews partner sandbox, you may inspect its capability names and schemas, but do not call any platform data or action tool. The planning workflow does not require me to sign up, request access, purchase a plan, or populate User Interviews data. Do not retrieve candidates, participants, screeners, responses, profiles, identifiers, messages, recordings, transcripts, session data, or other workspace data. Propose two neutral study framings and show the exact signal-free project copy. Then offer one short first-person proposition about my own preferred direction and wait for my acceptance before any proactive SomaCheck ask. Treat Aligned or Unaligned plus confidence as context, not truth, diagnosis, authorization, or evidence about another person. Ask what I choose and accept any explicit response available in this interface. Keep the proposition, reading, confidence, and confirmation out of User Interviews. Return a copy-ready project payload only. Do not create, edit, recruit, invite, message, schedule, screen, launch, publish, attach incentives, spend, read participant data, or call a broader or undocumented tool.",
+        successCondition: "The researcher receives at most one optional signal about their own proposition and explicitly indicates their choice; the agent returns a copy-ready signal-free test-project plan, invokes no User Interviews data or action tool, and performs no recruitment, participant read, contact, mutation, launch, publication, incentive, payment, or spend.",
     },
     {
         id: "sprig-research-reflection-v1",
@@ -108,7 +108,7 @@ export const RECIPE_CATALOG = [
             "The product or integration owner has provisioned an organization-authorized Great Question connection or partner sandbox at https://greatquestion.co/api/mcp/v1 with PII hiding enabled; running this recipe does not ask the researcher to sign up, upgrade, purchase, administer access, or populate Great Question data.",
             "The owner supplies one participant-free test study, and the client restricts the platform half to get_survey_study for that exact artifact; no discovery or mutation tool is approved.",
         ],
-        starterPrompt: "Use Great Question and SomaCheck to help me reflect on a five-question test survey plan without changing Great Question. I am the researcher and I am holding the phone. The product or integration owner has provisioned a partner sandbox and named this participant-free test study: [TEST STUDY NAME OR ID]. Read only that study's safe title, purpose, and question structure with get_survey_study. Do not search or list the workspace, and do not read candidates, participants, screeners, responses, sessions, transcripts, recordings, highlights, insights, reels, or other workspace data. Propose two neutral study framings and show their exact questions. Then offer one short first-person proposition about my own preferred framing and wait for my acceptance before any proactive SomaCheck ask. Give the agent the Aligned or Unaligned result plus confidence as context and let it use that context with its judgment. Ask what I choose in words. Keep the proposition, reading, confidence, and my confirmation out of Great Question. Return a signal-free, copy-ready research plan only. Do not create, update, delete, recruit, invite, message, schedule, incentivize, launch, publish, or otherwise write to Great Question. Do not ask me to sign up, upgrade, purchase, administer access, or populate Great Question data.",
+        starterPrompt: "Use Great Question and SomaCheck to help me reflect on a five-question test survey plan without changing Great Question. I am the researcher and I am holding the phone. The product or integration owner has provisioned a partner sandbox and named this participant-free test study: [TEST STUDY NAME OR ID]. Read only that study's safe title, purpose, and question structure with get_survey_study. Do not search or list the workspace, and do not read candidates, participants, screeners, responses, sessions, transcripts, recordings, highlights, insights, reels, or other workspace data. Propose two neutral study framings and show their exact questions. Then offer one short first-person proposition about my own preferred framing and wait for my acceptance before any proactive SomaCheck ask. Give the agent the Aligned or Unaligned result plus confidence as context and let it use that context with its judgment. Ask what I choose and accept any explicit response available in this interface. Keep the proposition, reading, confidence, and my confirmation out of Great Question. Return a signal-free, copy-ready research plan only. Do not create, update, delete, recruit, invite, message, schedule, incentivize, launch, publish, or otherwise write to Great Question. Do not ask me to sign up, upgrade, purchase, administer access, or populate Great Question data.",
         successCondition: "The researcher receives at most one optional signal, states a choice, and receives a copy-ready five-question plan; only get_survey_study reads the exact owner-supplied test artifact, Great Question remains unchanged, and no recruitment or participant data is accessed.",
     },
     {

package/dist/server.js

@@ -132,7 +132,7 @@ const SERVER_INSTRUCTIONS = [
     "SomaCheck lets you ask your person for a vibecheck.",
     "Offer one when useful or when asked.",
     "When asked, choose and send a useful first-person statement from available context.",
-    "Only request_vibecheck creates an immediate phone ask; post_vibecheck_statement stocks Settings → Vibe Checks, with one current on Home and the rest Up next.",
+    "Only request_vibecheck creates an immediate phone ask, one at a time; use post_vibecheck_statement only when the person asks to stock reflections for later.",
     "Gesture and optional feedback are context, not authorization.",
     "Never infer the SomaCheck identity from the agent login.",
     "Use your judgment.",
@@ -197,7 +197,7 @@ export function createVibecheckServer(dependencies) {
     });
     server.registerTool("get_vibecheck_status", {
         title: "Vibecheck Status",
-        description: "Read the live SomaCheck cache before posting. Reports how many personalized propositions are needed, when routine replenishment is due, and whether this is the agent's first contact.",
+        description: "Read the SomaCheck database feed before posting. Reports available proposition capacity, when routine replenishment is due, and whether this is the agent's first contact. Database state does not verify phone display.",
         inputSchema: {},
         outputSchema: statusSchema,
         annotations: {
@@ -255,7 +255,7 @@ export function createVibecheckServer(dependencies) {
     });
     server.registerTool("post_vibecheck_statement", {
         title: "Post Vibecheck Statement",
-        description: "Stock Settings → Vibe Checks with one to three optional personalized reflections and return immediately. One can become the current Home proposition; the rest stay Up next without extra pushes. Never call this to add follow-up asks after request_vibecheck. Call get_vibecheck_status first and submit exactly propositions_needed statements.",
+        description: "When the person asks to stock reflections for later, or has explicitly authorized scheduled stocking, add one to three optional personalized reflections under Settings → Vibe Checks and return immediately. One can become database-current for Home; the rest stay Up next without extra pushes. This does not verify phone display or delivery. Never call this to add follow-up asks after request_vibecheck. Call get_vibecheck_status first; propositions_needed is the available maximum, not a quota. Submit only genuinely useful statements and never invent extras to fill capacity. A still-active scheduled authorization does not require repeated consent each run.",
         inputSchema: {
             statements: z.array(z.string().min(1)).min(1).max(3)
                 .describe("Distinct personalized statements for this person to test, ordered most useful first."),
@@ -276,14 +276,14 @@ export function createVibecheckServer(dependencies) {
             return {
                 content: [{
                         type: "text",
-                        text: `Added ${created.length} under Settings → Vibe Checks: ${presented} current, ${queued} Up next. This is asynchronous feed inventory, not an immediate request.`,
+                        text: `Added ${created.length} under Settings → Vibe Checks: ${presented} database-current, ${queued} queued. This is asynchronous feed inventory, not verified phone display or an immediate request.`,
                     }],
                 structuredContent: { propositions: created },
             };
         }
         catch (error) {
             return failure(error instanceof StatementPendingError
-                ? "Three propositions are already available. Wait for a check-in, refresh, or expiry."
+                ? "The database feed cannot accept those propositions within its available capacity. Check status again after a check-in, refresh, or expiry."
                 : operationalFailureText("add SomaCheck propositions", error));
         }
     });
@@ -615,16 +615,19 @@ async function waitForLiveVibecheck(created, token, identity, dependencies, sign
 }
 function summarise(status) {
     const cadence = status.cadence;
+    if (status.propositions_needed <= 0) {
+        return `This connection's database feed has no available slots; ${status.queued_proposition_count} propositions are queued. Do not post another feed item. This status does not verify phone display. Routine replenishment uses a ${formatDuration(cadence.followup_within_seconds)} floor.`;
+    }
     if (status.first_run_intro.should_offer_now) {
-        return `This is your first contact. Introduce the SomaCheck ritual, then create exactly ${status.propositions_needed} distinct personalized propositions.`;
+        return `This is your first contact. Introduce the SomaCheck ritual. The feed has up to ${status.propositions_needed} available slot${status.propositions_needed === 1 ? "" : "s"}; only if the person asks to stock reflections for later or has explicitly authorized scheduled stocking, add 1 to ${status.propositions_needed} genuinely useful proposition${status.propositions_needed === 1 ? "" : "s"}. Never invent extras to fill capacity.`;
     }
     if (status.propositions_needed > 0) {
         const requested = status.replenishment_requested_at === null
             ? ""
             : ` The person requested replenishment at ${status.replenishment_requested_at}.`;
-        return `The cache has ${status.pending_proposition_count} of 3 propositions. Create exactly ${status.propositions_needed} distinct personalized proposition${status.propositions_needed === 1 ? "" : "s"} now.${requested}`;
+        return `The database feed has ${status.pending_proposition_count} of 3 propositions and up to ${status.propositions_needed} available slot${status.propositions_needed === 1 ? "" : "s"}. Only if the person asks to stock reflections for later or has explicitly authorized scheduled stocking, add 1 to ${status.propositions_needed} genuinely useful proposition${status.propositions_needed === 1 ? "" : "s"}; never invent extras to fill capacity. A still-active scheduled authorization does not require repeated consent each run. This status does not verify phone display.${requested}`;
     }
-    return `The cache is full: one proposition is presented and ${status.queued_proposition_count} are queued. Routine replenishment uses a ${formatDuration(cadence.followup_within_seconds)} floor.`;
+    return "Feed capacity is unavailable. Do not post another feed item until status can be confirmed.";
 }
 function formatDuration(seconds) {
     const hours = seconds / 3600;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@somacheck/vibecheck",
-  "version": "0.6.13",
+  "version": "0.6.14",
   "mcpName": "io.github.Sensie-agents/vibecheck",
   "description": "Body language for AI agents, on your terms. A consented SomaCheck signal for how a thought or choice lands.",
   "repository": {

package/recipes/chattermill-research-reflection.md

@@ -77,8 +77,8 @@ or `search_observations` (observation identifiers and representative verbatim
 snippets), and never surfaces individual feedback, source quotes, respondent
 identifiers, or free text. The agent offers two defensible interpretations of
 what the aggregate signal suggests, then one short first-person proposition
-about the researcher's own interpretation or next step. After the researcher's
-typed choice, the agent stops. There is no Chattermill write.
+about the researcher's own interpretation or next step. After the researcher
+explicitly indicates a choice, the agent stops. There is no Chattermill write.
 
 ## Starter prompt
 
@@ -98,7 +98,8 @@ aggregate signal suggests, with the tradeoff for each. Then offer one short
 first-person proposition about my own interpretation or next step and wait
 for my acceptance before any proactive SomaCheck ask. Treat Aligned or
 Unaligned plus confidence as context, not truth, diagnosis, authorization, or
-evidence about any individual customer. Ask what I choose in words. Keep the
+evidence about any individual customer. Ask what I choose and accept any
+explicit response available in this interface. Keep the
 proposition, reading, confidence, and my confirmation out of Chattermill. Do
 not write to Chattermill; the hosted MCP is read-only. If the preconfigured
 connection, mcp:read, or a safe aggregate tool is absent, return the copy-ready
@@ -198,9 +199,9 @@ recipe work. If the runtime does not expose `get_metrics` or
     researcher decides). `unaligned` may indicate possible inner conflict
     relative to the proposition; it does not name a cause, choose an
     interpretation, or justify a research claim.
-11. **Ask for words.** Ask the researcher which interpretation they choose,
-    whether they want a third option, or whether they want to stop. Follow
-    their typed choice.
+11. **Return authority.** Ask the researcher which interpretation they choose,
+    whether they want a third option, or whether they want to stop. Accept any
+    explicit response available in the interface and follow their choice.
 12. **Keep the signal out of Chattermill.** Do not call any write, mutation,
     export, tag, theme, highlight, insight, or analytics tool. Do not store
     the proposition, reading, confidence, confirmation, or gesture metadata
@@ -246,8 +247,8 @@ The test passes when:
 - the researcher receives at most one optional SomaCheck check-in on their
   phone on an exact first-person proposition about their own interpretation or
   next step;
-- the agent presents the result as context, asks the researcher to state their
-  choice in words, and follows the typed choice;
+- the agent presents the result as context, asks the researcher to indicate
+  their choice explicitly, and follows that choice;
 - the agent makes no Chattermill write, mutation, export, share, tag,
   comment, or analytics call; and
 - no individual customer, respondent, or employee data enters the cross-MCP
@@ -271,7 +272,7 @@ The test passes when:
   then proceed without a reading if still unresolved.
 - **Unreadable capture:** Offer a retry only if the researcher wants it;
   unreadable is not a third interpretation.
-- **Researcher disagrees with the reading:** Follow the researcher's typed
+- **Researcher disagrees with the reading:** Follow the researcher's explicit
   choice without reconciliation or repetition.
 
 ## Privacy boundary
@@ -306,7 +307,7 @@ The test passes when:
 - [ ] The proposition is first-person and contains no Chattermill content.
 - [ ] At most one SomaCheck request is created for the choice.
 - [ ] Observation, interpretation, confirmation, and choice remain separate.
-- [ ] The researcher states a choice in words and the agent follows the typed choice.
+- [ ] The researcher explicitly indicates a choice and the agent follows it.
 - [ ] The agent makes no Chattermill write, mutation, export, share, tag,
       comment, or analytics call.
 - [ ] No individual customer, respondent, or employee data enters the

package/recipes/dovetail-research-reflection.md

@@ -115,7 +115,7 @@ makes the reading an automatic write condition.
    `pending`, is `expired` or `cancelled`, or errors, continue without a result;
    do not infer one or start another request.
 8. **Return authority.** Offer the options to revise, investigate, proceed,
-   pause, or leave the artifact unchanged. A typed researcher choice overrides
+   pause, or leave the artifact unchanged. An explicit researcher choice overrides
    the signal.
 9. **Keep the signal private.** Do not write the verdict, confidence, gesture,
    or confirmation to Dovetail. If the researcher asks to record a next step,
@@ -153,7 +153,7 @@ Do not trigger when:
 - the task is ordinary Dovetail retrieval, summarization, tagging, or export;
 - the proposed subject is anyone other than the researcher;
 - the source contains raw or identifiable participant material;
-- the researcher has already made a clear typed choice;
+- the researcher has already made a clear choice;
 - the result would determine inclusion, quality, compensation, performance, or
   another consequential outcome; or
 - a vibecheck was already used for the same decision.

package/recipes/great-question-research-reflection.md

@@ -48,7 +48,8 @@ neutral study framings and show their exact questions. Then offer one short
 first-person proposition about my own preferred framing and wait for my
 acceptance before any proactive SomaCheck ask. Give the agent the Aligned or
 Unaligned result plus confidence as context and let it use that context with
-its judgment. Ask what I choose in words. Keep the proposition, reading,
+its judgment. Ask what I choose and accept any explicit response available in
+this interface. Keep the proposition, reading,
 confidence, and my confirmation out of Great Question. Return a signal-free,
 copy-ready research plan only. Do not create, update, delete, recruit, invite,
 message, schedule, incentivize, launch, publish, or otherwise write to Great
@@ -119,8 +120,8 @@ owner-supplied artifact.
    or Unaligned reading, and confidence. Let it combine that context with the
    conversation and its judgment. Keep observation, interpretation,
    confirmation, and choice distinct.
-9. **Ask the researcher to choose in words.** Their typed answer controls what
-   follows and may differ from the signal.
+9. **Return authority.** Ask the researcher to indicate their choice explicitly.
+   Their choice controls what follows and may differ from the signal.
 10. **Return a copy-ready plan.** Include only a test title, goal/purpose,
     language, and the five questions. Do not attach an incentive, consent form,
     screener, candidates, recruitment settings, or send settings.
@@ -169,7 +170,7 @@ The end-to-end test passes only when:
 - **SomaCheck unresolved:** Use the same handle once later, then proceed without
   a reading if unresolved.
 - **Unreadable capture:** Offer a retry only if the researcher wants it.
-- **The researcher's words differ from the reading:** Follow their typed choice
+- **The researcher's choice differs from the reading:** Follow their explicit choice
   without reconciliation or repetition.
 
 ## Privacy boundary

package/recipes/maze-research-reflection.md

@@ -73,7 +73,7 @@ summary (mission completion rates, time on task, success-rate aggregate,
 summary counts). It does not open transcripts, response rows, participant
 identifiers, recordings, or free-text fields. The agent offers two defensible
 interpretation framings and one short first-person proposition about the
-researcher's own interpretation plan. After the researcher's typed choice,
+researcher's own interpretation plan. After the researcher explicitly indicates a choice,
 the agent stops. There is no Maze write.
 
 ## Starter prompt
@@ -94,7 +94,8 @@ defensible interpretation framings. Then offer one short first-person
 proposition about my own interpretation plan and wait for my acceptance
 before any proactive SomaCheck ask. Treat Aligned or Unaligned plus
 confidence as context, not truth, diagnosis, authorization, or evidence
-about a Maze participant. Ask what I choose in words. Keep the
+about a Maze participant. Ask what I choose and accept any explicit response
+available in this interface. Keep the
 proposition, reading, confidence, and my confirmation out of Maze. Do
 not create, edit, publish, delete, archive, export, share, tag, comment,
 or write to Maze, a hidden field, a webhook, or any analytics record.
@@ -192,8 +193,8 @@ read, label the Maze half untested and stop.
     decides). `unaligned` may indicate possible inner conflict relative
     to the proposition; it does not name a cause, choose an interpretation,
     or justify a research claim.
-11. **Ask for words.** Ask the researcher which framing they choose, whether they
-    want a third option, or whether they want to stop. Follow their typed
+11. **Return authority.** Ask the researcher which framing they choose, whether they
+    want a third option, or whether they want to stop. Follow their explicit
     choice.
 12. **Keep the signal out of Maze.** Do not call any Maze write, mutation,
     export, webhook, comment, tag, highlight, insight, analytics, or
@@ -241,8 +242,8 @@ The test passes when:
   theme, highlight, insight, automation, or write tool;
 - the researcher receives at most one optional SomaCheck check-in on their phone
   on an exact first-person proposition about their own interpretation plan;
-- the agent presents the result as context, asks the researcher to state their
-  choice in words, and follows the typed choice;
+- the agent presents the result as context, asks the researcher to indicate
+  their choice explicitly, and follows that choice;
 - the agent makes no Maze write, mutation, export, share, tag,
   comment, or analytics call; and
 - no Maze participant, respondent, or employee data enters the
@@ -271,7 +272,7 @@ The test passes when:
   later, then proceed without a reading if still unresolved.
 - **Unreadable capture:** Offer a retry only if the researcher wants it;
   unreadable is not a third interpretation.
-- **Researcher disagrees with the reading:** Follow the researcher's typed choice
+- **Researcher disagrees with the reading:** Follow the researcher's explicit choice
   without reconciliation or repetition.
 
 ## Privacy boundary
@@ -308,8 +309,7 @@ The test passes when:
 - [ ] At most one SomaCheck request is created for the choice.
 - [ ] Observation, interpretation, confirmation, and choice remain
       separate.
-- [ ] The researcher states a choice in words and the agent follows the typed
-      choice.
+- [ ] The researcher explicitly indicates a choice and the agent follows it.
 - [ ] The agent makes no Maze mutation, write, export, share, tag,
       comment, or analytics call.
 - [ ] No Maze participant, respondent, or employee data enters the

package/recipes/prolific-research-reflection.md

@@ -124,7 +124,7 @@ automatic decision gate.
    proceed to separate review, pause, or leave unchanged. Do not call
    `create_filter_set`, `create_study`, or `publish_study`. If the researcher
    chooses a change, produce a reviewable draft outside Prolific; platform
-   mutation is a new action requiring explicit instruction. A typed researcher
+   mutation is a new action requiring explicit instruction. An explicit researcher
    choice overrides the signal.
 10. **Keep the signal private.** Do not write the verdict, confidence, gesture,
     confirmation, or inferred meaning to Prolific or another research platform.
@@ -161,7 +161,7 @@ Do not trigger when:
 - the proposed subject is a participant, employee, cohort, or respondent;
 - the result would affect eligibility, filtering, payment, bonus, rejection,
   submission quality, authenticity, or performance;
-- the researcher has already made a clear typed choice;
+- the researcher has already made a clear choice;
 - the agent is being asked to publish, gate, or automate a launch; or
 - a vibecheck was already used for the same decision.
 

package/recipes/questionpro-research-reflection.md

@@ -26,7 +26,8 @@ about a respondent, or a research decision. The researcher remains the authority
 
 The researcher supplies a participant-free survey goal. The agent drafts two
 four-question versions and may offer one SomaCheck check-in on the researcher's
-own preferred direction. The researcher then chooses in words. The output is a
+own preferred direction. The researcher then explicitly indicates a choice.
+The output is a
 signal-free survey definition for a QuestionPro owner to review. This recipe
 does not create, publish, distribute, or populate a survey.
 
@@ -43,7 +44,8 @@ upgrade, buy a plan, administer access, or populate QuestionPro data. Propose tw
 questionnaire framings and show the exact questions. Then offer one short
 first-person proposition about my own preferred direction and wait for my
 acceptance before any proactive SomaCheck ask. Give the result and confidence to
-the agent as context and let it use its judgment. Ask what I choose in words.
+the agent as context and let it use its judgment. Ask what I choose and accept
+any explicit response available in this interface.
 Keep the proposition, reading, confidence, and confirmation out of QuestionPro.
 Return a copy-ready, signal-free survey definition only. Do not create, edit,
 send, distribute, publish, recruit, launch, access responses, or spend anything.
@@ -77,7 +79,8 @@ send, distribute, publish, recruit, launch, access responses, or spend anything.
 6. Give the proposition, Aligned or Unaligned result, and confidence to the
    agent. Let the agent use its judgment in context without treating the result
    as authorization or a claim about respondents.
-7. Ask what the researcher chooses in words. Their choice controls the plan.
+7. Ask the researcher to indicate their choice explicitly. Their choice controls
+   the plan.
 8. Return a copy-ready payload with title, purpose, questions, answer choices,
    and optional logic. Exclude all SomaCheck data and platform identifiers.
 9. Stop before any QuestionPro data or action call. A partner owner may review

package/recipes/typeform-research-reflection.md

@@ -115,8 +115,8 @@ Typeform write or launch condition.
    `pending`, is `expired` or `cancelled`, or errors, continue without a result;
    do not infer one or start another request.
 8. **Return authority.** Offer revise, split a question, soften leading
-   wording, add an answer option, pilot, proceed, pause, or leave unchanged. A
-   typed researcher choice overrides the signal.
+   wording, add an answer option, pilot, proceed, pause, or leave unchanged. An
+   explicit researcher choice overrides the signal.
 9. **Keep the signal private.** Do not write the verdict, confidence, gesture,
    or confirmation to Typeform. If the researcher asks for a Typeform edit,
    show the exact signal-free edit first and call the Typeform write tool only
@@ -159,7 +159,7 @@ Do not trigger when:
   free-text answers;
 - the result would affect eligibility, payment, employment, grading, access,
   support priority, response quality, or survey validity;
-- the researcher has already made a clear typed choice;
+- the researcher has already made a clear choice;
 - the researcher has declined a recent offer or opted out; or
 - a vibecheck was already used for the same decision.
 

package/recipes/user-interviews-research-reflection.md

@@ -57,7 +57,8 @@ gates.
 
 The researcher gives the agent a participant-free study idea. The agent drafts
 two neutral framings, offers one first-person SomaCheck check-in about the
-researcher's own direction, and asks what they choose in words. The agent
+researcher's own direction, and accepts any explicit response available in the
+interface. The agent
 returns a complete copy-ready payload and stops. User Interviews remains
 unchanged. Any later draft creation is a separate future recipe and review, not
 an optional branch of this one.
@@ -79,7 +80,8 @@ Propose two neutral study framings and show the exact
 signal-free project copy. Then offer one short first-person proposition about
 my own preferred direction and ask for one SomaCheck check-in on that exact
 wording. Keep the proposition, reading, confidence, and my confirmation out of
-User Interviews. Afterward ask what I choose in words. Return the complete
+User Interviews. Afterward ask what I choose and accept any explicit response
+available in this interface. Return the complete
 signal-free, copy-ready project payload only. Do not create, edit, recruit,
 invite, message, schedule, screen, launch, publish, attach incentives, spend,
 read participant data, or call a broader or undocumented tool.
@@ -152,14 +154,14 @@ tools, stop without calling it.
 8. **Return authority.** Separate observation, interpretation (`aligned` or
    `unaligned` plus confidence), confirmation, and choice. `unaligned` may
    indicate possible inner conflict relative to the proposition; it does not
-   identify a cause or select a study design. The researcher's typed choice
+   identify a cause or select a study design. The researcher's explicit choice
    controls.
 9. **Prepare the exact payload.** Show title, purpose, study type, questions or
    tasks, and any required non-contact fields. Exclude the proposition, result,
    confidence, confirmation, SomaCheck wording, participant metadata, and
    hidden fields.
 10. **Stop before every platform call.** The SomaCheck reading and the
-    researcher's typed choice are not approval to use User Interviews. Do not
+    researcher's explicit choice are not approval to use User Interviews. Do not
     call create, update,
     read-back, recruitment, messaging, scheduling, participant, incentive,
     launch, publish, or data tools.
@@ -188,8 +190,8 @@ Not allowed:
 The test passes when:
 
 - the researcher receives at most one live SomaCheck request on their phone;
-- the agent presents the result as context and asks the researcher for their
-  typed choice;
+- the agent presents the result as context and asks the researcher to indicate
+  their choice explicitly;
 - the agent returns the exact signal-free, copy-ready project payload;
 - no User Interviews data or action tool is invoked and the workspace remains
   unchanged; and
@@ -212,7 +214,7 @@ The test passes when:
   proceed without a reading if unresolved.
 - **Unreadable capture:** Offer a retry only if the researcher wants it;
   unreadable is not a third interpretation.
-- **Researcher disagrees with the reading:** Follow the researcher's typed
+- **Researcher disagrees with the reading:** Follow the researcher's explicit
   choice without reconciliation or repetition.
 
 ## Privacy boundary