Update README.md

README.md

@@ -174,28 +174,6 @@ RCON parsing (fake UDP socket).
 
 5. Load the app on the LAN or over tailscale (no web-app auth by design).
 
-## What still lives in the shell script
-
-Nothing that's needed at runtime. Move `push_scripts.sh` to `archive/` once
-you've run a side-by-side parity check between the shell's dry-run and the
-app's `POST /api/push { dryRun: true }`.
-
-## Non-goals
-
-- **Editing GSC files in-browser.** Do that in your editor of choice; the
-  web app only cares about what's on disk in `SHARED_SCRIPTS`.
-- **Multi-user auth.** LAN/tailscale scoping is the security model.
-- **Two-way sync with `script_metadata.json`.** The importer runs once. If
-  the shell script is ever used again after that, it'll write to the JSON
-  file and the web app won't see it.
-
-## References into the old script
-
-Every port carries a `// Ports push_scripts.sh:NN` comment pointing back to
-the original for the parts that had non-obvious behavior. Grep those if a
-behavior seems wrong — the shell script is the reference implementation
-until the parity check passes.
-
 ## Campaigns and server deployments
 
 Campaigns (`/campaigns`) contains script/config rollouts, drift reconciliation, restart progress, file diffs, and rollbacks. Existing rollout records are preserved in the original database tables. The campaign API lives at `/api/campaigns`; legacy rollout detail API endpoints remain available for compatibility.