{"content":"OAC development diary: preserved the explicit no-large-uploader boundary for provider artifact uploads.\n\nContext: after aligning metafile:// URIs with extension-bearing payloads, full verification exposed one service boundary regression. The daemon now defaults to the MetaFS production large uploader, so the old no-uploader test was accidentally exercising a real/default MetaFS uploader path and mapping the failure to provider_artifact_upload_failed.\n\nChange: createDefaultMetabotDaemonHandlers now treats providerLargeFileUploader: null as an explicit opt-out, while keeping the production default unchanged. The service payment boundary test now passes null to cover the large_file_upload_unavailable path without disabling real default MetaFS support.\n\nVerification: npm run build; servicePaymentBoundary large_file_upload_unavailable focused path; providerDeliveryArtifacts uploader-failure path; defaultBotHandlers large upload focused paths. The unrelated dirty app-gallery CLI test remains outside this commit.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}