[yuhangsigma]

Validate and Release assume every plugin sits at plugins/<host>/<name>/. The Claude plugin is becoming a single plugin for every region, at plugins/claude/ itself, so the workflows need to accept that layout. They keep accepting the current one, a folder per plugin, so this can merge before the layout changes.

Validate

• The skills step looks at depth 1 or 2 (-mindepth 1 -maxdepth 2).
• In the other-hosts check, plugins/claude is the plugin when it holds .claude-plugin/plugin.json; otherwise each folder is, as before.

Release

• The version step does the same for plugins/claude.
• The archive step zips plugins/claude's contents once as <name from plugin.json>-<slug>.claude.plugin and skips Claude in the per-folder loop. With the current layout it zips each folder as before.

What I ran, with the Claude Code CLI pinned in validate.yml (2.1.284), against both layouts:

	current main	new layout
claude plugin validate --strict on the marketplace, the manifest(s) and the skills	passes (13 skills dirs)	passes (1)
Validate's other-hosts check	65 manifests and entries at 0.11.12	53 at 0.11.13
Release version step	52 plugins at 0.11.12	40 plugins at 0.11.13
Release archive step	52 archives, 13 .claude.plugin	40 archives, one sigma-build-<slug>.claude.plugin

This needs to merge before the next sync: the sync PR changes the layout, and its Validate run uses the workflows on main. Once the new layout is in, the old-layout branches can be removed in a follow-up.

[yuhangsigma]

Closing: the Claude plugin will stay in a folder under plugins/claude/, like the other hosts, so these workflows need no change.