Backend: Add routes-f job status endpoint

[davedumto]

Summary

Add a Routes-F job status endpoint.

Requirements

• GET /api/routes-f/jobs/[id] returns queued|running|complete|failed.
• Returns 404 if job missing.
• Uses in-memory store for now.

Notes

• Keep status model extensible.

Acceptance Criteria

• Tests cover each status case.
• Missing job returns 404.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Christopherdominic]

@Christopherdominic has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi 👋

I’d like to work on this issue.

I’ve reviewed the description and acceptance criteria, and I’m confident I can implement the required changes following the project’s guidelines and coding standards. I’ll ensure proper testing and documentation where applicable.

Please assign this issue to me — I’ll get started right away. 🚀

Thank you!

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

[Bug-Hunter-X]

@Bug-Hunter-X has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello, kindly assign this isssue to me,

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bug-Hunter-X to this issue.

[Jay-Peter-Egemasi]

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

Hi, I’m Jerome, a backend developer experienced in building RESTful APIs and writing well-tested endpoints.

I’d like to work on issue #306 (Routes-F job status endpoint).

I will implement the GET /api/routes-f/jobs/[id] endpoint using an in-memory store for now, ensuring it returns queued, running, complete, or failed, and properly handles missing jobs with a 404 response. The status model will be structured to remain extensible for future updates.

I’ll also include tests covering all status cases and the 404 scenario.

Estimated completion time: within 24–48 hours.

ℹ️ 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 February 26, 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 issued 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 completed by @Jay-Peter-Egemasi as part of the Stellar Wave Program's 2nd Wave 🥳

😎 @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. You can also Leave a review to share your experience working on this issue.

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