feat(routes-f): creator milestone and goal history archive endpoint

[davedumto]

Overview

Implement app/api/routes-f/creator/goals/history/route.ts for archival records of past milestones and goals.

Scope

• GET /api/routes-f/creator/goals/history — list completed/expired goals for authenticated creator
• Query params: ?type=sub_count|tip_amount|viewer_count&limit=20&cursor=

Acceptance Criteria

• Each record includes title, type, target, achieved_value, completed_at, duration_days
• Expired goals (never completed) included with status: expired
• Cursor pagination, newest first
• Route lives exclusively in app/api/routes-f/creator/goals/history/

Notes

Standalone — no dependency on other open issues.

[yusstyle]

@yusstyle has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

hello can i work on this please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @yusstyle to this issue.

[kunal-drall]

@kunal-drall has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I'll take this — standalone history endpoint.
Will implement GET with cursor pagination (newest first), type filtering, returning completed + expired goals with full metadata (title, type, target, achieved_value, completed_at, duration_days, status). Auth-gated to authenticated creator.
Experienced with Next.js API routes and paginated query patterns.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @kunal-drall to this issue.

[Wilfred007]

@Wilfred007 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

CAN I WORK ON THIS TASK?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Wilfred007 to this issue.

[Jay-Peter-Egemasi]

@Jay-Peter-Egemasi has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hey I am Jerome, and I would like to take this issue head on.

ETA: before deadline

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jay-Peter-Egemasi to this issue.

[drips-wave]

Congratulations, @Jay-Peter-Egemasi! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Jay-Peter-Egemasi: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Jay-Peter-Egemasi as part of the Stellar Wave Program's 3rd Wave 🥳

Moderator's reason: [Auto-assessed] The contributor implemented the requested creator goal history archive endpoint in PR #544, including the necessary route logic and unit tests. The PR was submitted before the assigned deadline and has been open for over 24 hours without maintainer objections, demonstrating a genuine and quality contribution that addresses the issue scope.

😎 @Jay-Peter-Egemasi: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.