chore: evaluate project direction and polish backlog

[HamidMolareza]

Context

This repository is a small TypeScript GitHub Action for normalizing workflow inputs/defaults, logging them, and optionally converting command output into action outputs.

A recent review suggests that this project is not worth heavy product-style investment right now, but it is worth a small polish sprint if we want to keep it as a useful CI/CD utility and a presentable portfolio project.

Current assessment

• The project solves a real but niche GitHub Actions workflow problem.
• It already has useful project infrastructure: tests, CI, check-dist, CodeQL, release-please, version tags, and documentation.
• External traction is currently low: very few stars/forks and no meaningful user-reported issue history.
• The best fit is likely:
  • a small internal/dogfooding utility,
  • a portfolio/resume project showing GitHub Actions and release automation,
  • or a reusable helper for Payadel/personal workflows.
• It is probably not a good candidate for major product, monetization, or long-term feature-heavy development unless real users start depending on it.

Suggested polish backlog

• Fix input merge behavior in src/main.ts: targetIndex > 0 should not skip an existing YAML input at index 0.
• Add tests covering a GitHub input overriding the first YAML input.
• Revisit command execution behavior in src/execCommands.ts.
• Consider making command execution explicitly opt-in instead of enabled by default.
• Document the trust/security model for $(command) expansion.
• Add clear examples for safe usage and unsafe/untrusted input scenarios.
• Tighten README positioning: explain the exact problem, when to use this action, and when native GitHub Actions expressions are enough.
• Add a few real workflow examples from dogfooding usage.
• Improve Marketplace-facing metadata and wording.
• Keep the scope small; avoid turning this into a broad workflow automation framework.

Decision note

Recommended direction: do a short maintenance/polish pass, then only continue development if this action is used regularly in real repositories or receives external user demand.