Add Opik agent APIs, Zod schemas, in-memory store, and UI flows

[Trovic1]

Motivation

• Add a small Opik-orchestrated agent stack (Intake, Planner, Accountability, Reflection) to turn user resolutions into measurable plans and actionable check-ins.
• Provide typed, validated HTTP endpoints so frontend flows can call agents and get structured results using zod schemas.
• Make the app usable without Supabase by adding an in-memory fallback store for goals, plans, check-ins, and reflections.
• Surface the agent flows in the onboarding → planner → dashboard loop and enable check-in and weekly review flows in the UI.

Description

• Added agent types and validation in lib/agents/schemas.ts, plus prompt templates in lib/agents/prompts.ts, a safe JSON parser in lib/agents/parser.ts, and agent runners in lib/agents/runner.ts that emit traces via lib/opikClient.ts.
• Implemented API routes POST /api/agents/intake, POST /api/agents/planner, POST /api/agents/accountability, and POST /api/agents/reflection that validate input with zod and return structured JSON responses.
• Added an in-memory fallback persistence layer in lib/fallbackStore.ts and a Supabase client stub in lib/supabaseClient.ts so the app works without external storage.
• Wired frontend flows and UI components: components/OnboardingForm.tsx, AccountabilityCheckIn.tsx, ReflectionPanel.tsx, page wiring under app/app/ (onboarding, dashboard, goal detail, review), updated README.md, and added export scripts and asset tooling.

Testing

• No automated test suite was run because dependency installation and the dev server were not executed (npm install blocked by registry 403), so build, lint, and runtime checks were not performed.
• The changes were validated by static file generation and type-annotated code, but no end-to-end or CI checks completed due to the install failure.

---

Codex Task