@wibeco/bridge 0.2.4 → 0.2.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/templates/cursor/wibe-activity.mdc.example +5 -6
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@wibeco/bridge",
3
- "version": "0.2.4",
3
+ "version": "0.2.5",
4
4
  "description": "Privacy-first live activity bridge for Cursor, Claude Code, and Codex.",
5
5
  "repository": {
6
6
  "type": "git",
package/templates/cursor/wibe-activity.mdc.example CHANGED
@@ -6,9 +6,8 @@ alwaysApply: true
6
6
  # Wibe activity
7
7
 
8
8
  - This repository is connected to Wibe project `${WIBE_PROJECT_ID}`.
9
- - For most tasks, publish only two updates: the settled plan and the completed outcome.
10
- - 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.
11
- - Write one or two concrete sentences totaling 20–55 words. Explain the user-facing goal, what changed, and validation or blockers when material.
12
- - 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.
13
- - Do not repeat information already shared or publish separate updates for editing, testing, committing, or pushing.
14
- - 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>`.
9
+ - For most tasks, publish one update only after the requested outcome is complete. Do not publish plans, routine progress, or separate updates for editing, testing, committing, or pushing.
10
+ - Use `wibe_share_progress` with phase `shipped` at completion. Publish earlier only with phase `blocked` when a material blocker leaves the task unfinished.
11
+ - Write one self-contained paragraph of 20–55 words in past tense. Lead with what now works, then explain the user or team impact and meaningful validation. Mention important limitations when present.
12
+ - Describe the outcome, not the agent’s process. Never include first-person narration, prompts, source code, secrets, raw commands, routine tool calls, filenames, line counts, praise, hype, or speculation; Wibe displays code and file changes separately.
13
+ - If the Wibe MCP tool is unavailable, run `npx --yes --package @wibeco/bridge@latest wibe share-progress --summary "<summary>" --phase <shipped|blocked>`.