Release v0.52.0 · Pipelex/pipelex-sdk

`@pipelex/sdk` on npm

A duplicate refused for a bundle naming the original's run files: MethodCopyRefused, MethodCopyRefusalReason, BundleStorageReference, copyMethod and docs/method-copy.md describe the refusal the platform now answers a duplicate too, when a .mthds file names a stored file under the original method's own run files (pipelex-storage://<org_id>/<method_id>/…), which erasing the original would remove, beside the references the destination cannot read; the verdict, its reason bundle_names_other_storage and its shape are unchanged, so a caller branching on outcome needs nothing new.

The copy's documented refusals: copyMethod's JSDoc, MethodCopyRequestOptions and docs/method-copy.md match the platform's answers: the 409 conflict of a tree the organization no longer holds whole is runtime and told from a reused key's input one by errorDomain, the 413 also refuses a name that leaves the copy's row no room for a publish, the 500 is not retryable when the platform has no storage credentials, and the 503 also covers a DynamoDB failure, its detail naming the copy's method id when the row could not be confirmed, a copy that may stand and that a retry may make twice; a copy of an empty draft, and its copied_from, carry a null draft_digest.

A duplicate refused for a bundle naming the original's run files: MethodCopyRefused, MethodCopyRefusalReason.BUNDLE_NAMES_OTHER_STORAGE, BundleStorageReference, copy_method and docs/method-copy.md describe the refusal the platform now answers a duplicate too, when a .mthds file names a stored file under the original method's own run files (pipelex-storage://<org_id>/<method_id>/…), which erasing the original would remove, beside the references the destination cannot read; the verdict, its reason bundle_names_other_storage and its shape are unchanged, so a caller branching on outcome needs nothing new.

The copy's documented refusals: copy_method's docstring and docs/method-copy.md match the platform's answers: the 409 conflict of a tree the organization no longer holds whole is runtime and told from a reused key's input one by error_domain, the 413 also refuses a name that leaves the copy's row no room for a publish, the 500 is not retryable when the platform has no storage credentials, and the 503 also covers a DynamoDB failure, its detail naming the copy's method id when the row could not be confirmed, a copy that may stand and that a retry may make twice; a copy of an empty draft, and its copied_from, carry a None draft_digest.

The web app's brand tokens are named after their roles, and an unset colour keeps the template's own (Breaking): the web app template runs on @pipelex/mthds-form 0.23.1, and a branded page writes the accent's ink onto --link and --ring and its pale fill onto --selected, the form kernel's role-named tokens, where it wrote --brand, --brand-muted and --brand-muted-foreground, so a focused control is outlined in the team's accent too, and the template's utilities are text-link, border-link and bg-selected, where they were text-brand, border-brand, bg-brand-muted and text-brand-muted-foreground, which a project's own components rename the same way. Only the colours a team set are written: a team that set no button colour keeps the template's neutral --primary where it got Pipelex green, one that set neither an accent nor a button colour keeps the template's link ink, selected fill and focus ring, one that set no header colour keeps the page as its band, and one that set logos and no colour renders no colour sheet at all.