@wibeco/bridge 0.2.2 → 0.2.3

package/dist/{chunk-XMEA243L.js → chunk-QDJNDFHB.js}

@@ -295,8 +295,8 @@ async function shareProgressCommand(options, cwd = process.cwd()) {
   }
   const summary = options.summary?.trim() ?? "";
   const wordCount = summary.split(/\s+/).filter(Boolean).length;
-  if (wordCount < 8 || wordCount > 22 || summary.length > 500) {
-    throw new Error("Progress summary must contain 8\u201322 words.");
+  if (wordCount < 20 || wordCount > 55 || summary.length > 500) {
+    throw new Error("Progress summary must contain 20\u201355 words.");
   }
   const title = options.title?.trim();
   if (title && title.length > 120) {

package/dist/cli.js

@@ -6,7 +6,7 @@ import {
   setupCommand,
   shareProgressCommand,
   statusCommand
-} from "./chunk-XMEA243L.js";
+} from "./chunk-QDJNDFHB.js";
 import {
   runPresenceHeartbeat
 } from "./chunk-A7KGZ7NX.js";
@@ -21,7 +21,7 @@ Commands:
         Use --reauthorize only to replace a rejected or revoked device token.
   status
   emit --adapter <name> --event <hook-name>  (JSON payload on stdin)
-  share-progress --summary <8-22 words> [--title <title>] [--phase <phase>] [--confidence <0-1>]
+  share-progress --summary <20-55 words> [--title <title>] [--phase <phase>] [--confidence <0-1>]
   doctor [--repository <owner/repo>]`;
 async function main() {
   const [command, ...args] = process.argv.slice(2);

package/dist/codex-hook.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import {
   emitCommand
-} from "./chunk-XMEA243L.js";
+} from "./chunk-QDJNDFHB.js";
 import "./chunk-A7KGZ7NX.js";
 
 // src/codex-hook.ts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wibeco/bridge",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "description": "Privacy-first live activity bridge for Cursor, Claude Code, and Codex.",
   "repository": {
     "type": "git",

package/templates/cursor/README.md

@@ -7,6 +7,10 @@ The emit command always returns a valid empty JSON object to Cursor and fails op
 delivery can never block an agent tool call.
 Session hooks own a metadata-only heartbeat every 45 seconds and stop it at session end. Routine
 prompt, tool, shell, and MCP lifecycle hooks are never reclassified as presence.
+The always-applied activity rule normally publishes only a task plan and a richer completion
+summary through Wibe MCP. Material blockers and major direction changes on longer tasks are the
+only intermediate updates. `wibe share-progress` is the device-authenticated fallback when MCP is
+unavailable.
 
 Run `wibe setup` to authorize a revocable, project-scoped device token. Interactive credentials are
 stored in the operating-system keychain; hooks do not require repository secrets. The mapper drops

package/templates/cursor/wibe-activity.mdc.example

@@ -6,9 +6,9 @@ alwaysApply: true
 # Wibe activity
 
 - This repository is connected to Wibe project `${WIBE_PROJECT_ID}`.
-- After a plan is settled, share it with `wibe_share_plan` when that tool is available.
-- After a meaningful implementation, validation, blocker, or completion milestone, call `wibe_share_progress`.
-- Write one concrete 8–22 word sentence. Use present progressive for active work and past tense for completed work.
-- Mention validation or blockers when material. Never include prompts, source code, secrets, raw commands, praise, hype, or speculation.
-- Do not publish routine tool calls or repeated updates. Wait at least 90 seconds between progress updates unless reporting a blocker or completion.
+- For most tasks, publish only two updates: the settled plan and the completed outcome.
+- Share the plan with `wibe_share_plan` when available. Use `wibe_share_progress` at completion, or earlier only for a material blocker or a major direction change on work lasting over ten minutes.
+- Write one or two concrete sentences totaling 20–55 words. Explain the user-facing goal, what changed, and validation or blockers when material.
+- Use present progressive for active work and past tense for completed work. Never include prompts, source code, secrets, raw commands, routine tool calls, praise, hype, or speculation.
+- Do not repeat information already shared or publish separate updates for editing, testing, committing, or pushing.
 - If the Wibe MCP tools are unavailable, run `npx --yes --package @wibeco/bridge@latest wibe share-progress --summary "<summary>" --phase <planning|implementing|validating|blocked|shipped>`.