feature to write the name of artifact with custom and dynamic inputs

[krishna9358]

…namic inputs

Summary

• Added artifactName input with dynamic placeholder support ({{run_id}}, {{timestamp}}, {{date}}, {{time}}, {{run_name}}, {{task}}, {{dataset}})
• Created DynamicArtifactNameInput UI component showing available placeholders with click-to-insert
• Replaced fileName parameter with fileExtension for cleaner separation
• Default naming pattern: {{run_id}}-{{timestamp}}

Changes

• worker/src/components/core/artifact-writer.ts - Added input port, placeholder substitution logic
• frontend/src/components/workflow/DynamicArtifactNameInput.tsx - New component for sidebar UI
• frontend/src/components/workflow/ConfigPanel.tsx - Integrated custom input for artifact-writer
• Updated tests for new input structure

Testing

• bun run test
• bun run lint
• bun run typecheck
• Additional notes:

Documentation

• Updated the relevant doc(s) (see docs/guide.md) or checked that no updates are needed.
• Recorded contract/architecture changes in both public docs and .ai logs when applicable.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[betterclever]

Review Feedback

Issue 1: {{dataset}} placeholder is hardcoded to "default"

In worker/src/components/core/artifact-writer.ts:67, the {{dataset}} placeholder is hardcoded to return the string "default". This provides no value to users and is misleading.

Suggestion: Either remove this placeholder or properly implement it by adding dataset to the execution context.

Issue 2: {{task}} placeholder naming is confusing

The {{task}} placeholder doesn't actually return a task name - it returns the component's reference ID (node ID in the workflow). The naming is misleading for users.

Suggestion: Rename to {{node_id}} or {{component_ref}} for clarity, and update documentation accordingly.

Issue 3: {{run_name}} implementation is unintuitive

The `{{run_name}}) logic takes the last segment after a hyphen, or the first 8 characters of the run ID. This "vibe-based" logic is confusing and not predictable for users.

Suggestion: Either remove this placeholder or make it explicitly configurable (e.g., add a proper run name to the execution context).

Issue 4: Documentation mismatch

The placeholder descriptions don't match what they actually return:

• {{dataset}} says "Dataset name" but always returns "default"
• {{task}} says "Task name" but returns the component ref ID

Suggestion: Update documentation to match actual behavior, or fix the behavior to match the documentation.

---

Overall, the placeholder system needs more thoughtful design. Hardcoded values and misleading names make this feature difficult for users to understand and use effectively.

[betterclever]

This placeholder is hardcoded to always return "default". Either remove this placeholder or properly implement it by adding dataset to the execution context.

[betterclever]

Misleading name: this returns the component reference ID (node ID in workflow), not a task name. Consider renaming to node_id or component_ref for clarity.

[betterclever]

The documentation says "Dataset name (if available)" but this actually returns the hardcoded string "default". Please either remove this placeholder or implement it properly.

[betterclever]

The documentation says "Task name (if available)" but this actually returns the component reference ID. Please update the documentation or rename the placeholder.

[betterclever]

This logic is confusing and unpredictable - it takes the last segment after a hyphen, or the first 8 characters of the runId. Consider removing this placeholder or adding an actual run name to the execution context.