replicas-engine 0.1.679 → 0.1.681

package/dist/src/{chunk-6VS3OIXH.js → chunk-HWSR36NN.js}

@@ -366,7 +366,9 @@ var FALLBACK_AGENT_MODEL = {
   relay: DEFAULT_CLAUDE_MODEL
 };
 function getDefaultAgentModel(provider, overrides) {
-  return overrides?.[provider]?.[0] ?? FALLBACK_AGENT_MODEL[provider];
+  const fallback = FALLBACK_AGENT_MODEL[provider];
+  const options = getAgentModelOptions(provider, overrides);
+  return options.includes(fallback) ? fallback : options[0];
 }
 function normalizeClaudeModel(model) {
   if (model === "opus" || model === CLAUDE_OPUS_1M_MODEL || model === LEGACY_CLAUDE_OPUS_1M_MODEL) {
@@ -454,6 +456,10 @@ var AGENT_MODELS = {
   pi: [...OPENROUTER_MODELS, ...ASTER_MODELS],
   relay: [CLAUDE_FABLE_5_MODEL, CLAUDE_OPUS_5_MODEL, CLAUDE_OPUS_4_8_MODEL, CLAUDE_SONNET_5_MODEL]
 };
+function getAgentModelOptions(provider, overrides) {
+  const override = overrides?.[provider];
+  return override?.length ? override : AGENT_MODELS[provider];
+}
 var MODEL_LABELS = {
   fable: "Fable 5",
   [CLAUDE_FABLE_5_MODEL]: "Fable 5",
@@ -1621,6 +1627,8 @@ replicas computer record stop
 replicas media upload /tmp/demo.mp4 --name "Demo recording"
 \`\`\`
 
+For any external destination, continue with the required delivery flow in \`MEDIA.md\`.
+
 ## Command reference
 
 ### \`replicas computer info\`
@@ -1755,7 +1763,7 @@ replicas computer record start /tmp/walkthrough.mp4
 replicas computer record stop
 replicas media upload /tmp/walkthrough.mp4 --name "Walkthrough recording"
 \`\`\`
-Then embed the printed \`![\u2026](\u2026)\` line in your chat reply. See \`MEDIA.md\`.
+Then embed the printed \`![\u2026](\u2026)\` line in your chat reply and follow \`MEDIA.md\` for any external destination.
 
 ## Failure modes
 
@@ -1955,16 +1963,9 @@ gh pr review 123 --approve
 gh pr review 123 --request-changes --body "Changes needed"
 \`\`\`
 
-## Image Uploads in PRs
+## Media in GitHub workflows
 
-GitHub does NOT have a public API for uploading images to PRs/issues. When you need to include images:
-- Do NOT use placeholder image URLs
-- Do NOT commit screenshots as files to the repository
-- Run \`replicas media upload <image> --name "<display name>" --share\` and put the printed \`Forge embed\` Markdown in the PR body or comment
-- For a self-contained HTML report, run \`replicas media upload <page.html> --name "<display name>" --access organization\` and put the printed \`Forge link\` Markdown in the PR body or comment. Organization members who are already signed in open it directly; others sign in and return to the page
-- For video, embed a shared poster image linked to the recording's **View in Replicas** URL; GitHub does not reliably render externally hosted video inline
-- Treat the public URL as an opt-in bearer capability; revoke it with \`replicas media revoke <media-id>\` only when the user asks or the media should stop rendering \u2014 revoking breaks embeds already posted on the PR
-- If you were triggered from Slack, also upload the image to the Slack thread so the user can see it directly
+Media delivery is owned by \`references/MEDIA.md\`. Read its GitHub section before adding screenshots, recordings, diagrams, or HTML reports to a pull request, issue, review comment, or commit; it covers the Replicas upload, GitHub's inline fallback, and the required **View in Replicas** link.
 `;
 var GITHUB_ABILITY = {
   label: "GitHub",
@@ -2026,7 +2027,7 @@ await replicas.gitlab.request('/projects/group%2Frepo/pipelines', {
 
 ## Descriptions and media
 
-API updates replace the entire merge request description, so always preserve the required Replicas footer and co-author trailers. For media, first run \`replicas media upload\` as documented in \`MEDIA.md\`; use GitLab's project uploads endpoint only when a native repository-protected embed is required.
+API updates replace the entire merge request description, so always preserve the required Replicas footer and co-author trailers. Media delivery is owned by \`references/MEDIA.md\`; read its GitLab section before adding media so the original bytes are uploaded to Replicas and GitLab and the dashboard link remains secondary.
 `;
 var GITLAB_ABILITY = {
   label: "GitLab",
@@ -2091,6 +2092,8 @@ await replicas.linear.graphql({
 \`\`\`
 
 Search with \`containsIgnoreCase: $query\` filters, for example on both \`title\` and \`description\`. Batch independent queries with \`Promise.all\` to save round trips.
+
+For screenshots, recordings, diagrams, or other media, read \`references/MEDIA.md\` before adding it to an issue or comment. It is the single source of truth for uploading the Replicas copy and the raw file to Linear; a dashboard link alone is not an inline attachment.
 `;
 var LINEAR_ABILITY = {
   label: "Linear",
@@ -2102,18 +2105,19 @@ var LINEAR_ABILITY = {
 
 // ../shared/src/default-skills/replicas-agent/abilities/media.ts
 var SECTION6 = `### Media
-Share screenshots, screen recordings, generated diagrams, audio clips, and self-contained HTML pages through Replicas and external messages.
+Deliver screenshots, screen recordings, generated diagrams, audio clips, and self-contained HTML pages to the Replicas dashboard and, when applicable, inline in the destination workflow.
 
 **Reference:** \`references/MEDIA.md\`
 
 Use this when:
+- You are about to run \`replicas media upload\`; this reference owns the complete Replicas-first, destination-second workflow
 - You produce a screenshot, recording, generated image, or audio clip the user should see
 - You produce a self-contained HTML report that should be linked from a pull request
 - You record video output (browser automation, screen capture) \u2014 including the recommended aspect ratio and FPS
-- You need to embed media in a Slack/Linear/GitHub message AND keep a referenceable copy in the Replicas dashboard`;
+- You need to embed media in a Slack/Linear/GitHub/GitLab message AND keep a referenceable copy in the Replicas dashboard`;
 var REFERENCE6 = `# Media (Screenshots, Recordings, Audio, HTML)
 
-This guide covers how to share screenshots, screen recordings, generated diagrams, audio clips, and self-contained HTML pages through Replicas and external surfaces (Slack, Linear, GitHub).
+This is the single source of truth for delivering screenshots, screen recordings, generated diagrams, audio clips, and self-contained HTML pages through Replicas and external surfaces (Slack, Linear, GitHub, GitLab).
 
 ## Prerequisites
 
@@ -2123,12 +2127,32 @@ The \`replicas\` CLI is pre-installed and authenticated in your workspace. No ad
 
 Upload to Replicas in these cases \u2014 and **only** these cases:
 
-1. **Media you produce.** Any screenshot, screen recording, generated diagram, or audio clip you create that the user might want to see. Upload before doing anything else with the file (analyzing, deleting, sending elsewhere). This applies even when you're also sending the file to Slack, Linear, GitHub, etc.
+1. **Media you produce.** Any screenshot, screen recording, generated diagram, audio clip, or HTML page you create that the user might want to see. Upload before doing anything else with the file (analyzing, deleting, sending elsewhere). This applies even when you're also sending the file to Slack, Linear, GitHub, or GitLab.
 2. **Files the user explicitly asks you to upload.** If the user sends or points at a file (image, video, audio, HTML) and asks you to upload it, run \`replicas media upload\`. Otherwise leave it alone \u2014 files in the workspace the user did not ask about should not be auto-uploaded as media.
-3. **Anything you plan to share externally (Slack, Linear, GitHub, etc.).** Upload to Replicas *in addition to* the platform's native upload. Never as a replacement.
+3. **Anything you plan to share externally (Slack, Linear, GitHub, GitLab, etc.).** Upload to Replicas *in addition to* the platform's destination upload. Never as a replacement.
 
 If none of these apply, don't upload.
 
+## Required delivery contract
+
+\`replicas media upload\` is always the first delivery action. When the current task has an external destination, every other delivery step follows only after that command succeeds. For every file:
+
+1. First, run \`replicas media upload\` with the original file. Do not begin any destination upload until the command succeeds. This creates the canonical dashboard copy and prints the authenticated chat embed plus a per-file dashboard link.
+2. Include the printed embed line in the Replicas chat reply, followed by the matching **View in Replicas** link. HTML uses its printed page link instead of an image embed.
+3. Identify every destination in the task and attempt to upload the same original bytes there. Use the destination's inline representation from the table below; do not replace the file with a Replicas link.
+4. Put the **View in Replicas** dashboard link next to the destination embed as a secondary link.
+5. Check each destination response. If a native upload is unavailable or fails, say so explicitly and keep the dashboard link; never claim that a link is an inline upload.
+
+| Destination | Required file delivery | Inline result |
+|---|---|---|
+| Replicas dashboard/chat | \`replicas media upload\` | Printed \`![\u2026](\u2026)\` line in chat |
+| Slack | \`files.getUploadURLExternal\` \u2192 raw-byte POST \u2192 \`files.completeUploadExternal\` | Uploaded file in the channel or thread |
+| Linear | \`fileUpload\` mutation \u2192 presigned upload \u2192 issue/comment mutation | Returned \`assetUrl\` in Markdown |
+| GitLab | Project \`/uploads\` endpoint with the original bytes | Returned GitLab Markdown |
+| GitHub | No supported attachment API; use a Replicas public forge share for the inline image or video poster | Printed Forge embed, linked to the recording when needed |
+
+The dashboard link is the subtitle and jump-back path. It is never a substitute for the destination upload.
+
 ## Uploading to Replicas
 
 \`\`\`bash
@@ -2185,7 +2209,7 @@ replicas media upload screenshot.png --name "Login page" --access public
 | \`https://api.tryreplicas.com/v1/media/<id>\` (inside \`![\u2026](\u2026)\`) | Authenticated API redirect to a presigned blob \u2014 requires the Replicas chat session | **Only** in the Replicas chat reply. Nowhere else. |
 | \`https://tryreplicas.com/organizations/<organization-id>/media/<media-id>\` | Organization-only page printed by \`--access organization\` | Pull requests and other places where every viewer belongs to the Replicas organization. |
 | \`https://api.tryreplicas.com/v1/media/public/<id>/<token>\` | Opt-in public bearer URL printed by \`--access public\` or \`--share\` | GitHub embeds for image, video, or audio media. |
-| \`https://tryreplicas.com/workspaces/<workspace-id>?media=<media-id>\` | Authenticated dashboard deep link that opens the media file in the workspace | Everywhere external \u2014 Slack, GitHub, Linear, PR bodies, comments, emails. |
+| \`https://tryreplicas.com/workspaces/<workspace-id>?media=<media-id>\` | Authenticated dashboard deep link that opens the media file in the workspace | Everywhere external: Slack, GitHub, GitLab, Linear, PR bodies, comments, emails. |
 
 ### NEVER link the API redirect URL outside the Replicas chat reply
 
@@ -2195,6 +2219,7 @@ This rule has no exceptions:
 - \u274C Never paste it in a Slack message \u2014 upload the actual bytes via the 3-step \`files.getUploadURLExternal\` \u2192 POST bytes \u2192 \`files.completeUploadExternal\` flow instead (see below).
 - \u274C Never paste it in a GitHub PR description, issue body, review comment, or commit message.
 - \u274C Never paste it in a Linear issue body or comment \u2014 upload via Linear's \`fileUpload\` mutation instead (see below).
+- \u274C Never paste it in a GitLab merge request or issue; upload the original bytes through GitLab's project upload endpoint instead (see below).
 - \u274C Never link to it from any external doc, email, or external chat.
 - \u274C Never include it as a "backup link" in case the dashboard link breaks \u2014 it will always break externally.
 
@@ -2218,16 +2243,16 @@ Include each markdown embed line **verbatim** where you want that file to render
 
 After (or alongside) the embeds, include a \`[View in Replicas](<deep-link>)\` hyperlink for each file using the per-file dashboard URL from the CLI. This lets the user open the specific item in the workspace.
 
-## On external platforms \u2014 upload natively AND link the dashboard
+## On external platforms: embed the file AND link the dashboard
 
-Sharing media externally is a **two-step requirement** for every file:
+After \`replicas media upload\` succeeds, external delivery has two required follow-up steps for every file:
 
-1. **Upload the raw bytes natively to that platform** so the recipient sees the media embedded inline in the message itself.
+1. **Upload the raw bytes through that platform's supported inline path** so the recipient sees the media embedded in the message itself.
 2. **Link the Replicas dashboard deep link** (\`?media=<id>\` form) so the user can jump straight to the file in the workspace.
 
-A link alone is not enough. A native upload alone is not enough. Do both.
+A link alone is not enough. An upload without the dashboard link is not enough. Do both.
 
-GitHub has no native upload API, so use an explicit Replicas public share for screenshots and recording previews. GitLab has a native upload API and should receive the original bytes.
+Slack, Linear, and GitLab receive the original bytes through their native upload APIs. GitHub has no supported attachment API, so use an explicit Replicas public share for screenshots and recording previews.
 
 ### Slack \u2014 embed natively via the 3-step external file upload flow
 
@@ -2358,7 +2383,7 @@ GitHub does not reliably render arbitrary external videos as inline players. For
 [![Demo recording](<public-poster-url>)](<recording-dashboard-url>)
 \`\`\`
 
-Public forge shares are bearer capabilities. For private repositories, create one only when the user asked for inline PR media. Revoke with \`replicas media revoke <media-id>\` **only** when the user asks or the media should intentionally stop rendering \u2014 never as routine post-task cleanup, since revoking breaks every embed already posted on the PR.
+Public forge shares are unauthenticated bearer capabilities. For private repositories, create one only when the user explicitly asked for inline PR media. Without that consent, keep the media private in Replicas and report that GitHub has no supported attachment API; do not publish a bearer share or pretend the dashboard link is an embed. Revoke with \`replicas media revoke <media-id>\` **only** when the user asks or the media should intentionally stop rendering; never as routine post-task cleanup, since revoking breaks every embed already posted on the PR.
 
 For a self-contained HTML report, upload it with \`--access organization\` and put the printed \`Forge link\` Markdown in the PR body or comment. GitHub cannot render the page inline, so use the normal link rather than image syntax. HTML pages cannot be shared publicly.
 
@@ -2366,7 +2391,7 @@ Do **not** commit screenshots to the repo, use placeholder URLs, expose the auth
 
 ### GitLab: native inline screenshots and videos
 
-GitLab supports native project Markdown uploads. Always upload the media to Replicas first, then POST the same original file to the repository's \`/projects/:id/uploads\` API using the workspace GitLab credential. Insert the returned \`markdown\` value into the merge request body or comment and include the Replicas dashboard link. Image uploads render inline; MP4, MOV, and WebM uploads render as inline video players.
+GitLab supports native project Markdown uploads. For a GitLab destination, always upload the media to Replicas first, then POST the same original file to the repository's \`/projects/:id/uploads\` API using the workspace GitLab credential. Insert the returned \`markdown\` value into the merge request body or comment and include the Replicas dashboard link. Image uploads render inline; MP4, MOV, and WebM uploads render as inline video players.
 
 Do not use a Replicas public forge share for GitLab when the native project upload succeeds; native uploads preserve project access controls.
 
@@ -2415,7 +2440,7 @@ replicas media upload chart-a.svg chart-b.svg --name "Latency chart" --name "Err
 `;
 var MEDIA_ABILITY = {
   label: "Media",
-  description: "Share screenshots, recordings, generated images, audio clips, and HTML pages.",
+  description: "Deliver media to Replicas and destination workflows with inline uploads.",
   bullet: "- Producing or showing the user any media \u2014 screenshots, screen recordings, generated images or diagrams, audio clips, or HTML recap pages \u2014 including in your Replicas chat reply, PR descriptions/comments, and other external platforms",
   section: SECTION6,
   referenceFile: { name: "MEDIA.md", content: REFERENCE6 }
@@ -2697,7 +2722,7 @@ In agent mode the CLI hides commands that don't make sense for in-workspace agen
 | \`replicas automation ...\` | Manage automations (cron + GitHub/GitLab event triggers) |
 | \`replicas preview ...\` | Register / list preview URLs (covered in \`PREVIEWS.md\`) |
 | \`replicas service ...\` | Run long-lived services detached so they survive workspace sleep/wake (see below) |
-| \`replicas media ...\` | Upload screenshots, videos, audio (covered in \`MEDIA.md\`) |
+| \`replicas media ...\` | Upload media to the dashboard and follow \`MEDIA.md\` for destination embedding |
 | \`replicas slack thread ...\` | Attach or switch Slack thread routing (covered in \`SLACK.md\`) |
 
 \`replicas <command> --help\` is always the source of truth for flags.
@@ -2991,6 +3016,8 @@ await replicas.slack.call('chat.postMessage', {
 
 Only the announcing message gets the button \u2014 follow-ups about a pull request already linked in the thread keep the link in the text and drop the \`blocks\`. Use "View MR" for GitLab. With several links, give each button a unique \`action_id\` and name its repository in the label ("View PR \xB7 web").
 
+For screenshots, recordings, diagrams, or other media, read \`references/MEDIA.md\` before posting. It is the single source of truth for uploading the Replicas copy and the raw file to Slack; a dashboard link in \`text\` is not an inline attachment.
+
 Attach every new top-level conversation so future replies route to this workspace. For a reply in another thread, attach its root \`thread_ts\`, not the reply timestamp. Do not attach the originating thread again.
 
 ## Search and batch
@@ -6677,7 +6704,7 @@ var DEFAULT_CODEX_ARGS = [
 var MIN_CODEX_CLI_VERSION = "0.144.6";
 var CODEX_UPGRADE_TIMEOUT_MS = 12e4;
 var codexCliVersionEnsured = null;
-var ENGINE_PACKAGE_VERSION = "0.1.679";
+var ENGINE_PACKAGE_VERSION = "0.1.681";
 var INITIALIZE_METHOD = "initialize";
 var INITIALIZED_NOTIFICATION = "initialized";
 var ACCOUNT_LOGIN_START_METHOD = "account/login/start";

package/dist/src/headless-agent.js

@@ -7,7 +7,7 @@ import {
   headlessAgentRequestSchema,
   putPresignedFile,
   recoverCompletedTurn
-} from "./chunk-6VS3OIXH.js";
+} from "./chunk-HWSR36NN.js";
 
 // src/headless-agent.ts
 import { createHash } from "crypto";

package/dist/src/index.js

@@ -190,7 +190,7 @@ import {
   serializeCanvasContentResponse,
   shellQuotePosix,
   stripAgentDiagnosticErrors
-} from "./chunk-6VS3OIXH.js";
+} from "./chunk-HWSR36NN.js";
 
 // src/index.ts
 import { serve } from "@hono/node-server";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "replicas-engine",
-  "version": "0.1.679",
+  "version": "0.1.681",
   "description": "Lightweight API server for Replicas workspaces",
   "type": "module",
   "main": "dist/src/index.js",