* fix(bundler): resolve built-in step types when checking bundle references
`_resolved_locally` gives three of the four component kinds a
"is it bundled with Spec Kit?" check before the installed-in-project one:
presets -> _locate_bundled_preset or PresetManager.get_pack
extensions -> _locate_bundled_extension or ExtensionManager...is_installed
workflows -> _locate_bundled_workflow or WorkflowRegistry.is_installed
steps -> StepRegistry.is_installed <-- no bundled check
`StepRegistry` tracks *community* step types installed under
`.specify/workflows/steps/`. Spec Kit ships 11 step types as built-ins
registered in `STEP_REGISTRY`, so every one of them looked unresolved:
steps/shell -> False
steps/gate -> False
steps/command -> False
steps/if -> False
A bundle declaring a dependency on any built-in step type was therefore
reported as an unresolved reference — an error online, a warning offline.
There is no `_locate_bundled_step` to mirror, because step types are not
an on-disk asset directory; `STEP_REGISTRY` is the equivalent check, and
is what `specify workflow step info` reports as "built-in".
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(bundler): check an immutable built-in step set, not the mutable registry
Review catch: `STEP_REGISTRY` is not limited to bundled steps.
`load_custom_steps` adds project-installed ids to that process-global
mapping and never removes them, so in a long-lived process a community step
loaded while working on project A would be accepted as "bundled" when
validating a bundle for project B — before B's own StepRegistry is
consulted.
Snapshot the shipped ids into `BUILTIN_STEP_TYPES` immediately after
`_register_builtin_steps()`, before `load_custom_steps` is even defined,
and check that frozenset instead.
Verified: with the check on STEP_REGISTRY the new cross-project test fails
(a leaked community id resolves as bundled); with BUILTIN_STEP_TYPES it
passes. 1 failed, 5 passed -> 6 passed.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Ali jawwad
21fb1bbbb3