Command Level Templating

[RiSKeD]

This PR introduces command level templating as discussed in #248. The first commit refactors the dutagent with a common entry point for passing args to modules. The second commit makes the concept of a main module optional. The third commit adds command level templating as seen above. The help texts are also improved but still need to be refactored after #191 is resolved.

[Copilot]

Pull request overview

This PR introduces command-level templating functionality, allowing commands to declare named arguments that can be distributed to modules via ${arg-name} template syntax. The changes refactor the "main module" concept to "interactive module" to better reflect its purpose, and make having an interactive module optional when using command-level arguments.

Key changes:

• Adds Args field to Command struct for declaring named command arguments with positional mapping
• Renames Main to Interactive in ModuleConfig to clarify the module's role
• Implements template substitution using os.Expand with validation of template references during configuration parsing

Reviewed changes

Copilot reviewed 19 out of 19 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
pkg/dut/dut.go	Core implementation: adds ArgDecl struct, template validation and substitution logic, renames Main to Interactive, updates error definitions
pkg/dut/dut_test.go	Comprehensive test coverage for template validation, extraction, and substitution with various edge cases
cmds/dutagent/states.go	Refactors module execution: adds getModuleArgs for unified argument distribution, extracts runModules function, adds runtime validation for argument requirements
cmds/dutagent/states_test.go	Updates test cases to use Interactive instead of Main, renames variables for consistency
cmds/dutagent/rpc.go	Updates buildCommandHelp to handle commands without interactive modules and append command args documentation
docs/dutagent-config.md	Updates schema documentation to reflect interactive field and new command-level args capability
docs/command-arg-templating.md	New comprehensive guide explaining three argument approaches: non-interactive, interactive, and templating with examples
contrib/dutagent-cfg-example.yaml	Demonstrates new templating feature with file-transfer command example
pkg/module/*/*-example-cfg.yml	Updates all module examples from main: true to interactive: true
cmds/exp/contrib/config-*.yaml	Updates experimental config files to use interactive instead of main

---

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

[Copilot]

Pull request overview

Copilot reviewed 19 out of 19 changed files in this pull request and generated 2 comments.

---

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

[RiSKeD]

@jenstopp One thing i noticed when working on this is that the dut.go file/pkg handles a lot of concerns. Unmarshalling of the config, All the command, module, and dut functions too. Long-term it might be better to separate these concerns into multiple packages.

[Copilot]

Pull request overview

Copilot reviewed 19 out of 19 changed files in this pull request and generated 1 comment.

---

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

[llogen]

I have nothing to complain about. Looks very clean and straight forward to me

[RiSKeD]

Tested this on the internal board with an updated config using all methods.

[Copilot]

Pull request overview

Copilot reviewed 19 out of 19 changed files in this pull request and generated no new comments.

---

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