Prepare Frame Control 0.2.0 for public testing

- Without the maintainer's key, Android compatibility reports stay on the
  Mac and the UI says so; the shared database is never contacted.
- Remove personal infrastructure details from scripts and docs: the Drive
  folder and gog wrapper now come from the environment, and the Chromium
  build host is required instead of defaulted.
- Add an MIT license, tester instructions in the README, and bump to 0.2.0.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

app/package-lock.json

@@ -1,13 +1,13 @@
 {
   "name": "frame-control",
-  "version": "0.1.1",
+  "version": "0.2.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "frame-control",
-      "version": "0.1.1",
-      "license": "UNLICENSED",
+      "version": "0.2.0",
+      "license": "MIT",
       "devDependencies": {
         "electron": "^44.4.5",
         "electron-builder": "^26.15.3"

app/package.json

@@ -1,11 +1,11 @@
 {
   "name": "frame-control",
   "productName": "Frame Control",
-  "version": "0.1.1",
+  "version": "0.2.0",
   "description": "Mac app for managing a Valve Steam Frame over SSH",
   "private": true,
   "main": "main.js",
-  "license": "UNLICENSED",
+  "license": "MIT",
   "scripts": {
     "start": "env -u ELECTRON_RUN_AS_NODE electron .",
     "icon": "env -u ELECTRON_RUN_AS_NODE electron build/make-icon.js",