Add Neon skill references and implement email sign-in component

[jtc0023]

• Create auth.md for Neon authentication references.
• Add claimable-neon.md detailing the claimable Neon project flow.
• Introduce function-triggers.md to explain function triggers setup and usage.
• Document logging capabilities in logs-loki.md for branch-scoped logs.
• Implement parse-env.md for type-safe environment variable parsing.
• Introduce sdk.md for the new @neon/sdk TypeScript client.
• Add EmailSignIn component for user authentication via email.
• Include light mode logo SVG for branding.
• Initialize neon.ts configuration with authentication enabled.

[vercel]

@jtc0023 is attempting to deploy a commit to the Comp AI - PoC Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Retargeted this onto main.

release is the default branch so that a plain clone runs the last tagged release, but nothing merges into it — it is fast-forwarded onto the tag by the Release workflow and that is all. Changes go to main, and reach release when a release is cut.

Nothing is wrong with your branch. If the diff now shows commits that are already on main, rebase and force-push:

git fetch origin main
git rebase origin/main
git push --force-with-lease