Frontend platform: add reusable timeline component for transaction and event history

[CMI-James]

Background

The app could reuse a single timeline visual for transaction history, event streams, and future audit-style views instead of duplicating list treatments.

Feature Focus

Shared timeline component

Where to Implement (Exact Targets)

• frontend/src/components/v1/TxStatusPanel.tsx
• frontend/src/components/v1/ContractEventFeed.tsx
• frontend/src/index.css
• frontend/tests/components/v1/ContractEventFeed.test.tsx

What to Implement

• Add a reusable timeline component or composition pattern.
• Support status, timestamp, and metadata slots.
• Keep the component suitable for both compact and detail-rich history views.

Interface / Endpoint / Method Details

• The timeline should remain expressive without becoming visually noisy.
• API design should avoid over-specializing to a single use case.
• Accessibility semantics should remain intact for ordered historical content.

Acceptance Criteria

• Implementation is complete in the specified files/modules.
• Behavior is reachable through the intended route, component, or contract method.
• Existing unaffected behavior remains stable.
• Code quality checks pass for the touched subsystem.

Required Tests

• Add tests for timeline item rendering, ordering, and adaptation across at least two current use cases.

Definition of Done

• PR includes implementation, tests, and any necessary docs updates.
• Reviewer can verify behavior directly from code and tests without assumptions.

[Uche44]

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

Good day.

Let me handle this for you.

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

[Ejere]

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

can I work on this issue?

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

[drips-wave]

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

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