fix: correct platform checklist with actual completed work and add missing JS platforms

Corrections:
- Clarify that Phase 1 completed Next.js, SvelteKit, Remix, NestJS (not base Node.js)
- Add Node.js base patterns as completed (established during framework work)

Additions:
- Add missing JavaScript platforms: Koa, Hapi, Deno, Bun
- Add Express for review (may have existing patterns)

Special Requirements:
- Add detailed Next.js + Vercel integration requirements
- Specify automatic-vercel.mdx page creation
- Include content structure from existing Vercel documentation
- Note Pages Router vs App Router limitations

Updated Rollout Schedule:
- Phase 1: Complete remaining JavaScript platforms first
- Phases 2-3: Continue with Python, PHP, Java, etc.

Author: smeubank

.cursor/project/features/005-unified-cron-monitoring-experience/PLATFORM-CRON-DOCS-CHECKLIST.md

@@ -10,13 +10,23 @@ This checklist guides the application of our proven cron documentation improveme
 ## 🎯 Platforms to Update
 
 ### ✅ Completed Platforms
-- [x] **JavaScript/Node.js** - ✅ **Phase 1 Complete**
-  - [x] Next.js
+- [x] **JavaScript Frameworks** - ✅ **Phase 1 Complete**
+  - [x] Next.js ⭐ *Special: Needs Vercel automatic integration page*
   - [x] SvelteKit  
   - [x] Remix
   - [x] NestJS
+  - [x] Node.js (base patterns established)
 
-### 🔄 Pending Platforms
+### 🔄 Pending JavaScript Platforms
+- [ ] **Node.js Additional Frameworks**
+  - [ ] Koa
+  - [ ] Hapi
+  - [ ] Express (basic patterns may exist, needs review)
+- [ ] **JavaScript Runtimes**
+  - [ ] Deno
+  - [ ] Bun
+
+### 🔄 Pending SDK Platforms
 
 #### High-Priority SDK Platforms
 - [ ] **Python** 
@@ -182,6 +192,55 @@ Brief intro to cron monitoring for {platform}.
 - [ ] Focus on the available functionality
 - [ ] Clear setup instructions specific to CLI/HTTP approach
 
+### ⭐ Next.js Special Requirements - Vercel Integration
+
+**Platforms:** Next.js specifically
+- [ ] **Create dedicated Vercel integration page** - `automatic-vercel.mdx`
+- [ ] **Link only from Next.js crons main page** - Not shown for other JavaScript frameworks
+- [ ] **Content source combination:**
+  - [Automatic Check-Ins (Vercel Only)](https://docs.sentry.io/platforms/javascript/guides/nextjs/crons/#automatic-check-ins-vercel-only)
+  - [Instrument Vercel Cron Jobs](https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#step-6-instrument-vercel-cron-jobs-optional)
+
+**Required Content Structure:**
+```markdown
+# Automatic Vercel Integration
+
+Automatic cron monitoring for Next.js applications deployed on Vercel.
+
+## Prerequisites
+- Next.js application hosted on Vercel
+- Vercel Cron Jobs configured in vercel.json
+- Pages Router (App Router not yet supported)
+
+## Configuration
+
+Add to your next.config.js:
+
+```javascript
+module.exports = withSentryConfig(nextConfig, {
+  automaticVercelMonitors: true,
+});
+```
+
+## How It Works
+- Instrumented cron jobs decided at runtime by examining crons field in vercel.json
+- Automatically creates Check-Ins in Sentry
+- Currently supports Pages Router only
+
+## Limitations
+- Vercel hosting required
+- Pages Router only (App Router route handlers not yet supported)
+- Requires vercel.json cron configuration
+```
+
+**Implementation Checklist:**
+- [ ] Create `docs/platforms/javascript/guides/nextjs/crons/automatic-vercel.mdx`
+- [ ] Add link from main Next.js crons page only
+- [ ] Include clear prerequisites and limitations
+- [ ] Working code example with next.config.js
+- [ ] Link to Vercel cron jobs documentation
+- [ ] Note about Pages Router vs App Router support
+
 ## 📊 Quality Assurance Checklist
 
 ### Content Quality
@@ -266,19 +325,24 @@ Brief intro to cron monitoring for {platform}.
 
 ## 🔄 Platform Rollout Schedule
 
+### JavaScript Platform Completion (Q1)
+1. **Next.js Vercel Integration** - Create automatic-vercel.mdx page
+2. **Node.js Frameworks** - Koa, Hapi, Express (review needed)
+3. **JavaScript Runtimes** - Deno, Bun
+
 ### Immediate Priority (Q1)
-1. **Python** - High usage, good auto-instrumentation support
-2. **PHP** - High usage, Laravel integration important
-3. **Java** - Enterprise focus, Spring Boot integration
+4. **Python** - High usage, good auto-instrumentation support
+5. **PHP** - High usage, Laravel integration important
+6. **Java** - Enterprise focus, Spring Boot integration
 
 ### Secondary Priority (Q2)  
-4. **Go** - Growing adoption, manual methods focus
-5. **Ruby** - Established user base
-6. **Elixir** - Smaller but dedicated user base
+7. **Go** - Growing adoption, manual methods focus
+8. **Ruby** - Established user base
+9. **Elixir** - Smaller but dedicated user base
 
 ### Final Priority (Q3)
-7. **HTTP Documentation** - Language-agnostic approach
-8. **CLI Documentation** - Developer tooling focus
+10. **HTTP Documentation** - Language-agnostic approach
+11. **CLI Documentation** - Developer tooling focus
 
 ## 📝 PR Template for Each Platform