Add cmd_verify prompt to install output; fix --insecure docs

- install.sh: print 'verify' command immediately after successful restart
  so users know to confirm the backend patch loaded before creating tasks
- README: correct --insecure description; it controls TLS to the TrueNAS
  API (where the API key is transmitted), not the S3 endpoint — previous
  wording implied it was safe to use for S3 self-signed certs

README.md

@@ -379,5 +379,11 @@ B2's native restic backend uses a different auth path than S3-compatible B2.
 **S3-compatible backup fails**
 S3 support already existed in the backend — the credential setup is the likely
 issue. Verify the endpoint URL, access key, secret key, and bucket name in
-the credential settings. Use `--insecure` in create_task.py only if you are
-using a self-signed certificate on your S3 endpoint.
+the credential settings.
+
+**`create_task.py` SSL error connecting to TrueNAS**
+`create_task.py` talks to the **TrueNAS API**, not your S3 endpoint, and
+verifies its TLS certificate. If your NAS uses a self-signed certificate,
+pass `--insecure` — but be aware this disables certificate verification for
+the API call that transmits your TrueNAS API key. Adding your NAS certificate
+to your system's trust store is safer.

install.sh

@@ -117,6 +117,9 @@ if ! systemctl restart middlewared; then
 fi
 echo "Done."
 echo ""
+echo "Verify the backend patch loaded correctly:"
+echo "  python3 $PATCH_DIR/create_task.py verify"
+echo ""
 echo "Refresh your browser to pick up the UI change."
 echo ""
 echo "To create a TrueCloud Backup task with S3 or B2 credentials:"