bug: .aliases() and .worker() silently dropped by assembleConfig

[devalade]

What to build

The builder DSL documents .aliases(map) and .worker() but calling them has no effect at runtime — assembleConfig drops them silently. No warning, no validation error. The caller only discovers the drop when the expected behavior (e.g. shipnode run <alias>) fails.

Fix assembleConfig (or the schema it validates against) so these methods actually propagate to the resolved config. Add a regression test that instantiates a builder with .aliases({ deploy: 'pnpm deploy' }) and asserts the alias is present in the resolved config output.

Acceptance criteria

• .aliases(map) values appear in config show output
• .worker() values appear in config show output
• shipnode run <alias> executes the mapped command
• Regression test covers both methods and fails against the current 2.5.1 behavior
• If any DSL method is intentionally unsupported in a given version, config validate emits a warning naming it

Blocked by

None - can start immediately

[devalade]

Fixed in shipnode 2.5.2 — .aliases() and .worker() now propagate correctly through assembleConfig.