lychee

You probably might want to use batch for this, if possible, because PowerShell by default disallows script execution. It's really wild

I probably stretched this out more than it should've been but I had to get this off my mind

I believe that the CLI should go by a `MAJOR.CHANGES` system Where: - `MAJOR` is the major version of the DSL, ensuring that changes among both packages can remain on...

Another addendum to this suggestion is that if a major DSL release has occured, so should a CLI release.

@terefang Apologies for my asking, as I'm quite new to all of this stuff and I would like to help to the best of my ability, but is `s3cr3tPa55w0rd` the...

Unless I'm gravely mistaken, it seems if Go's `crypto` module already does this for the user. 

> If permitted, I'd like to add a shell hook that executes the default shell using the `$SHELL` env var so running `nix develop` will drop you into whatever shell...

> @itslychee I have specified the three major systems, do you reckon there's anything else to add? Don't forget to change `buildInputs` to `packages`, and after that I'd squash all...

Also since `eachDefaultSystem` is used currently, it's best to add `"x86_64-linux"` to the platform list to keep it backwards compatible as `eachDefaultSystem` used 4 platforms as described [here](https://github.com/numtide/flake-utils?tab=readme-ov-file#defaultsystems--system)

> Could you clarify that a bit further? The platforms list does contain "x86_64-linux" but it has come to my attention that "x86_64-darwin" is not included in the list, I...