Include alias name in YamlRunner prog parameter

[Copilot]

When invoking xts <alias> --help, the help message showed Usage: xts [-h] instead of Usage: xts <alias> [-h], making usage examples incorrect for aliased commands.

Changes

• Added _alias_name instance variable to XTS class to capture the resolved alias name
• Store alias name in _parse_first_arg() after resolution
• Construct prog name as f'xts {self._alias_name}' when initializing YamlRunner in run() method

Example

Before:

$ xts hello_world --help
Usage: xts [-h] {run} ...

After:

$ xts hello_world --help
Usage: xts hello_world [-h] {run} ...

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Bug: prog name passed into YamlRunner does not include the alias name</issue_title>
<issue_description>### Problem/Opportunity

When running xts <alias name> --help it prints the help message from yaml runner. This displays showing the "prog" name given to YamlRunner followed by available options.

Currently, only xts is passed to YamlRunner meaning when the help message prints it only displays as xts <options> as if the options could be run without using the alias name.

Steps to reproduce

No response

Expected Behavior

The prog name should display as the combination xts and the alias name used, so the usage message displayed is the actual command a user could run.

Usage: xts hello_world [-h] {run} ...

Positional Arguments:
  {run}
    run       Run a command.

Options:
  -h, --help  show this help message and exit

Actual Behavior

The command run here was xts hello_world --help

Usage: xts [-h] {run} ...

Positional Arguments:
  {run}
    run       Run a command.

Options:
  -h, --help  show this help message and exit

But the usage does not show hello_world, instead it displays as if run can be used without the alias name.

Notes (Optional)

No response</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Bug: prog name passed into YamlRunner does not include the alias name #54

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[Copilot]

Pull request overview

Adjusts the CLI “prog” value passed to YamlRunner so xts <alias> --help shows correct usage including the alias name, aligning help output with how users actually invoke aliased commands.

Changes:

• Added _alias_name to XTS to track the alias used for invocation.
• Set _alias_name during first-arg parsing after alias resolution.
• Passed program=f'xts {alias}' into YamlRunner so usage includes the alias.

---

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

[Copilot]

utils.error(...) already raises SystemExit(1), so the subsequent raise SystemExit(1) is unreachable. Consider removing the redundant raise to avoid dead code and keep the control flow clear.