6314 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
core-devops	862a90a316	fix(runtime): complete crewai/deepagents/gemini-cli removal + fail-closed on unresolvable runtime ... Addresses core-security REQUEST-CHANGES (review 4269) on PR #1385 (RFC internal#483). The original removal was incomplete and silently changed behavior: 1. manifest.json workspace_templates still listed crewai/deepagents/ gemini-cli. handlers.knownRuntimes (the workspace-create admission allowlist) is built at boot from manifest.json via runtime_registry.go — NOT from provisioner.knownRuntimes — so a create request for a "removed" runtime was still admitted. Removed the 3 entries; the manifest now resolves to the 6 kept template-backed runtimes (claude-code, hermes, openclaw, codex, langgraph, autogen) + injected meta-runtimes. langgraph/autogen retained intentionally — not in the internal#483 removal set and still in provisioner.knownRuntimes. 2. selectImage silently fell back to DefaultImage (langgraph) for any named-but-unresolvable runtime: a user asking for crewai got a langgraph container with no signal. selectImage now returns (string, error) and rejects a NAMED-but-unresolvable runtime with ErrUnresolvableRuntime (naming the offending runtime). Start propagates it; the existing markProvisionFailed path already broadcasts WorkspaceProvisionFailed + records the message. Implements the CTO hardgate directive (feedback_platform_must_hardgate_base_contract — fail-closed, no silent degrade). The genuinely-unspecified (empty) runtime remains a distinct legitimate path → DefaultImage. go build ./... and go test ./internal/provisioner/ ./internal/handlers/ ./internal/imagewatch/ ./internal/registry/ ./internal/models/ all pass. selectImage tests updated to assert the new fail-closed contract (new expected values verified against the security finding, not made-green). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-16 15:36:16 -07:00
core-devops	e809a2e319	chore(runtime): remove crewai/deepagents/gemini-cli from the runtime catalog ... CTO-approved scope-narrowing to the four maintained runtimes (claude-code, openclaw, hermes, codex) plus autogen/langgraph legacy. RFC molecule-ai/internal#483. - provisioner/registry.go: drop the 3 from knownRuntimes (kept alphabetical ordering; count pin updated 9 -> 6 in registry_test.go). - handlers/admin_workspace_images.go: drop the 3 from AllRuntimes so imagewatch stops pulling now-removed template images. - models/runtime_defaults.go: doc-comment list updated; drop the 3 explicit drift-detection rows from runtime_defaults_test.go. - localbuild_test.go RepoNotFound fixture switched crewai -> hermes (post-removal crewai is no longer a known runtime, so the test would hit the "unknown runtime" branch instead of the intended 404 path). - provisioner_test.go error-classification fixture string crewai -> hermes (no removed-runtime names in fixtures). Live-workspace safety gate cleared first: zero workspaces on the 3 runtimes across the production fleet (per-tenant DB query on hongming/go-to-market/chloe-dong + CP tenant_resources provisioning ledger covering reno-stars). Registry/pin row removal handled by a separate controlplane migration PR, landed after this merges. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-16 15:17:26 -07:00
devops-engineer	ec664869b0	Merge pull request 'fix(inbox): drop self-delegation-echo rows from inbox poller' (#1348) from fix/inbox-self-echo into main	2026-05-16 21:09:20 +00:00
devops-engineer	8b11368656	ci: rerun CI on healthy host (load-era timing flake, no code change) ... PR#1348 (#190 self-echo fix) sole red = test_batch_fetcher_runs_submitted_rows_concurrently in tests/test_inbox_uploads.py (2.6ms wall-clock overshoot, 0.2516s vs 0.25s) — a load-induced timing flake, NOT in this PR's changed code (workspace/inbox.py _is_self_echo_row). Host has recovered (load1 ~1.5, runner pool drained, throttle PR#72 live). Empty commit = the only CI-rerun mechanism on Gitea 1.22.6 (reference_empty_commit_is_only_rerun_mechanism_on_1_22_6). Same tree, no code change; CTO non-author-review waiver + mandatory retroactive core-security review apply to the new head unchanged. internal#469 / #190. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-16 14:00:07 -07:00
core-be	6bfc1c83ea	Merge origin/main into fix/inbox-self-echo (bring up to base, zero-conflict; #190 internal#469)	2026-05-16 12:53:09 -07:00
devops-engineer	2cb52615b0	Merge pull request 'infra(ci): route publish/deploy ship jobs to dedicated publish lane (internal#462)' (#1376) from infra/internal-462-publish-deploy-lane into main	2026-05-16 19:47:21 +00:00
infra-sre	16957b7c15	infra(ci): route publish/deploy ship jobs to dedicated publish lane (internal#462) ... Urgent prod-deploy publish builds currently FIFO-compete with ordinary PR required-CI on the shared 20-runner pool. PR#1350's (CTO-reported canvas-message-loss fix) production image build sat ~25min behind the PR-CI backlog after merge, directly delaying a user-facing fix. internal#462 comment 32299 + the already-merged operator-config publish-lane scaffolding (config.publish.yaml + publish-lane-ensure.sh, internal#394/#399) define a reserved `publish`/`release` sub-pool (molecule-runner-publish-*, OUTSIDE the managed 1..20 range so it is never auto-drained / recycled / drift-flagged). This retargets the 7 post-merge ship jobs across 5 workflows from `runs-on: ubuntu-latest` to `runs-on: publish` so a merged fix's image build/push/deploy gets reserved capacity and starts immediately, while PR-CI keeps the general pool: - publish-workspace-server-image.yml: build-and-push, deploy-production - publish-canvas-image.yml: build-and-push - publish-runtime.yml: publish, cascade - redeploy-tenants-on-main.yml: redeploy - redeploy-tenants-on-staging.yml: redeploy publish-runtime-autobump.yml is intentionally NOT moved: it is pull_request-triggered (PR-CI by nature, a required status), not a post-merge ship job — the lane reserves capacity for the ship path, not for PR checks. HARD MERGE PRECONDITION: this MUST NOT merge until the publish-lane runners are registered and advertising the `publish` label. Targeting an unregistered label queues jobs indefinitely with zero eligible runners — the exact #599/#576 `docker`-label failure mode. Lane registration is a GO-gated live-fleet mutation (publish-lane-ensure.sh ALLOW_FLEET_MUTATION=1, requires explicit Hongming in-chat GO). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-16 11:49:10 -07:00
Molecule AI Core-BE	1549a9a2fd	ci: rerun — runner-host ENOSPC infra failure on af25019 (no code change) ... Run 57610 Canvas(Next.js)+Platform(Go) failed solely on runner-host disk exhaustion (ENOSPC / 'no space left on device' in /tmp/go-build* and node write). PR#1348 touches only Python (workspace/inbox.py + .gitea sop-checklist); zero Go/TSX. main HEAD is green on both jobs. Disk since reclaimed (74%/58G free). Empty commit = only Gitea 1.22.6 rerun mechanism. Tree unchanged from af25019.	2026-05-16 11:44:20 -07:00
devops-engineer	6cfe76b6dd	Merge pull request 'fix(workspace-server): persist poll-mode canvas user message synchronously before queued 200 (internal#471, sibling of #1347)' (#1350) from fix/canvas-user-message-poll-mode-sync-persist into main	2026-05-16 15:49:25 +00:00
Molecule AI Core-BE	1d29e9ea24	fix(handlers): prevent poll-mode sync-persist test from hanging CI ... sqlmock.ExpectationsWereMet() hangs indefinitely when the expected INSERT mock never fires. If the production code ever regresses to goAsync (pre-fix shape), the handler returns before the INSERT fires, the mock never fires, and ExpectationsWereMet() blocks for the full test/-suite timeout — wedging the CI run with no diagnostic. Fix: check expectations in a goroutine with a 2s hard timeout. When the mock has fired (synchronous production code), ExpectationsWereMet() returns <1ms and the select fires the `case err := <-expectDone` arm. When the mock has NOT fired (async regression), the 2s timeout fires and the test fails with a clear message instead of hanging. Also reduce insertDelay from 150ms → 50ms. 50ms is ~50× the normal INSERT latency and sufficient to prove synchronous blocking; the larger value was adding unnecessary suite-level wall-clock under -race detection, where mock delays are amplified by the instrumenter's goroutine overhead. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-16 14:47:07 +00:00
Molecule AI Core-BE	af25019900	fix(inbox): add delegate_result exclusion to _is_self_echo_row ... RFC #2829 PR-2 regression fix: rows with method="delegate_result" are now excluded from the self-echo guard even when source_id matches our workspace_id. The platform may write a delegation-result row with our workspace_id as source_id (e.g. a self-delegation or edge case in the platform's result-writing path); such rows must reach the inbox so the runtime receives the delegation result. Fixes regression vs PR #1346 where this guard was present. Added test_is_self_echo_row_false_for_delegate_result regression pin. All 9 self-echo tests pass locally. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-16 13:31:30 +00:00
core-be	a92beb5d49	fix(workspace-server): persist poll-mode canvas user message synchronously before queued 200 ... Sibling of #1347/internal#470 — the POLL-mode arm of the canvas user-message data-loss bug Hongming reported ("i sometimes lose my own message when i exit chat", 2026-05-16). Hongming's tenant is entirely poll-mode (4 external workspaces, no URL — verified empirically: every workspace returns the {delivery_mode:poll, status:queued} short-circuit envelope), so #1347 (push-mode only, persists AFTER the poll short-circuit) structurally cannot cover his reported case. #1347's "poll-mode was never affected" framing is overstated: logA2AReceiveQueued's durable activity_logs INSERT ran inside h.goAsync(...) — a detached goroutine with no happens-before barrier against the synthetic {status:queued} 200. The canvas sees the send acknowledged while the row may still be racing; a workspace-server restart / deploy / OOM / EC2 hibernation between the 200 and the goroutine's commit loses the message permanently (chat-history reads activity_logs; missing row = message gone on reopen). No fallback either, unlike push-mode's legacy-INSERT path. Fix: make the poll-mode ingest persist SYNCHRONOUS — committed before the queued 200 — on a context.WithoutCancel context (parity with persistUserMessageAtIngest). Best-effort preserved (LogActivity logs+swallows INSERT errors, never blocks the send). Post-commit broadcast still fires inside LogActivity (a missed WS event is not data loss; the durable row is the truth chat-history re-reads on reopen). TDD: a2a_poll_ingest_persist_test.go — deterministic RED (queued 200 returned in ~0.5ms, before the 150ms INSERT → DATA LOSS) → GREEN after fix. Full internal/handlers + internal/messagestore suites green; vet clean. Refs: molecule-ai/internal#471 (tracking), molecule-ai/internal#470 (push-mode sibling, PR #1347) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-16 06:04:14 -07:00
devops-engineer	8e754e6b28	Merge pull request 'fix(workspace-server): inject /configs token files agent-owned, not root (P0 list_peers 401)' (#1327) from fix/workspace-token-injection-agent-owned into main	2026-05-16 12:51:57 +00:00
Molecule AI Core-BE	deeff950be	fix(inbox): drop self-delegation-echo rows from inbox poller ... Internal #469: when a workspace delegates to a target that never picks up the task, tool_delegate_task calls report_activity("a2a_receive", ...) which POSTs to the platform with source_id = the sender's workspace UUID (spoof- defense). The activity API exposes that row under type=a2a_receive, so the inbox poller re-fetches it and message_from_activity sets peer_id = the workspace's own UUID — the workspace sees its own delegation-failure echoed back as if a peer had delegated to it. Fix adds _is_self_echo_row(row, workspace_id) that returns True when source_id == workspace_id, mirroring the existing _is_self_notify_row pattern. The guard is wired into _poll_once after the self-notify check: self-echo rows are skipped from the queue, the cursor still advances, and the notification callback does not fire. The real delegate_result push path (delegate_result method) is unaffected. 8 new tests cover the predicate (same-workspace, different-workspace, None source, empty workspace_id, absent key) and the integrated poller behavior (skipped from queue, cursor advances, no notification). Live-repro confirmed on hongming.moleculesai.app prior to this fix. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-16 12:38:55 +00:00
devops-engineer	8179ff77e9	Merge branch 'main' into fix/workspace-token-injection-agent-owned	2026-05-16 12:05:32 +00:00
Molecule AI Infra-Runtime-BE	6188c6ddf3	fix(org_helpers): correct duplicate phrase in loadWorkspaceEnv comment ... The comment had the phrase "the workspace-specific .env" duplicated. Removed the redundant repetition. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-16 10:27:13 +00:00
Molecule AI Infra-SRE	50de2f6155	chore: re-trigger CI (infra-sre 09:47Z)	2026-05-16 09:47:45 +00:00
Molecule AI Core Platform Lead	3461b86cba	fix(sop-checklist): post na-declarations status for review-check.sh	2026-05-16 09:39:27 +00:00
hongming	85c627c86f	Merge pull request 'chore: promote staging→main (chat E2E + accumulated fixes)' (#1242) from promote/staging-to-main into main	2026-05-16 09:20:35 +00:00
core-be	f986444dbd	fix(workspace-server): inject /configs token files agent-owned, not root ... The fleet-wide list_peers 401 (Hermes et al): two workspace-server token-injection paths wrote /configs/.auth_token (and /configs/.platform_inbound_secret) as root:root 0600 AFTER the template entrypoint's `chown -R agent:agent /configs` ran. The a2a_mcp_server runs as the agent uid (1000, via `gosu agent`), so platform_auth.get_token() hit `[Errno 13] Permission denied` → empty bearer → platform 401 on /registry/{id}/peers (the literal tool_list_peers path). PR#23 fixed only the entrypoint dir chown (first boot); it cannot reach the post-entrypoint root re-injection. This covers both injection paths: 1. WriteAuthTokenToVolume (#1877, pre-start): the throwaway alpine container ran chmod 0600 but never chowned — alpine runs as root, so the file stayed root:root. Now `chown 1000:1000 /vol/.auth_token` (0600 preserved). 2. WriteFilesToContainer (#418, post-start re-injection): the tar headers left Uid/Gid unset → CopyToContainer extracted root:root. Now every tar entry is stamped Uid/Gid = agent. This path (re)writes BOTH .auth_token and .platform_inbound_secret, so both are fixed. uid 1000:1000 verified from the templates (claude-code-default + hermes Dockerfile `useradd -u 1000 ... agent`, entrypoint `gosu agent`), exposed as AgentUID/AgentGID constants. Tar-build and alpine-cmd extracted into pure helpers (mirrors buildTemplateTar) so the ownership contract is unit-tested without a live Docker daemon; the test fails on pre-fix root:root and passes post-fix (real tar / real command, not a mock). PR#23's entrypoint chown is unchanged (still correct for the dir + first boot). No feature flag, no backwards-compat shim. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-16 02:19:11 -07:00
fullstack-engineer	aef45b83a6	Merge main into promote/staging-to-main to resolve outdated branch	2026-05-16 01:17:18 -07:00
devops-engineer	43a77ccfbc	Merge pull request 'test(e2e): gate fresh-provision peer-visibility via literal MCP list_peers' (#1298) from e2e/peer-visibility-mcp-gate-v2 into main	2026-05-16 07:32:27 +00:00
core-devops	c7eeec1607	ci: re-trigger (prior run infra-failed: act_runner<->Gitea API read-timeout storm starved all-required aggregator + go test -race 10m budget blown on contended runner; PR touches zero Go) [no-op]	2026-05-16 06:58:48 +00:00
core-devops	2e8603f940	test(e2e): gate fresh-provision peer-visibility via the literal MCP list_peers call ... Hermes and OpenClaw were reported "fleet-verified / cascade-complete" off proxy signals (registry registration + heartbeat; model round-trip 200) while a freshly-provisioned workspace asked "can you see your peers" on canvas actually FAILS (Hermes: 401 on the molecule MCP list_peers call; OpenClaw: native sessions_list fallback, no platform peers). Tasks #142/#159 were even marked "completed" under this proxy-verification flaw. This adds a dedicated staging-E2E gate that codifies the LITERAL user-facing path so it can never silently regress: - New e2e-peer-visibility.yml + tests/e2e/test_peer_visibility_mcp_staging.sh. - Provisions a brand-new throwaway org via the real CP provisioning path + one sibling workspace per runtime under test (hermes, openclaw, claude-code) under a shared parent. - For each runtime, drives the byte-for-byte JSON-RPC tools/call name=list_peers envelope to POST /workspaces/:id/mcp using that workspace's OWN bearer token, through the real WorkspaceAuth + MCPRateLimiter chain. NOT a proxy: not GET /registry/:id/peers, not /health, not the heartbeat table. - Asserts HTTP 200 + JSON-RPC result (not error) + the returned peer set literally contains the other provisioned sibling IDs (not empty, not a native-sessions fallback). - Scoped teardown only of the e2e-pv-<run_id> org this run created (script EXIT trap + workflow always() net + sweep-stale-e2e-orgs as the final 'e2e-' prefix net) — never a cluster-wide cleanup. Honest gate, NO continue-on-error: it is RED on today's broken behavior by design and goes green only when the in-flight Hermes-401 + OpenClaw-MCP-wiring root-cause fixes actually land. Landed NON-required (not in branch_protections) so it does not wedge unrelated merges while red; flip-to-required checklist tracked in molecule-core#1296. Gitea-1.22.6 / act_runner hardening honored: mirrored actions/checkout SHA (the one e2e-staging-canvas.yml uses successfully), per-SHA concurrency, workflow-level GITHUB_SERVER_URL, no cross-repo uses. Passes lint-workflow-yaml, lint-continue-on-error-tracking, lint-required-no-paths locally. Refs: molecule-core#1296 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-15 23:08:56 -07:00
fullstack-engineer	a3f3ac361e	fix(e2e-chat): set CORS_ORIGINS for dynamic canvas port in CI	2026-05-15 22:12:57 -07:00
fullstack-engineer	48a1a604ac	chore: retrigger CI after operator maintenance and auto-heal race condition	2026-05-15 21:42:20 -07:00
fullstack-engineer	97cb104667	chore: retrigger CI after fixing runner-queue-janitor per-workflow supersession bug	2026-05-15 20:35:10 -07:00
fullstack-engineer	6c72aee1d9	chore: retrigger CI after system mass cancellation event	2026-05-15 20:28:15 -07:00
fullstack-engineer	873b522f10	chore: retrigger CI after mass cancellation ... All workflows for PR #1242 were simultaneously cancelled around 2026-05-16T00:02Z. Canvas, Python Lint, Shellcheck, and Detect changes had already succeeded; Platform Go and all-required were in-flight. Empty commit to re-queue the full check suite.	2026-05-15 18:28:27 -07:00
fullstack-engineer	ab99ea54ad	fix(e2e-chat): dynamic canvas port to avoid conflict with Gitea :3000 ... The operator host runs Gitea on 127.0.0.1:3000. With act_runner using container.network: host, the E2E Chat job's Next.js dev server (also port 3000) collides and crashes with EADDRINUSE. Changes: - Pick an ephemeral host port for the canvas dev server (same pattern already used for the platform port). - Pass the port to next dev via -p flag (overrides package.json -p 3000). - Update the health-check loop to probe the dynamic port. - Export PLAYWRIGHT_BASE_URL so Playwright tests connect to the right URL. - Make playwright.config.ts read baseURL from PLAYWRIGHT_BASE_URL env var with fallback to localhost:3000 (preserves local dev workflow). This is an infrastructure compatibility fix, not a test logic change.	2026-05-15 17:14:40 -07:00
fullstack-engineer	e21898f7a5	fix(ci): restore main-style all-required sentinel ... During staging→main merge conflict resolution the all-required job accidentally inherited staging's + + shape while keeping main's Python polling script. This creates a broken hybrid: the job is killed after 1 minute before the 40-minute polling deadline, and + re-introduces the Gitea 1.22 skipped-sentinel bug that main deliberately avoids. Restore main's proven shape: no , no , , Python polling. Per core-devops review on PR #1242.	2026-05-15 16:23:06 -07:00
fullstack-engineer	b5c8b235ab	fix(e2e-chat): correct actions/setup-node SHA ... The pinned SHA 60edb5dd...d6f5 was invalid (typo in last 4 chars). act_runner failed to resolve it with 'reference not found' after ~14s, causing the E2E Chat job to fail before any test step could run. Switch to the v6.4.0 SHA (48b55a01...4041e) already verified in ci.yml and e2e-staging-canvas.yml. mc#774 tracker: this was a pre-existing failure mode, not introduced by PR #1142 / promotion #1242.	2026-05-15 16:16:09 -07:00
fullstack-engineer	896c680eb4	chore: retrigger CI after adding Paired reference to PR body	2026-05-15 15:39:37 -07:00
devops-engineer	2045388293	fix(canvas): skip config.yaml write for openclaw + bump request timeout to 35s (promote #1237 to main) (#1241) ... Direct-to-main promote of #1237 (URGENT FIX, user GO). Approved by core-devops (review #3876, DB-promoted from PENDING). All required gates green: CI / all-required = success, sop-checklist / all-items-acked = success. All CI jobs green (incl. Platform (Go), Canvas (Next.js)). Triggers publish-canvas-image.yml + publish-workspace-server-image.yml on main → ECR :staging-<sha> → tenant fleet redeploy. Refs: #1237 (staging merge 6a082197), internal#418, follow-up internal#423	2026-05-15 22:27:51 +00:00
fullstack-engineer	0e13a80121	chore: promote staging→main (chat E2E + accumulated fixes) ... Promotes the following staging-only changes to main: - feat(e2e): stabilize Playwright chat tests for desktop + mobile (PR #1142) - feat(workspace): broadcast and talk-to-user platform abilities - feat(adapter-base): ProviderRegistry type + resolve_provider_routing - fix(staging): OFFSEC-010 CP config wiring + CWE-78 rows.Err fixes - fix(staging): restore goAsync tracking in dispatch calls - fix(ci): needs-based all-required sentinel - fix(canvas): load chat history in MobileChat (closes #1062) Merge-conflict resolutions: - ThemeToggle.tsx: take staging (INDEX_SIZE_ERR test fix) - MobileChat.tsx + test: take staging (shared hooks refactor) - workspace_broadcast.go: take main (OFFSEC-015 org isolation) - org_helpers.go + tests: combine both (CWE-78 guard + rows.Err) - secrets.go: take staging (descriptive rows.Err log messages) - workspace.go: combine (goAsync tracking + SaaS tier hard-gate) - cp_provisioner.go: combine (OFFSEC-010 comments + main formatting) - ci.yml: combine (mc#774 trackers + all-required needs cleanup) - test_a2a_offsec003_sanitization.py: delete (redundant per mc#62d38667)	2026-05-15 15:20:52 -07:00
devops-engineer	a118c63cd9	fix(canvas): skip config.yaml write for openclaw + bump request timeout to 35s (#1237) ... Direct merge per user GO (URGENT FIX implementation). Approved by core-devops (review #3869, DB-promoted from PENDING per Gitea 1.22.6 bug). Required gates: CI / all-required = success, sop-checklist / all-items-acked = success. Non-required Platform (Go) failure (pre-existing TestProxyA2A_Upstream502_*) unrelated to canvas-only diff. Refs: internal#418, follow-up internal#423	2026-05-15 15:05:49 -07:00
core-devops	843092db7d	feat(e2e): stabilize Playwright chat tests for desktop + mobile ... Comprehensive Playwright E2E coverage for the unified chat stack. - chat-seed.ts: external workspace creation with psql bypass for loopback URLs, heartbeat keeper, platform_inbound_secret pre-seed, and DB cleanup - echo-runtime.ts: minimal A2A JSON-RPC server with workspace-side /internal/chat/uploads/ingest endpoint for file-attachment round-trips - panel load, send/receive echo, history persistence - file attachment round-trip (desktop + mobile) - composer auto-grow (mobile) - markdown rendering: code blocks and tables (desktop) - activity log visibility (desktop) - Extract shared hooks: useChatHistory, useChatSend, useChatSocket - MobileChat: add file attachments, markdown rendering, history context - ChatTab: migrate to shared hooks - data-testid: chat-panel, workspace-card, mobile-chat-cta - .gitea/workflows/e2e-chat.yml: ephemeral Postgres/Redis, workspace-server build, canvas dev server, Playwright run, artifact upload on failure	2026-05-15 14:20:04 -07:00
devops-engineer	02a37a360c	Merge pull request 'chore: promote #1121 (broadcast + talk-to-user abilities) to main' (#1224) from promote/1121-broadcast-talk-to-user-to-main into main	2026-05-15 19:52:03 +00:00
hongming-codex-laptop	5a05302cd6	fix(broadcast): OFFSEC-015 — scope recipients to sender's org ... Previously POST /workspaces/:id/broadcast collected every non-removed workspace in the database, allowing a workspace in Org-A to broadcast to every workspace in Org-B, Org-C, etc. Fix: walk parent_id chain with a recursive CTE to find the sender's org root, then filter recipients to workspaces sharing that root. Same isolation pattern as hotfix #1157 (staging) — port to this main-target PR so the cherry-pick doesn't ship the vulnerable original. Adds workspace_broadcast_test.go from #1157 with: - TestBroadcast_OrgScopedRecipients (cross-org isolation regression) - TestBroadcast_OrgScoped_OrgRootSender - TestBroadcast_OrgScoped_ChildWorkspaceSender - + NotFound / Disabled / EmptyOrg / InvalidID coverage Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-15 12:30:03 -07:00
hongming-codex-laptop	59b4f44224	fix(mcp): add broadcast_message dispatch arm to a2a_mcp_server ... test_dispatcher_schema_drift caught that broadcast_message was registered in platform_tools.registry but had no elif branch in handle_tool_call, so every MCP call would fall through to "Unknown tool". Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-15 12:03:08 -07:00
hongming-codex-laptop	ee55473812	test(e2e): workspace broadcast and talk-to-user abilities ... 20-assertion shell E2E covering the full abilities contract: - talk_to_user_enabled=true (default) → POST /notify succeeds - PATCH /abilities to disable → /notify returns 403 with error code and delegate_task hint; re-enabling restores delivery - broadcast_enabled=false (default) → POST /broadcast returns 403 - PATCH /abilities to enable → fan-out succeeds, delivered count >= 1 - Receiver activity log has broadcast_receive row (activity_type) with correct summary and source_id pointing at sender workspace - Sender activity log has broadcast_sent row; sender has no self-receive - Empty broadcast message returns 400 - Partial PATCH leaves unmentioned flags unchanged Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-15 12:03:08 -07:00
hongming-codex-laptop	29b4bffb13	feat(workspace): add broadcast and talk-to-user platform abilities ... Two new workspace-level ability flags (broadcast_enabled, talk_to_user_enabled) with full backend enforcement, MCP tool, and canvas UI: - Migration: adds broadcast_enabled (default false) and talk_to_user_enabled (default true) columns to workspaces table - PATCH /workspaces/:id/abilities (AdminAuth) toggles either flag independently - POST /workspaces/:id/broadcast (WorkspaceAuth) fans out a broadcast_receive activity_log entry + WS BROADCAST_MESSAGE event to all non-removed peers; requires broadcast_enabled=true on the sender - AgentMessageWriter checks talk_to_user_enabled; returns ErrTalkToUserDisabled which surfaces as HTTP 403 on /notify and the send_message_to_user MCP tool - broadcast_message MCP tool added to registry + a2a_tools_messaging.py - Canvas ChatTab shows "Agent is not enabled to chat with you" banner with Enable button when talkToUserEnabled=false on the workspace node Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-15 12:03:08 -07:00
devops-engineer	76609f4129	Merge pull request 'feat(workspace): broadcast and talk-to-user platform abilities' (#1121) from feat/workspace-abilities-broadcast-talk-to-user into staging	2026-05-15 07:42:19 +00:00
Molecule AI App-FE	5dc1e462de	fix(external-workspace): pin molecule-ai-workspace-runtime>=0.1.999 in OpenClaw snippet (#1143) ... fix(external-workspace): pin molecule-ai-workspace-runtime>=0.1.999 in OpenClaw snippet Ensures the molecule-mcp console script (heartbeat + register-on-startup) is present on install. Older versions only ship a2a_mcp_server which does not heartbeat, causing workspaces to go OFFLINE within 60s. Closes openclaw keepalive regression. Co-authored-by: Molecule AI App-FE <app-fe@agents.moleculesai.app> Co-committed-by: Molecule AI App-FE <app-fe@agents.moleculesai.app>	2026-05-15 07:35:57 +00:00
hongming-codex-laptop	8439a066b6	fix(mcp): add broadcast_message dispatch arm to a2a_mcp_server ... test_dispatcher_schema_drift caught that broadcast_message was registered in platform_tools.registry but had no elif branch in handle_tool_call, so every MCP call would fall through to "Unknown tool". Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-15 00:19:44 -07:00
hongming-codex-laptop	d7d376118d	test(e2e): workspace broadcast and talk-to-user abilities ... 20-assertion shell E2E covering the full abilities contract: - talk_to_user_enabled=true (default) → POST /notify succeeds - PATCH /abilities to disable → /notify returns 403 with error code and delegate_task hint; re-enabling restores delivery - broadcast_enabled=false (default) → POST /broadcast returns 403 - PATCH /abilities to enable → fan-out succeeds, delivered count >= 1 - Receiver activity log has broadcast_receive row (activity_type) with correct summary and source_id pointing at sender workspace - Sender activity log has broadcast_sent row; sender has no self-receive - Empty broadcast message returns 400 - Partial PATCH leaves unmentioned flags unchanged Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-15 00:19:44 -07:00
hongming-codex-laptop	026d1c5fae	feat(workspace): add broadcast and talk-to-user platform abilities ... Two new workspace-level ability flags (broadcast_enabled, talk_to_user_enabled) with full backend enforcement, MCP tool, and canvas UI: - Migration: adds broadcast_enabled (default false) and talk_to_user_enabled (default true) columns to workspaces table - PATCH /workspaces/:id/abilities (AdminAuth) toggles either flag independently - POST /workspaces/:id/broadcast (WorkspaceAuth) fans out a broadcast_receive activity_log entry + WS BROADCAST_MESSAGE event to all non-removed peers; requires broadcast_enabled=true on the sender - AgentMessageWriter checks talk_to_user_enabled; returns ErrTalkToUserDisabled which surfaces as HTTP 403 on /notify and the send_message_to_user MCP tool - broadcast_message MCP tool added to registry + a2a_tools_messaging.py - Canvas ChatTab shows "Agent is not enabled to chat with you" banner with Enable button when talkToUserEnabled=false on the workspace node Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-15 00:19:44 -07:00
devops-engineer	48ad38e795	Merge pull request 'feat(adapter-base): ProviderRegistry type + resolve_provider_routing utility' (#1138) from feat/provider-routing-base-v2 into staging	2026-05-15 06:52:15 +00:00
core-devops	4bdb10b5e2	feat(adapter-base): add ProviderRegistry type + resolve_provider_routing utility ... Adds a shared resolver that maps `provider:model` strings to (api_key, base_url, model_id). Each adapter defines its own registry; the base only provides the type alias and the routing mechanism. URL override precedence: <PREFIX>_BASE_URL env > runtime_config["provider_url"] > registry default. Unknown prefixes fall back to OpenAI credentials. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-14 23:02:09 -07:00
devops-engineer	ec96a8f600	Merge pull request 'fix(ci): throttle SOP refire workflow fan-out' (#1134) from fix/ci-sop-refire-concurrency into main	2026-05-15 05:57:38 +00:00