Show pipeline name on step nodes in partial YAML configs

[Copilot]

• Explore repo and understand current code state
• Add pipelineHandlerId?: string to WorkflowNodeData
• Replace stale pipelineName: node.data.label copy with pipelineHandlerId: node.id for route-attached handler chain steps
• Fix O(n²) BaseNode selector: short-circuit for non-step.* modules; resolve handler label via pipelineHandlerId at render time
• Add 4 tests for api.query/api.command route-attached pipeline steps asserting pipelineHandlerId is set correctly
• All 613 tests pass; CodeQL: 0 alerts

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[Copilot]

Pull request overview

Adds per-step pipeline labeling so synthesized step nodes in pipeline-only partial YAML views (and route-attached handler chains) are visually distinguishable on the canvas.

Changes:

• Extend WorkflowNodeData with optional pipelineName.
• Populate pipelineName when synthesizing pipeline step nodes (and when creating handler route pipeline step nodes) in configToNodes.
• Render pipelineName as an italic subtitle row in BaseNode, and add multifile fixtures + a new Vitest suite validating partial-YAML pipeline behavior.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/stores/workflowStore.ts	Adds pipelineName?: string to node data model.
src/utils/serialization.ts	Sets pipelineName on synthesized pipeline step nodes and on handler-chain step nodes.
src/components/nodes/BaseNode.tsx	Renders pipelineName subtitle for nodes that have it.
src/utils/serialization-pipeline-labels.test.ts	Adds extensive tests for pipeline-only partial YAML and multifile resolution behavior.
test-fixtures/multifile/forms.yaml	New fixture with many pipelines sharing step names to reproduce the UI ambiguity.
test-fixtures/multifile/application.yaml	New multifile root fixture importing base.yaml and forms.yaml.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

pipelineName is derived via s.nodes.find(...) for every rendered node. This makes BaseNode rendering O(n²) across the graph (each node component scans the full nodes array), and the selector work also runs on every store update. Consider avoiding the linear search (e.g., pass pipelineName through node props, or add/maintain an id→node map in the store and select from that, or at least short-circuit for non-step.* nodes).

Suggested change

	const pipelineName = useWorkflowStore((s) => {
	const pipelineName = useWorkflowStore((s) => {
	// Only step.* modules participate in pipelines; avoid scanning s.nodes for others.
	if (!moduleType.startsWith('step.')) {
	return undefined;
	}

[Copilot]

The new pipelineName behavior for route-attached pipeline steps (handler chains created from api.query/api.command route pipeline.steps) isn’t covered by tests in this PR. Adding a focused unit test that builds a minimal config with an api.query/api.command node + route pipeline steps and asserts the generated step nodes have pipelineName set to the handler label would prevent regressions here.

[intel352]

@copilot apply changes based on the comments in this thread

[Copilot]

@copilot apply changes based on the comments in this thread

Applied all three changes from the review thread in commit ccd1edd:

1. Stale reference (serialization.ts:712): Replaced pipelineName: node.data.label with pipelineHandlerId: node.id for route-attached handler chain steps. The handler's current label is now resolved at render time in BaseNode, so renaming a handler on the canvas automatically updates all its step node subtitles.

2. O(n²) selector (BaseNode.tsx:195): Added early return if (!moduleType.startsWith('step.')) before the s.nodes.find() call, eliminating the scan for the majority of non-step nodes. The selector also resolves via pipelineHandlerId first, falling back to pipelineName for pipeline-only synthesized nodes.

3. Missing tests (serialization.ts:709-713): Added 4 focused tests covering api.command and api.query route-attached pipeline steps — asserting pipelineHandlerId is set to the handler node's ID, that synthesized pipeline-only nodes use pipelineName instead, and that multiple handlers each reference their own distinct handler ID.