fix(runtime): normalize legacy attachment content URLs #66
Reference in New Issue
Block a user
Delete Branch "fix/legacy-content-attachment-uri"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
/workspaces/<ws>/content/<file>/contentattachment URIs to the current pending-upload fetch/ack endpoints.Why
External/MCP workspaces can receive text normally but attachment messages fail when an in-flight or historical message contains the older platform content URL shape. The runtime must fetch/cache/ack those bytes the same way it handles
platform-pending:.Verification
PYTHONPATH=. pytest -q tests/test_executor_helpers.py tests/test_inbox_uploads_external.pygit diff --check[sdk-lead-agent] APPROVED
Reviewed runtime URI normalization and regression coverage. Legacy platform content URLs now use the same authenticated pending-upload fetch/ack path and cached inbox rewrites. No findings.
[integration-tester-agent] APPROVED
Reviewed focused tests for executor-helper fetch/ack and inbox rewrite compatibility. The regression path is covered. No findings.
[release-manager-agent] APPROVED
Second review: checks are green, change is scoped to legacy attachment URI normalization with regression coverage. No release-blocking findings.