replicas-cli 0.2.642 → 0.2.644

package/dist/index.cjs

@@ -24619,7 +24619,7 @@ var SENTRY_ABILITY = {
 
 // ../shared/src/slack-response-style.ts
 var SLACK_CONCISE_REPLY_SHAPE = "one to three plain sentences on what you did and what it means, with no headers, bullet lists, command logs, or step-by-step narration";
-var SLACK_BLOCK_KIT_GUIDANCE = "Use Block Kit whenever structure or a link would make the message faster to scan or use. You have broad leeway to combine supported display elements: `section` and `fields` for compact updates; `context` for secondary metadata; `header` and `divider` for genuinely distinct sections; images for useful previews; and `actions` with URL buttons for pull requests, dashboards, downloads, or next steps. Consult the [Slack Block Kit reference](https://docs.slack.dev/reference/block-kit/blocks) for exact schemas before using an unfamiliar block. Do not add selects, date pickers, approval buttons, or other controls that require an interaction callback. Keep simple replies as plain text, do not add decorative UI or repeat content across blocks, and always keep `text` as a concise, complete fallback for notifications and accessibility.";
+var SLACK_BLOCK_KIT_GUIDANCE = "Use Block Kit whenever structure or a link would make the message faster to scan or use. Before composing a structured message, read Slack's live [block catalog](https://docs.slack.dev/reference/block-kit/blocks) and the linked schema for each block you plan to use; do not rely on memory for which blocks exist or their fields. You have broad leeway to use display-only blocks and `actions` with URL buttons, but do not add controls that require an interaction callback. Keep simple replies as plain text, do not add decorative UI or repeat content across blocks, and always keep `text` as a concise, complete fallback for notifications and accessibility.";
 var SLACK_PR_BUTTON_GUIDANCE = 'The first time you share a given pull request or merge request link in a thread \u2014 the message announcing you opened it \u2014 attach a button for it: send `blocks` alongside `text` \u2014 a `section` block holding your message as `mrkdwn`, then an `actions` block with one element per newly shared link, `{"type": "button", "style": "primary", "text": {"type": "plain_text", "text": "View PR"}, "url": "<pr url>", "action_id": "view_pr"}`. Later messages about a pull request you already linked in this thread keep the link in the sentence and get no button, and never re-post a button for a link someone already has. Label it "View MR" for GitLab, and if there are several give each button a unique `action_id` and name its repository in the label ("View PR \xB7 web"). Always keep `text` populated with the same message \u2014 Slack uses it for notifications and fallback \u2014 and keep the link in the sentence too.';
 
 // ../shared/src/default-skills/replicas-agent/abilities/slack.ts
@@ -27242,7 +27242,7 @@ var headlessFilesystemAgentResultSchema = external_exports.object({
 });
 
 // ../shared/src/cli-version.ts
-var CLI_VERSION = "0.2.642";
+var CLI_VERSION = "0.2.644";
 
 // ../shared/src/version.ts
 function compareVersions(v1, v2) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "replicas-cli",
-  "version": "0.2.642",
+  "version": "0.2.644",
   "description": "CLI for managing Replicas workspaces - SSH into cloud dev environments with automatic port forwarding",
   "main": "dist/index.cjs",
   "bin": {