fix(librarian): use dynamic year instead of hardcoded 2024/2025

[minkichoe-lbox]

Summary

• Replace hardcoded year references (2024/2025) with dynamic ${new Date().getFullYear()} calculation
• Prevents prompt from becoming outdated each year

Changes

• src/agents/librarian.ts: 5 occurrences updated (lines 49, 50, 51, 52, 252)

Testing

• bun run typecheck passes
• bun run build succeeds

---

Summary by cubic

Switched the librarian agent’s date guidance to use the current year dynamically instead of hardcoded 2024/2025. This keeps search instructions and “Latest Info” queries up to date automatically.

• Bug Fixes
  • Replaced hardcoded years with new Date().getFullYear() (and -1 where needed) in date checks, search examples, and the tooling table.

^{Written for commit 47e64a4. Summary will update on new commits.}

[github-actions]

All contributors have signed the CLA. Thank you! ✅
_{Posted by the CLA Assistant Lite bot.}

[cubic-dev-ai]

1 issue found across 1 file

Confidence score: 3/5

• Escaped template literal in src/agents/librarian.ts causes the prompt to show the literal ${new Date().getFullYear()} instead of the actual year, so users will see stale text immediately.
• This is a concrete behavior regression that should be corrected before merge to avoid confusing users about the date context.
• Pay close attention to src/agents/librarian.ts - escaped template literal keeps ${new Date().getFullYear()} literal.

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="src/agents/librarian.ts">

<violation number="1" location="src/agents/librarian.ts:49">
P2: Escaped template literal prevents dynamic year; prompt contains literal `${new Date().getFullYear()}` text instead of interpolated current year.</violation>
</file>

---

Since this is your first cubic review, here's how it works:

• cubic automatically reviews your code and comments on bugs and improvements
• Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
• Ask questions if you need clarification on any suggestion

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[minkichoe-lbox]

I have read the CLA Document and I hereby sign the CLA

[kdcokenny]

Awesome, thanks!