Why do I have to nest my charts inside of the `charts/` subdirectory?

Lets say I have a Git repository structured like this:

```
github.com/myorg/helm-charts
chart1/
templates/
Chart.yaml
chart2/
templates/
Chart.yaml
README.md
```

If I pass the `chart_dir` in my GitHub Workflow file as the current checked out working directory (e.g. `.`), it doesn't work. If I re-organize my repository structure so that it maps to:

```
github.com/myorg/helm-charts
charts/
chart1/
templates/
Chart.yaml
chart2/
templates/
Chart.yaml
README.md
```

it works just fine.

Having a top-level repository `helm-charts` and requiring a nested `charts` directory stutters and is completely unnecessary. Why was this design decision chosen and would you be willing to change it?

Start with the GitHub Workflow configuration and the code path that consumes chart_dir; compare behavior when it is set to . with the required charts/ layout. Review the existing comment discussion before deciding whether root-level charts should be supported, and validate completion against the repository structure shown in the issue.

Written by the indexing model from the issue text.