Why does LoadFromPath() function of generated .pkl.go file needs .pkl file at runtime when there is already generated .pkl.go files.

Iam using pkl files for config and generated go files for it. In the process of loading config Iam using LoadFromPath() this function expects a pkl file as parameter so for this I need to have pkl executable in my system.My query is when we are already generating go file from pkl why do we need to give pkl file path again.Is there any way to load pkl files from generated code without giving path to .pkl file??

Start with the generated .pkl.go files and the LoadFromPath() entry point described in the issue. Trace why runtime loading still requires the original .pkl path and whether generated code can load configuration independently. Done should be a documented answer or a defined implementation path, with any needed behavior demonstrated by tests.

Written by the indexing model from the issue text.