`draft create` does not respect file permissions in packs
After skimming through the existing packs, it looks like most or all of them don't have executables, which could explain this bug I found: if a file in a pack is marked as an executable, draft create -ping it drops the executable bit in the resulting file structure. To express this more generally, file permissions from draft packs should be preserved by draft create.
That is a great thing to have found! Thank you.
...and, in an ironic twist, the reverse was discovered happening inside charts/[service-name]/templates: _helpers.tpl, together with all *.yaml files, have gotten the executable bit added in the draft created file structure, where it was not present in the pack!