Interoperability would be easier if the name of the task json was static.

[bentorkington]

Describe the feature
Use a static filename for the tasks JSON instead of one based on a sha1 that bumps with new releases.

Describe your idea
Add the schema version to a static top-level key in the JSON, and use that for determining if migration is necessary.

In the next version bump, rename the tasks JSON to something friendly like 'tasks.json' (in conjunction with #18?)

Now users can write scripts that process their tasks / integrate it with other things they use, that won't break whenever basilk bumps its version.