Problem
plugins/pipelinesteps/plugin.go retains a *handlers.PipelineWorkflowHandler field and exposes it via a PipelineHandler() getter. cmd/server/main.go then calls this getter and directly sets properties on the handler, bypassing the plugin interface contract.
Fix Direction
Use wiring hooks in the plugin lifecycle to perform setup internally. The caller should never need to reach inside a plugin to configure it. Move the SetStepRegistry call and any other direct property sets into the plugin's own Init() or wiring hook so cmd/server/main.go only calls standard plugin lifecycle methods.
Context
See docs/DEFERRED_ISSUES.md — Architecture section.
Problem
plugins/pipelinesteps/plugin.goretains a*handlers.PipelineWorkflowHandlerfield and exposes it via aPipelineHandler()getter.cmd/server/main.gothen calls this getter and directly sets properties on the handler, bypassing the plugin interface contract.Fix Direction
Use wiring hooks in the plugin lifecycle to perform setup internally. The caller should never need to reach inside a plugin to configure it. Move the
SetStepRegistrycall and any other direct property sets into the plugin's ownInit()or wiring hook socmd/server/main.goonly calls standard plugin lifecycle methods.Context
See
docs/DEFERRED_ISSUES.md— Architecture section.