Fix unhandled cache-write rejection; finish events->programs cleanup

Catching the Upstash set() rejection in middleware/cache.js prevents
intermittent crashes on warm serverless instances. Also tidies
package.json/README leftovers from the events->programs rename.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: TaniWanKenobi

README.md

@@ -84,7 +84,6 @@ public/              # Static frontend demo
 controllers/         # Route handler logic
 routes/              # Express route definitions
 middleware/
-  auth.js            # x-api-key validation
   cache.js           # Upstash Redis cache
 server.js            # App entrypoint
 ```

middleware/cache.js

@@ -30,7 +30,9 @@ const cache = (duration) => {
       const originalJson = res.json.bind(res);
       res.json = (data) => {
         if (data.success) {
-          client.set(key, data, { ex: duration });
+          client.set(key, data, { ex: duration }).catch((err) => {
+            console.error('Cache write failed:', err);
+          });
         }
         originalJson(data);
       };

package.json

@@ -1,7 +1,7 @@
 {
   "name": "ysws-events-api",
   "version": "1.0.0",
-  "description": "API for YSWS and Hack Club events",
+  "description": "Public read-only API for Hack Club's YSWS programs",
   "main": "server.js",
   "scripts": {
     "start": "node server.js",
@@ -10,13 +10,12 @@
   "keywords": [
     "hackclub",
     "ysws",
-    "events",
+    "programs",
     "api"
   ],
   "author": "",
   "license": "MIT",
   "dependencies": {
-    "@slack/webhook": "^7.0.7",
     "@upstash/redis": "^1.36.3",
     "airtable": "^0.12.2",
     "cors": "^2.8.6",