Add timestamp fields to scoring interface

[AbelOsaretin]

What

getSolarData and getSatelliteData return timestamp fields, but IotInput does not include them. TypeScript allows this due to structural typing, but the interface is incomplete.

Why

If scoring logic ever needs to consider data freshness (staleness check), the timestamp is silently discarded.

Scope

• Add timestamp to IotInput interface
• Use in scoring logic if needed (e.g., staleness check)
• OR: Document that timestamps are intentionally excluded

Acceptance Criteria

• IotInput interface includes timestamp field
• Or: documentation explains why timestamps are excluded
• No breaking changes

Technical Context

• src/lib/scoring.ts:1-4 — IotInput interface
• src/routes/iot.ts:20,32 — timestamp in return values
• src/__tests__/scoring.test.ts — test fixtures don't include timestamps

[Chinonso-Peter]

@Chinonso-Peter has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Can i work on this

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

[Gbemi-programmer]

@Gbemi-programmer has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would like to work on this issue, I have read the requirements and can deliver a good Pr that satisfy this issue condition.

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

[Awosdot]

@Awosdot has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi mate, I will like to apply for this.
I intand \ to add a timestamp field to the IotInput interface in src/lib/scoring.ts, wire it through from src/routes/iot.ts where it's already returned, and use it for a stalenass check in scoring logic (or document why not, if that's the better fit). I'll update test fixtures in scoring.test.ts accordingly and confirm no breaking changes.
This is a small, well-scoped change, I should be done within an hour or two.

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

[Flashweb1]

@Flashweb1 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I'd like to take on this issue. I'll carefully analyze the existing codebase, implement a clean and efficient solution following the project's guidelines, test my changes thoroughly, and submit a high-quality pull request. Thank you for considering my application.

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

[drips-wave]

Congratulations, @Gbemi-programmer! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Gbemi-programmer: 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 completed by @Gbemi-programmer as part of the Stellar Wave Program's 7th Wave 🥳

😎 @Gbemi-programmer: 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.