Add submitter attribution and plugin detection

This session is being continued from a previous conversation that ran out of context. The conversation is summarized below: Analysis: Let me analyze this conversation chronologically: 1. **Initial Context**: This is a continuation of a previous conversation about building "Oneshot" - a platform for showcasing verified AI-powered code transformations. The previous session had completed Phase 1 MVP including CLI, harness extractors, web app, GitHub OAuth, comments/stars. 2. **Enhanced Session Detection**: User asked what we're detecting about the AI setup. I showed the current extractors capture prompt, model, harness, timestamp, and sessionData. User then requested enhancements: - Markdown config files (CLAUDE.md, agents.md, PRDs) - MCP server configurations - System prompts - Temperature/settings/model parameters - Token counts - Plugins (Beads, Ralph Wiggum) - NOT needed: full context, tool calls 3. **Extractor Enhancements**: I updated all three extractors (Claude Code, Cursor, Codex) to capture the enhanced data, updated the ExtractedSession interface, updated the RecipePanel component to display the new data, and updated the submit command to include enhanced fields in the payload. 4. **Deployment Setup**: User wanted to deploy to Vercel with Neon database through Vercel. We went through: - Git initialization and GitHub repo creation (jasonnovack/oneshot) - Vercel project creation with packages/web as root - Neon database via Vercel Storage integration - GitHub OAuth app setup - Environment variables configuration - Database migrations 5. **Build Errors**: Multiple build errors encountered: - Monorepo npm workspaces issue (Root Directory was packages/web but workspaces need root install) - Trailing space in outputDirectory setting - useSearchParams() needing Suspense boundary - deprecated experimental.serverActions config 6. **Successful Deployment**: After fixing errors, deployed successfully via `npx vercel build --prod && npx vercel deploy --prebuilt --prod` 7. **Current Work**: User wanted to: - Add todos for debugging auto-deploys, submit instructions, and sign-in 404 fix - Walk through submitting the first shot - We built the CLI and tried to submit, but session detection didn't find Claude Code sessions Key files modified: - `/packages/cli/src/extractors/index.ts` - Enhanced ExtractedSession interface - `/packages/cli/src/extractors/claude-code.ts` - Added markdown config, MCP, plugin detection - `/packages/cli/src/extractors/cursor.ts` - Same enhancements - `/packages/cli/src/extractors/codex.ts` - Same enhancements - `/packages/cli/src/commands/submit.ts` - Include enhanced session data in payload - `/packages/web/src/components/RecipePanel.tsx` - Display new session data - `/packages/web/src/app/auth/device/page.tsx` - Added Suspense boundary - `/packages/web/next.config.js` - Removed deprecated config - `/packages/web/drizzle.config.ts` - Fixed for older drizzle-kit version User messages to note: - User chose Neon (Recommended) for database - User chose "oneshot" as repo name, Public visibility - User provided DATABASE_URL, GitHub OAuth credentials - Vercel URL: https://oneshot-web.vercel.app - User reported multiple build errors that we fixed iteratively - User's final request: walk through submitting first shot + add todos for 3 items Pending todos: 1. Debug Vercel auto-deploys from GitHub 2. Add instructions for submitting to Oneshot 3. Fix GitHub sign-in 404 error 4. Submit first shot to test the app (in progress) Current state: CLI submit command ran but didn't auto-detect Claude Code session, falling back to manual input. We were checking ~/.claude/projects/ to see what's available. Summary: 1. Primary Request and Intent: - **Enhance session detection** to capture: markdown config files (CLAUDE.md, agents.md, PRDs), MCP server configs, system prompts, model parameters (temperature, max_tokens), token counts, and plugins (Beads, Ralph Wiggum). NOT needed: full context, tool calls. - **Deploy to Vercel** with Neon database through Vercel's integration - **Debug and fix build errors** for successful deployment - **Submit first shot** to test the app end-to-end - User explicitly requested todos: (1) Debug auto-deploys, (2) Add submit instructions, (3) Fix GitHub sign-in 404 error 2. Key Technical Concepts: - npm workspaces monorepo structure - Drizzle ORM with Neon serverless Postgres - NextAuth.js with GitHub OAuth - Next.js 14 App Router with Suspense boundaries for useSearchParams() - Vercel deployment with prebuilt artifacts - Claude Code session extraction from ~/.claude/projects/ - MCP (Model Context Protocol) server detection - Plugin detection (Beads, Ralph Wiggum) 3. Files and Code Sections: - **`/packages/cli/src/extractors/index.ts`** - Extended ExtractedSession interface with new fields: ```typescript export interface MarkdownConfig { filename: string path: string content: string } export interface McpServer { name: string command?: string args?: string[] env?: Record<string, string> url?: string } export interface PluginInfo { name: string version?: string config?: object } export interface ModelParameters { temperature?: number maxTokens?: number topP?: number topK?: number stopSequences?: string[] [key: string]: unknown } export interface TokenUsage { inputTokens?: number outputTokens?: number totalTokens?: number cacheReadTokens?: number cacheCreationTokens?: number } export interface ExtractedSession { prompt: string model: string sessionData: object timestamp: Date harness: 'claude_code' | 'cursor' | 'codex' // Enhanced fields markdownConfigs?: MarkdownConfig[] mcpServers?: McpServer[] systemPrompt?: string modelParameters?: ModelParameters tokenUsage?: TokenUsage plugins?: PluginInfo[] } ``` - **`/packages/cli/src/extractors/claude-code.ts`** - Added functions for markdown config detection, MCP server detection, plugin detection. Key functions: `findMarkdownConfigs()`, `findMcpServers()`, `detectPlugins()`. Looks for files like CLAUDE.md, agents.md, PRD.md in project root, .claude/, and docs/ directories. - **`/packages/cli/src/commands/submit.ts`** - Updated to include enhanced session data: ```typescript const enhancedSessionData = { ...session.sessionData, markdownConfigs: session.markdownConfigs, mcpServers: session.mcpServers, systemPrompt: session.systemPrompt, modelParameters: session.modelParameters, tokenUsage: session.tokenUsage, plugins: session.plugins, } ``` - **`/packages/web/src/components/RecipePanel.tsx`** - Updated to display all enhanced session data including model parameters, token usage, plugins, MCP servers, system prompts, and expandable markdown config files with copy buttons. - **`/packages/web/src/app/auth/device/page.tsx`** - Fixed Suspense boundary issue: ```typescript function DeviceAuthContent() { // ... component using useSearchParams() } export default function DeviceAuthPage() { return ( <Suspense fallback={...}> <DeviceAuthContent /> </Suspense> ) } ``` - **`/packages/web/next.config.js`** - Simplified to remove deprecated config: ```javascript const nextConfig = {} module.exports = nextConfig ``` - **`/packages/web/drizzle.config.ts`** - Fixed for drizzle-kit 0.20.18: ```typescript import 'dotenv/config' import type { Config } from 'drizzle-kit' export default { schema: './src/db/schema.ts', out: './drizzle', driver: 'pg', dbCredentials: { connectionString: process.env.DATABASE_URL!, }, } satisfies Config ``` - **`/packages/web/.env.local`** - Created with all required environment variables for local development 4. Errors and fixes: - **Monorepo install error** (`ENOENT: packages/web/packages/web/package.json`): Changed Vercel Root Directory from `packages/web` to empty, added Build Command: `npm run build --workspace=@oneshot/web`, Output Directory: `packages/web/.next` - **Trailing space in outputDirectory** (`packages/web/.next ` instead of `packages/web/.next`): User fixed in Vercel settings - **useSearchParams() without Suspense** (`should be wrapped in a suspense boundary`): Split DeviceAuthPage into DeviceAuthContent + wrapper with Suspense - **deprecated experimental.serverActions**: Removed from next.config.js (now enabled by default in Next.js 14) - **Vercel remote build still failing**: Deployed using `npx vercel build --prod && npx vercel deploy --prebuilt --prod` as workaround - **drizzle-kit push command**: Used `push:pg` instead of `push` for older version - **drizzle config connectionString**: Changed from `url` to `connectionString` for drizzle-kit 0.20.18 5. Problem Solving: - Successfully deployed to Vercel at https://oneshot-web.vercel.app - Database schema migrated to Neon - GitHub OAuth configured (though currently showing 404 - on todo list) - Currently troubleshooting: Claude Code session detection not finding sessions in `~/.claude/projects/-Users-jasonnovack-projects-oneshot/` 6. All user messages: - "What are we currently detecting about the AI setup that generated the diff?" - "Ok... I don't care so much about full context, but I do care about any markdown files that govern it... I also don't care about which tools the model chose to invoke. I do care about any MCPs that were used, any system prompts... temperature/settings/model parameters, token counts, and plugins..." - "Go ahead and implement" - "Let's back up. I have an existing Neon organization but it's through Vercel, so I need to set up this project in Vercel first. Please walk me through total hosting & deployment including Vercel, Neon from Vercel, and anything else that may be needed" - "Yes" (confirming Vercel project setup) - "DATABASE_URL = postgresql://neondb_owner:npg_n0AESb8tvCqP@ep-rapid-credit-a41mcdto-pooler.us-east-1.aws.neon.tech/neondb?sslmode=require" - "Client ID: Ov23lidM16kfK6L3pnDn Client Secret: e6748f9ad611040fb4afde5c14b8139504e8bc94" - "Done. For future reference, my vercel project url is https://oneshot-web.vercel.app" - "Build error. Is there a way I can give you access to Vercel to check for build issues yourself?" - "I changed the Root Directory and redeployed. There's another build error." - "Fixed that. Build failed" - "My limit is reset, please continue" - "Add these to-dos: 1. Let's debug to get auto deploys working. 2. Let's add instructions for someone who wants to submit to Oneshot. 3. Let's fix this: clicking Sign In with Github takes me to a 404 page. Also I'm not sure as a user when or why I would connect. But first, walk me through submitting the first shot so I can see it in the app." 7. Pending Tasks: - Debug Vercel auto-deploys from GitHub - Add instructions for submitting to Oneshot - Fix GitHub sign-in 404 error - Submit first shot to test the app (in progress) 8. Current Work: Walking through submitting the first shot. Built the CLI successfully. Ran submit command: ```bash node packages/cli/dist/index.js submit --api-url https://oneshot-web.vercel.app --type fix --title "Fix Next.js build errors" ``` Output showed session detection failed: ``` 🔍 Detecting AI harness... ⚠️ No session detected. You can enter details manually. ``` Was checking `~/.claude/projects/` to see what's available. Found directories exist: ``` -Users-jasonnovack-projects-oneshot ``` 9. Optional Next Step: Check the Claude Code session files in `~/.claude/projects/-Users-jasonnovack-projects-oneshot/` to understand why detection failed, then either fix the detection or manually submit a shot to test the app. User's exact request: "But first, walk me through submitting the first shot so I can see it in the app." Last output showed: `ls -la ~/.claude/projects/` returned directories including `-Users-jasonnovack-projects-oneshot`. Need to look inside that directory for JSONL session files.. Please continue the conversation from where we left it off without asking the user any further questions. Continue with the last task that you were asked to work on.