Purpose

This PR addresses the issue where Custom nodes (.dyf files) published via "Publish → Publish Custom Node (.dyf)" menu didn't appear in the package contents in the publish wizard.

Cause
ShowNodePublishInfo() only populated CustomNodeDefinitions but not CustomDyfFilepaths. The wizard filters out CustomNode type items and only displays CustomNodePreview type items (created from CustomDyfFilepaths), resulting in empty package contents.

Solution

• Populate CustomDyfFilepaths with file paths from CustomNodeInfo before setting CustomNodeDefinitions (which triggers RefreshPackageContents())
• Added fallback to use workspace.FileName when CustomNodeInfo.Path is empty
• Enhanced OnDataContextChanged to check CustomDyfFilepaths count in addition to HasChanges for proper pending update detection

Changes

Declarations

Check these if you believe they are true

• Is documented according to the standards
• The level of testing this PR includes is appropriate
• Changes to the API follow Semantic Versioning and are documented in the API Changes document.

Release Notes

• now correctly refreshes the datacontext and triggers update to the UI

Reviewers

@zeusongit

FYIs

@benglin