fix(ci): publish SDK internal deps before sdk

[khaliqgant]

Summary

• publish required SDK internal packages (config, github-primitive, workflow-types) during package=sdk releases before publishing @agent-relay/sdk
• skip already-published internal package versions so reruns can repair a missing package without failing on existing ones
• include the same internal deps in sdk dry-run validation

Why

@agent-relay/sdk@6.0.4 depends on @agent-relay/workflow-types@6.0.4, but that package was not published, so runtime imports of @agent-relay/sdk/workflows fail with Cannot find module @agent-relay/workflow-types. PR #804 fixed the package=all path; this covers the package=sdk path and lets reruns publish a missing internal dep idempotently.

Validation

• ruby -e "require 'yaml'; YAML.load_file('.github/workflows/publish.yml'); puts 'YAML_OK'"\n- npm --prefix packages/workflow-types run build\n- (cd packages/workflow-types && npm pack --ignore-scripts --pack-destination "$tmp") verified tarball contains dist/index.js, dist/index.d.ts, source maps, and package.json

---

[devin-ai-integration]

Devin Review found 1 potential issue.

View 3 additional findings in Devin Review.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d003c729f0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Skip SDK publish when version is already on npm

The new idempotency check only guards config, github-primitive, and workflow-types; the workflow still always runs npm publish for @agent-relay/sdk. In the exact recovery case this change targets (rerun with the same version after SDK was already published but an internal dep was missing), the internal dep can be repaired but the job still fails at SDK publish because npm rejects republishing an existing name/version. Add the same existence check (or a dist-tag update path) for SDK so reruns can complete successfully.

Useful? React with 👍 / 👎.