enhancement(resolver): hoist `import yaml` above both extension loops

[yasinBursali]

Severity: Trivial (cleanup)
Category: Compose resolver
Platform: All
Confidence: Flagged during PR 2C review

Description

After PR 2C added manifest filtering to the user-extension loop in
resolve-compose-stack.sh, both the built-in and user-extension loops now have
their own local try: import yaml; yaml_available = True block. Duplication is
harmless but redundant — import yaml can be hoisted above both loops.

Affected file(s)

• dream-server/scripts/resolve-compose-stack.sh — inline Python heredoc

Suggested approach

Move the import yaml / yaml_available block above the if ext_dir.exists():
guard so both loops share the same binding.

Labels

cleanup, resolver, tech-debt

[yasinBursali]

Addressed by upstream PR Light-Heart-Labs#1051 (fix(resolver): hoist yaml import, guard empty manifests, align user-ext loop). Note: PR is DRAFT, must merge after upstream PR Light-Heart-Labs#1029 (which adds a second yaml import inside the user-ext loop, making the hoist meaningful). Closing the fork issue.