fix(publish): add local-surface to the lockstep publish target list

Merged
KH
3mo ago
+3-2

Summary

  • @agentworkforce/local-surface (added in #263) was never added to the hardcoded package list in publish.yml's "Resolve target packages" step.
  • Because of that, it never went through the pnpm pack step that rewrites workspace:* deps to concrete versions before npm publish. It ended up on npm (v4.1.17, its only published version) with literal "workspace:*" strings still in its dependencies for @agentworkforce/deploy, persona-kit, and runtime.
  • Any plain npm install that resolves this package now hard-crashes with Unsupported URL Type "workspace:": workspace:* (npm-package-arg can't parse the pnpm workspace protocol). This breaks npm install -g agentworkforce@latest entirely, since @agentworkforce/cli depends on local-surface@4.1.17.
  • Fix: add local-surface to the topological package list, slotted after its workspace deps (deploy/persona-kit/runtime) and before its only consumer (cli).

Test plan

  • YAML validated (yaml.safe_load)
  • Next Publish Packages workflow run republishes local-surface at the new lockstep version via pnpm pack (confirms workspace refs are resolved in the published tarball)
  • npm install -g agentworkforce@latest succeeds after the new version is live

🤖 Generated with Claude Code