Repository navigation
AD0: the admin-dashboard epic doc set - #1
Merged
Merged
Conversation
The admin-dashboard epic: epic.yaml (key AD, three milestones: the spec, the dashboard on Workers and Supabase, a baseline), the README, the design (the template at fe02671, how each Vercel piece maps to Cloudflare and Supabase — the per-request client through Hyperdrive, the table, the seed and the session key as migrations, GitHub sign-in connected after the build, the middleware as a Node.js proxy on Next.js 16.3.8 — the repository, the build, and the alternatives rejected: keeping Next.js 15's edge middleware, a seed route, the GitHub keys as Worker secrets), the implementation plan, the risks (the Node.js proxy on OpenNext and next-auth beta.25 under Next.js 16 among them), the as-built status, and the three task contracts. Co-Authored-By: Claude <noreply@anthropic.com> Orun-Task: AD-1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The admin-dashboard epic: epic.yaml (key AD, three milestones: the spec, the dashboard on Workers and Supabase, a baseline), the README, the design (the template at fe02671, how each Vercel piece maps to Cloudflare and Supabase — the per-request client through Hyperdrive, the table, the seed and the session key as migrations, GitHub sign-in connected after the build, the middleware as a Node.js proxy on Next.js 16.3.8 — the repository, the build, and the alternatives rejected: keeping Next.js 15's edge middleware, a seed route, the GitHub keys as Worker secrets), the implementation plan, the risks (the Node.js proxy on OpenNext and next-auth beta.25 under Next.js 16 among them), the as-built status, and the three task contracts.
🤖 Generated with Claude Code