feat: [performance improvement] optimize navigation condition lookups

[anyulled]

💡 What: Replaced Object.entries(obj).find(...) with direct obj[key] property access in lib/shared/navigation.ts.
🎯 Why: Using Object.entries().find() dynamically looks up a value by iterating through all entries of an object. This unnecessarily allocates an array of entry tuples and performs an O(N) linear search. Direct property access achieves the same result in O(1) time without allocating intermediate structures.
📊 Impact: Eliminates O(N) linear searches and amortized O(N) array allocations during navigation generation.
🔬 Measurement: Verified that unit tests pass identically. Performance gains can be theoretically measured by profiling CPU and GC during multiple concurrent page requests that invoke navigation logic.

---

PR created automatically by Jules for task 17116299224077292302 started by @anyulled

Summary by CodeRabbit

• Documentation

  • Updated development guidelines with performance best practices for common data operations.

• Refactor

  • Optimized navigation configuration resolution for improved performance.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
devbcn-nextjs	Error		Jun 16, 2026 8:33am

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 30588910-fcc1-4e7d-9590-8cf2226fbfd7

📥 Commits

Reviewing files that changed from the base of the PR and between b2e2a82 and 9c146cc.

📒 Files selected for processing (2)

• .jules/bolt.md
• lib/shared/navigation.ts

---

📝 Walkthrough

Walkthrough

getEditionNavigation in lib/shared/navigation.ts replaces two Object.entries().find() linear scans with direct property index access: one for resolving editionCfp from cfpData and one for resolving a link's condition from the conditions map. .jules/bolt.md adds documentation of both anti-patterns.

Changes

Navigation Lookup Optimization

Layer / File(s)	Summary
Direct index lookups in getEditionNavigation and pattern docs lib/shared/navigation.ts, .jules/bolt.md	editionCfp is retrieved via cfpData[year] and link condition is resolved via direct indexing into conditions, replacing two Object.entries().find() scans. .jules/bolt.md documents both anti-patterns to avoid.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

size/size/XS

Poem

🐇 No more wandering entry by entry through maps,
A direct key lookup — no wasted laps!
cfpData[year] hops straight to the spot,
O(1) is better than searching the lot.
The bunny writes docs so the team won't forget:
Index directly — no .find() regret! 🥕

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main optimization change—replacing inefficient Object.entries().find() lookups with direct property access for O(1) performance improvement in navigation condition resolution.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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 bolt/perf-navigation-o1-lookup-17116299224077292302

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install failed: dependency version conflict. Check your lock file or package.json.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[gemini-code-assist]

Code Review

This pull request documents a performance best practice in .jules/bolt.md regarding avoiding Object.entries().find() for object property lookups, and applies this optimization in lib/shared/navigation.ts by replacing linear searches with direct property access. The review feedback correctly points out a redundant type assertion as keyof typeof conditions in lib/shared/navigation.ts that can be removed to simplify the code.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The type assertion as keyof typeof conditions is redundant. Since link.condition is typed as NavCondition (and narrowed by the preceding guard) and conditions is typed as Record<NavCondition, boolean>, TypeScript already recognizes link.condition as a valid key. Removing the assertion simplifies the code.

Suggested change

	const conditionValue = conditions[link.condition as keyof typeof conditions];
	const conditionValue = conditions[link.condition];