feat(voting): 5 votes per hackathon + redesigned results podium by agustinkassis · Pull Request #41 · lacrypta/lacrypta-dev

agustinkassis · 2026-06-23T21:01:54Z

What

Two voting-experience changes:

1. Vote budget: 1 → 5 votes per hackathon

A voter's budget is now VOTES_PER_HACKATHON (5) per distinct hackathon they participated in (was 1). This lets voters spread their votes across several different projects instead of being forced to back a single one.

Added the VOTES_PER_HACKATHON constant in lib/voting.ts and applied it in buildEligibleVoters (both the new-voter and the merge-dedupe branches).
/api/dev/soldiers and the DEV bar 🗳 count read the same function, so they update automatically.
Open/closed voting copy now reads "5 votos por hackatón…" via the same constant (no string drift).

2. Redesigned closed-results hero (`VotingHero`)

The published-results hero now showcases up to 6 winners with their prizes:

Top 3 on a podium — gold/silver/bronze cards, 1st centered and larger with a "Ganador" badge.
Positions 4–6 as a numbered list below.
Each entry shows its prize (from the program's 6-slot ladder: 400k/250k/150k/100k/60k/40k) and its vote count.
Removed the grid/checkerboard backdrop — kept the soft glow + top accent line for a cleaner look.

Why

1 vote per hackathon made every ballot all-or-nothing; 5 votes enables meaningful preference spreading across projects.
The old closed hero was a small 3-item side list with no prizes; the podium reads as a proper results celebration and surfaces the prize ladder.

Reviewer notes

prizeForPosition/formatSats are reused from lib/hackathons.ts (the program's existing prize distribution) — no new prize source.
The closed hero gracefully handles fewer than 6 winners (shows whatever has votes) and a 0-winner edge case.
Scope: this PR contains only the shippable feature work. The e2e test scaffolding used this session (a throwaway local "E2E TEST" hackathon, a retargeted dev seeder, and scripts/e2e-*.mjs helpers) was intentionally excluded so nothing test-only reaches production.

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

New Features
- Increased voting power: Users now receive 5 votes per hackathon participated in (previously 1).
- Enhanced results display: Winner showcase now supports up to 6 winners with improved visual hierarchy—featuring a podium for the top 3 and a runners-up section for positions 4–6, including vote counts and prize amounts where applicable.

Vote budget is now VOTES_PER_HACKATHON (5) per distinct hackathon a voter participated in, so voters can spread their votes across several projects instead of backing a single one. Centralized as a constant in lib/voting.ts (buildEligibleVoters) and reused in the open/closed voting copy. Redesigned the closed-results hero (VotingHero): - top 3 winners on a gold/silver/bronze podium (1st centered + "Ganador" badge), positions 4-6 as a numbered list - each winner shows its prize (from the program's 6-slot ladder) and votes - removed the grid/checkerboard backdrop for a cleaner look Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

vercel · 2026-06-23T21:02:00Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lacrypta-dev	Ready	Preview, Comment	Jun 23, 2026 9:02pm

coderabbitai · 2026-06-23T21:02:08Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a8b5bc7e-acaa-40cd-bb2d-469238d87094

📥 Commits

Reviewing files that changed from the base of the PR and between 9347d17 and 227a2f4.

📒 Files selected for processing (3)

app/hackathons/[id]/VotingSection.tsx
components/voting/VotingHero.tsx
lib/voting.ts

📝 Walkthrough

Walkthrough

Introduces VOTES_PER_HACKATHON = 5 constant in lib/voting.ts and scales maxVotes by it in buildEligibleVoters. The open-state UI copy in VotingSection and VotingHero is updated to interpolate this constant. VotingHero's closed-state results view is replaced with a podium (top 3) and runners-up (positions 4–6) layout using new PodiumCard and RunnerRow components.

Changes

Vote Budget Constant and Results UI

Layer / File(s)	Summary
Vote budget constant and maxVotes computation `lib/voting.ts`	Exports `VOTES_PER_HACKATHON = 5`; updates `VotingEligibleVoter.maxVotes` docs and scales `maxVotes` as `hackathons.size * VOTES_PER_HACKATHON` in both the new-entry and merge paths of `buildEligibleVoters`.
Open-state UI copy updated to VOTES_PER_HACKATHON `app/hackathons/[id]/VotingSection.tsx`, `components/voting/VotingHero.tsx`	Both components import `VOTES_PER_HACKATHON` and interpolate it into the open-voting explanatory message, removing hardcoded `"1 voto"` strings.
Closed-state podium and runners-up rendering `components/voting/VotingHero.tsx`	Removes hero backdrop grid overlay; adds module-level `MEDAL` and `RANK_TONE` constants; refactors `ClosedHero` to split winners into `podium` (top 3) and `runnersUp` (4–6); renders via new `PodiumCard` and `RunnerRow` components with `formatSats` prize display and links to project pages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 Five votes per hackathon, hooray!
The podium gleams in gold array,
Runners-up proudly take their place,
No more hardcoded "1" to trace.
With VOTES_PER_HACKATHON in the lead,
This bunny's happy — vote indeed! 🏆

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 62.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely summarizes both main changes: the vote budget increase (5 per hackathon) and the redesigned results podium, directly matching the PR objectives and changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feat/voting-budget-and-results-podium

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

agustinkassis · 2026-06-23T21:01:54Z

What

Two voting-experience changes:

1. Vote budget: 1 → 5 votes per hackathon

A voter's budget is now VOTES_PER_HACKATHON (5) per distinct hackathon they participated in (was 1). This lets voters spread their votes across several different projects instead of being forced to back a single one.

Added the VOTES_PER_HACKATHON constant in lib/voting.ts and applied it in buildEligibleVoters (both the new-voter and the merge-dedupe branches).
/api/dev/soldiers and the DEV bar 🗳 count read the same function, so they update automatically.
Open/closed voting copy now reads "5 votos por hackatón…" via the same constant (no string drift).

2. Redesigned closed-results hero (`VotingHero`)

The published-results hero now showcases up to 6 winners with their prizes:

Top 3 on a podium — gold/silver/bronze cards, 1st centered and larger with a "Ganador" badge.
Positions 4–6 as a numbered list below.
Each entry shows its prize (from the program's 6-slot ladder: 400k/250k/150k/100k/60k/40k) and its vote count.
Removed the grid/checkerboard backdrop — kept the soft glow + top accent line for a cleaner look.

Why

1 vote per hackathon made every ballot all-or-nothing; 5 votes enables meaningful preference spreading across projects.
The old closed hero was a small 3-item side list with no prizes; the podium reads as a proper results celebration and surfaces the prize ladder.

Reviewer notes

prizeForPosition/formatSats are reused from lib/hackathons.ts (the program's existing prize distribution) — no new prize source.
The closed hero gracefully handles fewer than 6 winners (shows whatever has votes) and a 0-winner edge case.
Scope: this PR contains only the shippable feature work. The e2e test scaffolding used this session (a throwaway local "E2E TEST" hackathon, a retargeted dev seeder, and scripts/e2e-*.mjs helpers) was intentionally excluded so nothing test-only reaches production.

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

New Features
- Increased voting power: Users now receive 5 votes per hackathon participated in (previously 1).
- Enhanced results display: Winner showcase now supports up to 6 winners with improved visual hierarchy—featuring a podium for the top 3 and a runners-up section for positions 4–6, including vote counts and prize amounts where applicable.

Vote budget is now VOTES_PER_HACKATHON (5) per distinct hackathon a voter participated in, so voters can spread their votes across several projects instead of backing a single one. Centralized as a constant in lib/voting.ts (buildEligibleVoters) and reused in the open/closed voting copy. Redesigned the closed-results hero (VotingHero): - top 3 winners on a gold/silver/bronze podium (1st centered + "Ganador" badge), positions 4-6 as a numbered list - each winner shows its prize (from the program's 6-slot ladder) and votes - removed the grid/checkerboard backdrop for a cleaner look Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

vercel · 2026-06-23T21:02:00Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lacrypta-dev	Ready	Preview, Comment	Jun 23, 2026 9:02pm

coderabbitai · 2026-06-23T21:02:08Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a8b5bc7e-acaa-40cd-bb2d-469238d87094

📥 Commits

Reviewing files that changed from the base of the PR and between 9347d17 and 227a2f4.

📒 Files selected for processing (3)

app/hackathons/[id]/VotingSection.tsx
components/voting/VotingHero.tsx
lib/voting.ts

📝 Walkthrough

Walkthrough

Introduces VOTES_PER_HACKATHON = 5 constant in lib/voting.ts and scales maxVotes by it in buildEligibleVoters. The open-state UI copy in VotingSection and VotingHero is updated to interpolate this constant. VotingHero's closed-state results view is replaced with a podium (top 3) and runners-up (positions 4–6) layout using new PodiumCard and RunnerRow components.

Changes

Vote Budget Constant and Results UI

Layer / File(s)	Summary
Vote budget constant and maxVotes computation `lib/voting.ts`	Exports `VOTES_PER_HACKATHON = 5`; updates `VotingEligibleVoter.maxVotes` docs and scales `maxVotes` as `hackathons.size * VOTES_PER_HACKATHON` in both the new-entry and merge paths of `buildEligibleVoters`.
Open-state UI copy updated to VOTES_PER_HACKATHON `app/hackathons/[id]/VotingSection.tsx`, `components/voting/VotingHero.tsx`	Both components import `VOTES_PER_HACKATHON` and interpolate it into the open-voting explanatory message, removing hardcoded `"1 voto"` strings.
Closed-state podium and runners-up rendering `components/voting/VotingHero.tsx`	Removes hero backdrop grid overlay; adds module-level `MEDAL` and `RANK_TONE` constants; refactors `ClosedHero` to split winners into `podium` (top 3) and `runnersUp` (4–6); renders via new `PodiumCard` and `RunnerRow` components with `formatSats` prize display and links to project pages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 Five votes per hackathon, hooray!
The podium gleams in gold array,
Runners-up proudly take their place,
No more hardcoded "1" to trace.
With VOTES_PER_HACKATHON in the lead,
This bunny's happy — vote indeed! 🏆

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 62.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely summarizes both main changes: the vote budget increase (5 per hackathon) and the redesigned results podium, directly matching the PR objectives and changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feat/voting-budget-and-results-podium

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

agustinkassis · 2026-06-23T21:01:54Z

What

Two voting-experience changes:

1. Vote budget: 1 → 5 votes per hackathon

A voter's budget is now VOTES_PER_HACKATHON (5) per distinct hackathon they participated in (was 1). This lets voters spread their votes across several different projects instead of being forced to back a single one.

Added the VOTES_PER_HACKATHON constant in lib/voting.ts and applied it in buildEligibleVoters (both the new-voter and the merge-dedupe branches).
/api/dev/soldiers and the DEV bar 🗳 count read the same function, so they update automatically.
Open/closed voting copy now reads "5 votos por hackatón…" via the same constant (no string drift).

2. Redesigned closed-results hero (`VotingHero`)

The published-results hero now showcases up to 6 winners with their prizes:

Top 3 on a podium — gold/silver/bronze cards, 1st centered and larger with a "Ganador" badge.
Positions 4–6 as a numbered list below.
Each entry shows its prize (from the program's 6-slot ladder: 400k/250k/150k/100k/60k/40k) and its vote count.
Removed the grid/checkerboard backdrop — kept the soft glow + top accent line for a cleaner look.

Why

1 vote per hackathon made every ballot all-or-nothing; 5 votes enables meaningful preference spreading across projects.
The old closed hero was a small 3-item side list with no prizes; the podium reads as a proper results celebration and surfaces the prize ladder.

Reviewer notes

prizeForPosition/formatSats are reused from lib/hackathons.ts (the program's existing prize distribution) — no new prize source.
The closed hero gracefully handles fewer than 6 winners (shows whatever has votes) and a 0-winner edge case.
Scope: this PR contains only the shippable feature work. The e2e test scaffolding used this session (a throwaway local "E2E TEST" hackathon, a retargeted dev seeder, and scripts/e2e-*.mjs helpers) was intentionally excluded so nothing test-only reaches production.

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

New Features
- Increased voting power: Users now receive 5 votes per hackathon participated in (previously 1).
- Enhanced results display: Winner showcase now supports up to 6 winners with improved visual hierarchy—featuring a podium for the top 3 and a runners-up section for positions 4–6, including vote counts and prize amounts where applicable.

Vote budget is now VOTES_PER_HACKATHON (5) per distinct hackathon a voter participated in, so voters can spread their votes across several projects instead of backing a single one. Centralized as a constant in lib/voting.ts (buildEligibleVoters) and reused in the open/closed voting copy. Redesigned the closed-results hero (VotingHero): - top 3 winners on a gold/silver/bronze podium (1st centered + "Ganador" badge), positions 4-6 as a numbered list - each winner shows its prize (from the program's 6-slot ladder) and votes - removed the grid/checkerboard backdrop for a cleaner look Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

vercel · 2026-06-23T21:02:00Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lacrypta-dev	Ready	Preview, Comment	Jun 23, 2026 9:02pm

coderabbitai · 2026-06-23T21:02:08Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a8b5bc7e-acaa-40cd-bb2d-469238d87094

📥 Commits

Reviewing files that changed from the base of the PR and between 9347d17 and 227a2f4.

📒 Files selected for processing (3)

app/hackathons/[id]/VotingSection.tsx
components/voting/VotingHero.tsx
lib/voting.ts

📝 Walkthrough

Walkthrough

Introduces VOTES_PER_HACKATHON = 5 constant in lib/voting.ts and scales maxVotes by it in buildEligibleVoters. The open-state UI copy in VotingSection and VotingHero is updated to interpolate this constant. VotingHero's closed-state results view is replaced with a podium (top 3) and runners-up (positions 4–6) layout using new PodiumCard and RunnerRow components.

Changes

Vote Budget Constant and Results UI

Layer / File(s)	Summary
Vote budget constant and maxVotes computation `lib/voting.ts`	Exports `VOTES_PER_HACKATHON = 5`; updates `VotingEligibleVoter.maxVotes` docs and scales `maxVotes` as `hackathons.size * VOTES_PER_HACKATHON` in both the new-entry and merge paths of `buildEligibleVoters`.
Open-state UI copy updated to VOTES_PER_HACKATHON `app/hackathons/[id]/VotingSection.tsx`, `components/voting/VotingHero.tsx`	Both components import `VOTES_PER_HACKATHON` and interpolate it into the open-voting explanatory message, removing hardcoded `"1 voto"` strings.
Closed-state podium and runners-up rendering `components/voting/VotingHero.tsx`	Removes hero backdrop grid overlay; adds module-level `MEDAL` and `RANK_TONE` constants; refactors `ClosedHero` to split winners into `podium` (top 3) and `runnersUp` (4–6); renders via new `PodiumCard` and `RunnerRow` components with `formatSats` prize display and links to project pages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 Five votes per hackathon, hooray!
The podium gleams in gold array,
Runners-up proudly take their place,
No more hardcoded "1" to trace.
With VOTES_PER_HACKATHON in the lead,
This bunny's happy — vote indeed! 🏆

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 62.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely summarizes both main changes: the vote budget increase (5 per hackathon) and the redesigned results podium, directly matching the PR objectives and changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feat/voting-budget-and-results-podium

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

agustinkassis · 2026-06-23T21:01:54Z

What

Two voting-experience changes:

1. Vote budget: 1 → 5 votes per hackathon

A voter's budget is now VOTES_PER_HACKATHON (5) per distinct hackathon they participated in (was 1). This lets voters spread their votes across several different projects instead of being forced to back a single one.

Added the VOTES_PER_HACKATHON constant in lib/voting.ts and applied it in buildEligibleVoters (both the new-voter and the merge-dedupe branches).
/api/dev/soldiers and the DEV bar 🗳 count read the same function, so they update automatically.
Open/closed voting copy now reads "5 votos por hackatón…" via the same constant (no string drift).

2. Redesigned closed-results hero (`VotingHero`)

The published-results hero now showcases up to 6 winners with their prizes:

Top 3 on a podium — gold/silver/bronze cards, 1st centered and larger with a "Ganador" badge.
Positions 4–6 as a numbered list below.
Each entry shows its prize (from the program's 6-slot ladder: 400k/250k/150k/100k/60k/40k) and its vote count.
Removed the grid/checkerboard backdrop — kept the soft glow + top accent line for a cleaner look.

Why

1 vote per hackathon made every ballot all-or-nothing; 5 votes enables meaningful preference spreading across projects.
The old closed hero was a small 3-item side list with no prizes; the podium reads as a proper results celebration and surfaces the prize ladder.

Reviewer notes

prizeForPosition/formatSats are reused from lib/hackathons.ts (the program's existing prize distribution) — no new prize source.
The closed hero gracefully handles fewer than 6 winners (shows whatever has votes) and a 0-winner edge case.
Scope: this PR contains only the shippable feature work. The e2e test scaffolding used this session (a throwaway local "E2E TEST" hackathon, a retargeted dev seeder, and scripts/e2e-*.mjs helpers) was intentionally excluded so nothing test-only reaches production.

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

New Features
- Increased voting power: Users now receive 5 votes per hackathon participated in (previously 1).
- Enhanced results display: Winner showcase now supports up to 6 winners with improved visual hierarchy—featuring a podium for the top 3 and a runners-up section for positions 4–6, including vote counts and prize amounts where applicable.

Vote budget is now VOTES_PER_HACKATHON (5) per distinct hackathon a voter participated in, so voters can spread their votes across several projects instead of backing a single one. Centralized as a constant in lib/voting.ts (buildEligibleVoters) and reused in the open/closed voting copy. Redesigned the closed-results hero (VotingHero): - top 3 winners on a gold/silver/bronze podium (1st centered + "Ganador" badge), positions 4-6 as a numbered list - each winner shows its prize (from the program's 6-slot ladder) and votes - removed the grid/checkerboard backdrop for a cleaner look Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

vercel · 2026-06-23T21:02:00Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lacrypta-dev	Ready	Preview, Comment	Jun 23, 2026 9:02pm

coderabbitai · 2026-06-23T21:02:08Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a8b5bc7e-acaa-40cd-bb2d-469238d87094

📥 Commits

Reviewing files that changed from the base of the PR and between 9347d17 and 227a2f4.

📒 Files selected for processing (3)

app/hackathons/[id]/VotingSection.tsx
components/voting/VotingHero.tsx
lib/voting.ts

📝 Walkthrough

Walkthrough

Introduces VOTES_PER_HACKATHON = 5 constant in lib/voting.ts and scales maxVotes by it in buildEligibleVoters. The open-state UI copy in VotingSection and VotingHero is updated to interpolate this constant. VotingHero's closed-state results view is replaced with a podium (top 3) and runners-up (positions 4–6) layout using new PodiumCard and RunnerRow components.

Changes

Vote Budget Constant and Results UI

Layer / File(s)	Summary
Vote budget constant and maxVotes computation `lib/voting.ts`	Exports `VOTES_PER_HACKATHON = 5`; updates `VotingEligibleVoter.maxVotes` docs and scales `maxVotes` as `hackathons.size * VOTES_PER_HACKATHON` in both the new-entry and merge paths of `buildEligibleVoters`.
Open-state UI copy updated to VOTES_PER_HACKATHON `app/hackathons/[id]/VotingSection.tsx`, `components/voting/VotingHero.tsx`	Both components import `VOTES_PER_HACKATHON` and interpolate it into the open-voting explanatory message, removing hardcoded `"1 voto"` strings.
Closed-state podium and runners-up rendering `components/voting/VotingHero.tsx`	Removes hero backdrop grid overlay; adds module-level `MEDAL` and `RANK_TONE` constants; refactors `ClosedHero` to split winners into `podium` (top 3) and `runnersUp` (4–6); renders via new `PodiumCard` and `RunnerRow` components with `formatSats` prize display and links to project pages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 Five votes per hackathon, hooray!
The podium gleams in gold array,
Runners-up proudly take their place,
No more hardcoded "1" to trace.
With VOTES_PER_HACKATHON in the lead,
This bunny's happy — vote indeed! 🏆

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 62.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely summarizes both main changes: the vote budget increase (5 per hackathon) and the redesigned results podium, directly matching the PR objectives and changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feat/voting-budget-and-results-podium

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

agustinkassis · 2026-06-23T21:01:54Z

What

Two voting-experience changes:

1. Vote budget: 1 → 5 votes per hackathon

A voter's budget is now VOTES_PER_HACKATHON (5) per distinct hackathon they participated in (was 1). This lets voters spread their votes across several different projects instead of being forced to back a single one.

Added the VOTES_PER_HACKATHON constant in lib/voting.ts and applied it in buildEligibleVoters (both the new-voter and the merge-dedupe branches).
/api/dev/soldiers and the DEV bar 🗳 count read the same function, so they update automatically.
Open/closed voting copy now reads "5 votos por hackatón…" via the same constant (no string drift).

2. Redesigned closed-results hero (`VotingHero`)

The published-results hero now showcases up to 6 winners with their prizes:

Top 3 on a podium — gold/silver/bronze cards, 1st centered and larger with a "Ganador" badge.
Positions 4–6 as a numbered list below.
Each entry shows its prize (from the program's 6-slot ladder: 400k/250k/150k/100k/60k/40k) and its vote count.
Removed the grid/checkerboard backdrop — kept the soft glow + top accent line for a cleaner look.

Why

1 vote per hackathon made every ballot all-or-nothing; 5 votes enables meaningful preference spreading across projects.
The old closed hero was a small 3-item side list with no prizes; the podium reads as a proper results celebration and surfaces the prize ladder.

Reviewer notes

prizeForPosition/formatSats are reused from lib/hackathons.ts (the program's existing prize distribution) — no new prize source.
The closed hero gracefully handles fewer than 6 winners (shows whatever has votes) and a 0-winner edge case.
Scope: this PR contains only the shippable feature work. The e2e test scaffolding used this session (a throwaway local "E2E TEST" hackathon, a retargeted dev seeder, and scripts/e2e-*.mjs helpers) was intentionally excluded so nothing test-only reaches production.

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

New Features
- Increased voting power: Users now receive 5 votes per hackathon participated in (previously 1).
- Enhanced results display: Winner showcase now supports up to 6 winners with improved visual hierarchy—featuring a podium for the top 3 and a runners-up section for positions 4–6, including vote counts and prize amounts where applicable.

Vote budget is now VOTES_PER_HACKATHON (5) per distinct hackathon a voter participated in, so voters can spread their votes across several projects instead of backing a single one. Centralized as a constant in lib/voting.ts (buildEligibleVoters) and reused in the open/closed voting copy. Redesigned the closed-results hero (VotingHero): - top 3 winners on a gold/silver/bronze podium (1st centered + "Ganador" badge), positions 4-6 as a numbered list - each winner shows its prize (from the program's 6-slot ladder) and votes - removed the grid/checkerboard backdrop for a cleaner look Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

vercel · 2026-06-23T21:02:00Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lacrypta-dev	Ready	Preview, Comment	Jun 23, 2026 9:02pm

coderabbitai · 2026-06-23T21:02:08Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a8b5bc7e-acaa-40cd-bb2d-469238d87094

📥 Commits

Reviewing files that changed from the base of the PR and between 9347d17 and 227a2f4.

📒 Files selected for processing (3)

app/hackathons/[id]/VotingSection.tsx
components/voting/VotingHero.tsx
lib/voting.ts

📝 Walkthrough

Walkthrough

Introduces VOTES_PER_HACKATHON = 5 constant in lib/voting.ts and scales maxVotes by it in buildEligibleVoters. The open-state UI copy in VotingSection and VotingHero is updated to interpolate this constant. VotingHero's closed-state results view is replaced with a podium (top 3) and runners-up (positions 4–6) layout using new PodiumCard and RunnerRow components.

Changes

Vote Budget Constant and Results UI

Layer / File(s)	Summary
Vote budget constant and maxVotes computation `lib/voting.ts`	Exports `VOTES_PER_HACKATHON = 5`; updates `VotingEligibleVoter.maxVotes` docs and scales `maxVotes` as `hackathons.size * VOTES_PER_HACKATHON` in both the new-entry and merge paths of `buildEligibleVoters`.
Open-state UI copy updated to VOTES_PER_HACKATHON `app/hackathons/[id]/VotingSection.tsx`, `components/voting/VotingHero.tsx`	Both components import `VOTES_PER_HACKATHON` and interpolate it into the open-voting explanatory message, removing hardcoded `"1 voto"` strings.
Closed-state podium and runners-up rendering `components/voting/VotingHero.tsx`	Removes hero backdrop grid overlay; adds module-level `MEDAL` and `RANK_TONE` constants; refactors `ClosedHero` to split winners into `podium` (top 3) and `runnersUp` (4–6); renders via new `PodiumCard` and `RunnerRow` components with `formatSats` prize display and links to project pages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 Five votes per hackathon, hooray!
The podium gleams in gold array,
Runners-up proudly take their place,
No more hardcoded "1" to trace.
With VOTES_PER_HACKATHON in the lead,
This bunny's happy — vote indeed! 🏆

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 62.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely summarizes both main changes: the vote budget increase (5 per hackathon) and the redesigned results podium, directly matching the PR objectives and changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feat/voting-budget-and-results-podium

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

agustinkassis · 2026-06-23T21:01:54Z

What

Two voting-experience changes:

1. Vote budget: 1 → 5 votes per hackathon

A voter's budget is now VOTES_PER_HACKATHON (5) per distinct hackathon they participated in (was 1). This lets voters spread their votes across several different projects instead of being forced to back a single one.

Added the VOTES_PER_HACKATHON constant in lib/voting.ts and applied it in buildEligibleVoters (both the new-voter and the merge-dedupe branches).
/api/dev/soldiers and the DEV bar 🗳 count read the same function, so they update automatically.
Open/closed voting copy now reads "5 votos por hackatón…" via the same constant (no string drift).

2. Redesigned closed-results hero (`VotingHero`)

The published-results hero now showcases up to 6 winners with their prizes:

Top 3 on a podium — gold/silver/bronze cards, 1st centered and larger with a "Ganador" badge.
Positions 4–6 as a numbered list below.
Each entry shows its prize (from the program's 6-slot ladder: 400k/250k/150k/100k/60k/40k) and its vote count.
Removed the grid/checkerboard backdrop — kept the soft glow + top accent line for a cleaner look.

Why

1 vote per hackathon made every ballot all-or-nothing; 5 votes enables meaningful preference spreading across projects.
The old closed hero was a small 3-item side list with no prizes; the podium reads as a proper results celebration and surfaces the prize ladder.

Reviewer notes

prizeForPosition/formatSats are reused from lib/hackathons.ts (the program's existing prize distribution) — no new prize source.
The closed hero gracefully handles fewer than 6 winners (shows whatever has votes) and a 0-winner edge case.
Scope: this PR contains only the shippable feature work. The e2e test scaffolding used this session (a throwaway local "E2E TEST" hackathon, a retargeted dev seeder, and scripts/e2e-*.mjs helpers) was intentionally excluded so nothing test-only reaches production.

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

New Features
- Increased voting power: Users now receive 5 votes per hackathon participated in (previously 1).
- Enhanced results display: Winner showcase now supports up to 6 winners with improved visual hierarchy—featuring a podium for the top 3 and a runners-up section for positions 4–6, including vote counts and prize amounts where applicable.

Vote budget is now VOTES_PER_HACKATHON (5) per distinct hackathon a voter participated in, so voters can spread their votes across several projects instead of backing a single one. Centralized as a constant in lib/voting.ts (buildEligibleVoters) and reused in the open/closed voting copy. Redesigned the closed-results hero (VotingHero): - top 3 winners on a gold/silver/bronze podium (1st centered + "Ganador" badge), positions 4-6 as a numbered list - each winner shows its prize (from the program's 6-slot ladder) and votes - removed the grid/checkerboard backdrop for a cleaner look Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

vercel · 2026-06-23T21:02:00Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lacrypta-dev	Ready	Preview, Comment	Jun 23, 2026 9:02pm

coderabbitai · 2026-06-23T21:02:08Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a8b5bc7e-acaa-40cd-bb2d-469238d87094

📥 Commits

Reviewing files that changed from the base of the PR and between 9347d17 and 227a2f4.

📒 Files selected for processing (3)

app/hackathons/[id]/VotingSection.tsx
components/voting/VotingHero.tsx
lib/voting.ts

📝 Walkthrough

Walkthrough

Introduces VOTES_PER_HACKATHON = 5 constant in lib/voting.ts and scales maxVotes by it in buildEligibleVoters. The open-state UI copy in VotingSection and VotingHero is updated to interpolate this constant. VotingHero's closed-state results view is replaced with a podium (top 3) and runners-up (positions 4–6) layout using new PodiumCard and RunnerRow components.

Changes

Vote Budget Constant and Results UI

Layer / File(s)	Summary
Vote budget constant and maxVotes computation `lib/voting.ts`	Exports `VOTES_PER_HACKATHON = 5`; updates `VotingEligibleVoter.maxVotes` docs and scales `maxVotes` as `hackathons.size * VOTES_PER_HACKATHON` in both the new-entry and merge paths of `buildEligibleVoters`.
Open-state UI copy updated to VOTES_PER_HACKATHON `app/hackathons/[id]/VotingSection.tsx`, `components/voting/VotingHero.tsx`	Both components import `VOTES_PER_HACKATHON` and interpolate it into the open-voting explanatory message, removing hardcoded `"1 voto"` strings.
Closed-state podium and runners-up rendering `components/voting/VotingHero.tsx`	Removes hero backdrop grid overlay; adds module-level `MEDAL` and `RANK_TONE` constants; refactors `ClosedHero` to split winners into `podium` (top 3) and `runnersUp` (4–6); renders via new `PodiumCard` and `RunnerRow` components with `formatSats` prize display and links to project pages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 Five votes per hackathon, hooray!
The podium gleams in gold array,
Runners-up proudly take their place,
No more hardcoded "1" to trace.
With VOTES_PER_HACKATHON in the lead,
This bunny's happy — vote indeed! 🏆

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 62.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely summarizes both main changes: the vote budget increase (5 per hackathon) and the redesigned results podium, directly matching the PR objectives and changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feat/voting-budget-and-results-podium

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

agustinkassis · 2026-06-23T21:01:54Z

What

Two voting-experience changes:

1. Vote budget: 1 → 5 votes per hackathon

A voter's budget is now VOTES_PER_HACKATHON (5) per distinct hackathon they participated in (was 1). This lets voters spread their votes across several different projects instead of being forced to back a single one.

Added the VOTES_PER_HACKATHON constant in lib/voting.ts and applied it in buildEligibleVoters (both the new-voter and the merge-dedupe branches).
/api/dev/soldiers and the DEV bar 🗳 count read the same function, so they update automatically.
Open/closed voting copy now reads "5 votos por hackatón…" via the same constant (no string drift).

2. Redesigned closed-results hero (`VotingHero`)

The published-results hero now showcases up to 6 winners with their prizes:

Top 3 on a podium — gold/silver/bronze cards, 1st centered and larger with a "Ganador" badge.
Positions 4–6 as a numbered list below.
Each entry shows its prize (from the program's 6-slot ladder: 400k/250k/150k/100k/60k/40k) and its vote count.
Removed the grid/checkerboard backdrop — kept the soft glow + top accent line for a cleaner look.

Why

1 vote per hackathon made every ballot all-or-nothing; 5 votes enables meaningful preference spreading across projects.
The old closed hero was a small 3-item side list with no prizes; the podium reads as a proper results celebration and surfaces the prize ladder.

Reviewer notes

prizeForPosition/formatSats are reused from lib/hackathons.ts (the program's existing prize distribution) — no new prize source.
The closed hero gracefully handles fewer than 6 winners (shows whatever has votes) and a 0-winner edge case.
Scope: this PR contains only the shippable feature work. The e2e test scaffolding used this session (a throwaway local "E2E TEST" hackathon, a retargeted dev seeder, and scripts/e2e-*.mjs helpers) was intentionally excluded so nothing test-only reaches production.

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

New Features
- Increased voting power: Users now receive 5 votes per hackathon participated in (previously 1).
- Enhanced results display: Winner showcase now supports up to 6 winners with improved visual hierarchy—featuring a podium for the top 3 and a runners-up section for positions 4–6, including vote counts and prize amounts where applicable.

Vote budget is now VOTES_PER_HACKATHON (5) per distinct hackathon a voter participated in, so voters can spread their votes across several projects instead of backing a single one. Centralized as a constant in lib/voting.ts (buildEligibleVoters) and reused in the open/closed voting copy. Redesigned the closed-results hero (VotingHero): - top 3 winners on a gold/silver/bronze podium (1st centered + "Ganador" badge), positions 4-6 as a numbered list - each winner shows its prize (from the program's 6-slot ladder) and votes - removed the grid/checkerboard backdrop for a cleaner look Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

vercel · 2026-06-23T21:02:00Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lacrypta-dev	Ready	Preview, Comment	Jun 23, 2026 9:02pm

coderabbitai · 2026-06-23T21:02:08Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a8b5bc7e-acaa-40cd-bb2d-469238d87094

📥 Commits

Reviewing files that changed from the base of the PR and between 9347d17 and 227a2f4.

📒 Files selected for processing (3)

app/hackathons/[id]/VotingSection.tsx
components/voting/VotingHero.tsx
lib/voting.ts

📝 Walkthrough

Walkthrough

Introduces VOTES_PER_HACKATHON = 5 constant in lib/voting.ts and scales maxVotes by it in buildEligibleVoters. The open-state UI copy in VotingSection and VotingHero is updated to interpolate this constant. VotingHero's closed-state results view is replaced with a podium (top 3) and runners-up (positions 4–6) layout using new PodiumCard and RunnerRow components.

Changes

Vote Budget Constant and Results UI

Layer / File(s)	Summary
Vote budget constant and maxVotes computation `lib/voting.ts`	Exports `VOTES_PER_HACKATHON = 5`; updates `VotingEligibleVoter.maxVotes` docs and scales `maxVotes` as `hackathons.size * VOTES_PER_HACKATHON` in both the new-entry and merge paths of `buildEligibleVoters`.
Open-state UI copy updated to VOTES_PER_HACKATHON `app/hackathons/[id]/VotingSection.tsx`, `components/voting/VotingHero.tsx`	Both components import `VOTES_PER_HACKATHON` and interpolate it into the open-voting explanatory message, removing hardcoded `"1 voto"` strings.
Closed-state podium and runners-up rendering `components/voting/VotingHero.tsx`	Removes hero backdrop grid overlay; adds module-level `MEDAL` and `RANK_TONE` constants; refactors `ClosedHero` to split winners into `podium` (top 3) and `runnersUp` (4–6); renders via new `PodiumCard` and `RunnerRow` components with `formatSats` prize display and links to project pages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 Five votes per hackathon, hooray!
The podium gleams in gold array,
Runners-up proudly take their place,
No more hardcoded "1" to trace.
With VOTES_PER_HACKATHON in the lead,
This bunny's happy — vote indeed! 🏆

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 62.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely summarizes both main changes: the vote budget increase (5 per hackathon) and the redesigned results podium, directly matching the PR objectives and changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feat/voting-budget-and-results-podium

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

agustinkassis · 2026-06-23T21:01:54Z

What

Two voting-experience changes:

1. Vote budget: 1 → 5 votes per hackathon

A voter's budget is now VOTES_PER_HACKATHON (5) per distinct hackathon they participated in (was 1). This lets voters spread their votes across several different projects instead of being forced to back a single one.

Added the VOTES_PER_HACKATHON constant in lib/voting.ts and applied it in buildEligibleVoters (both the new-voter and the merge-dedupe branches).
/api/dev/soldiers and the DEV bar 🗳 count read the same function, so they update automatically.
Open/closed voting copy now reads "5 votos por hackatón…" via the same constant (no string drift).

2. Redesigned closed-results hero (`VotingHero`)

The published-results hero now showcases up to 6 winners with their prizes:

Top 3 on a podium — gold/silver/bronze cards, 1st centered and larger with a "Ganador" badge.
Positions 4–6 as a numbered list below.
Each entry shows its prize (from the program's 6-slot ladder: 400k/250k/150k/100k/60k/40k) and its vote count.
Removed the grid/checkerboard backdrop — kept the soft glow + top accent line for a cleaner look.

Why

1 vote per hackathon made every ballot all-or-nothing; 5 votes enables meaningful preference spreading across projects.
The old closed hero was a small 3-item side list with no prizes; the podium reads as a proper results celebration and surfaces the prize ladder.

Reviewer notes

prizeForPosition/formatSats are reused from lib/hackathons.ts (the program's existing prize distribution) — no new prize source.
The closed hero gracefully handles fewer than 6 winners (shows whatever has votes) and a 0-winner edge case.
Scope: this PR contains only the shippable feature work. The e2e test scaffolding used this session (a throwaway local "E2E TEST" hackathon, a retargeted dev seeder, and scripts/e2e-*.mjs helpers) was intentionally excluded so nothing test-only reaches production.

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

New Features
- Increased voting power: Users now receive 5 votes per hackathon participated in (previously 1).
- Enhanced results display: Winner showcase now supports up to 6 winners with improved visual hierarchy—featuring a podium for the top 3 and a runners-up section for positions 4–6, including vote counts and prize amounts where applicable.

Vote budget is now VOTES_PER_HACKATHON (5) per distinct hackathon a voter participated in, so voters can spread their votes across several projects instead of backing a single one. Centralized as a constant in lib/voting.ts (buildEligibleVoters) and reused in the open/closed voting copy. Redesigned the closed-results hero (VotingHero): - top 3 winners on a gold/silver/bronze podium (1st centered + "Ganador" badge), positions 4-6 as a numbered list - each winner shows its prize (from the program's 6-slot ladder) and votes - removed the grid/checkerboard backdrop for a cleaner look Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

vercel · 2026-06-23T21:02:00Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lacrypta-dev	Ready	Preview, Comment	Jun 23, 2026 9:02pm

coderabbitai · 2026-06-23T21:02:08Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a8b5bc7e-acaa-40cd-bb2d-469238d87094

📥 Commits

Reviewing files that changed from the base of the PR and between 9347d17 and 227a2f4.

📒 Files selected for processing (3)

app/hackathons/[id]/VotingSection.tsx
components/voting/VotingHero.tsx
lib/voting.ts

📝 Walkthrough

Walkthrough

Introduces VOTES_PER_HACKATHON = 5 constant in lib/voting.ts and scales maxVotes by it in buildEligibleVoters. The open-state UI copy in VotingSection and VotingHero is updated to interpolate this constant. VotingHero's closed-state results view is replaced with a podium (top 3) and runners-up (positions 4–6) layout using new PodiumCard and RunnerRow components.

Changes

Vote Budget Constant and Results UI

Layer / File(s)	Summary
Vote budget constant and maxVotes computation `lib/voting.ts`	Exports `VOTES_PER_HACKATHON = 5`; updates `VotingEligibleVoter.maxVotes` docs and scales `maxVotes` as `hackathons.size * VOTES_PER_HACKATHON` in both the new-entry and merge paths of `buildEligibleVoters`.
Open-state UI copy updated to VOTES_PER_HACKATHON `app/hackathons/[id]/VotingSection.tsx`, `components/voting/VotingHero.tsx`	Both components import `VOTES_PER_HACKATHON` and interpolate it into the open-voting explanatory message, removing hardcoded `"1 voto"` strings.
Closed-state podium and runners-up rendering `components/voting/VotingHero.tsx`	Removes hero backdrop grid overlay; adds module-level `MEDAL` and `RANK_TONE` constants; refactors `ClosedHero` to split winners into `podium` (top 3) and `runnersUp` (4–6); renders via new `PodiumCard` and `RunnerRow` components with `formatSats` prize display and links to project pages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 Five votes per hackathon, hooray!
The podium gleams in gold array,
Runners-up proudly take their place,
No more hardcoded "1" to trace.
With VOTES_PER_HACKATHON in the lead,
This bunny's happy — vote indeed! 🏆

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 62.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely summarizes both main changes: the vote budget increase (5 per hackathon) and the redesigned results podium, directly matching the PR objectives and changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feat/voting-budget-and-results-podium

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

vercelBotdeployed to Preview June 23, 2026 21:02 View deployment

agustinkassis merged commit 82861e4 into mainJun 23, 2026
3 checks passed

This was referenced Jun 25, 2026
[codex] community voting notifications and controls #42
Merged
feat(home): gate community voting hero by viewer eligibility #44
Merged
feat(voting): auditoría de votos cerrados + podio refleja el resultado final #49
Merged

coderabbitaiBot mentioned this pull request Jul 21, 2026
Expire the home "Resultados publicados" hero one week after voting closes #71
Merged