Add status enum to timeline entry type in types/timeline.ts

[Kingsman-99]

Description

types/timeline.ts defines timeline entries without a status field. Consumers must infer status from the presence or absence of timestamps, which is ambiguous and inconsistent.

Acceptance Criteria

• A TimelineEntryStatus enum or string union is exported: "pending" | "in_progress" | "completed" | "failed"
• The TimelineEntry type gains a required status: TimelineEntryStatus field
• Existing fields are unchanged
• Unit tests pass

Context

• Target file: src/types/timeline.ts
• Use a string union rather than a numeric enum for JSON serialisation compatibility

[olaide2001]

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

Hi Maintainer, I will love to work on this issue because I have relevant experience on it . Pls assign it to me

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

[Primex-Tech]

@Primex-Tech has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I will love to fix this issue

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

[nakaksh]

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

Hi, I’d like to work on issue #749. My public work sample is https://github.com/nakaksh/revenue-radar-webmcp, also linked from https://nakaksh.dev. It is a reviewable Python and browser-native JavaScript WebMCP prototype with focused tests, provenance records, and an explicit human-approval boundary.

After a maintainer assigns the issue, I will inspect src/types/timeline.ts, its consumers, fixtures, and test conventions. I will export the JSON-safe string union "pending" | "in_progress" | "completed" | "failed", add the required status: TimelineEntryStatus field, preserve existing fields, and update only affected fixtures or consumers.

I will add focused coverage for each status, JSON-safe values, the required field, and unchanged existing fields. I will run npm test, npm run test:all or a targeted Vitest command covering the new test, and npm run lint; inspect the diff; and open one issue-linked PR only after the checks pass.

I use AI-assisted research, drafting, and code suggestions under direct review. I will understand every submitted change, test it myself, and will not submit untested or unreviewed model output. I can begin immediately after assignment and will wait for assignment before coding or opening a PR.

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

[Stevieoche]

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

I would love to work on this issue and give it a higher quality PR

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

[drips-wave]

Congratulations, @Stevieoche! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Stevieoche: 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 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@Stevieoche's PR #793 was approved and merged by @Kingsman-99.

🏆 @Stevieoche: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,068 total points). Track your full progress on GrantFox.

👏 Great work, @Stevieoche! Keep contributing to Stellar-split.

[drips-wave]

This issue has been completed by @Stevieoche as part of the Stellar Wave Program's 8th Wave 🥳

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