Update the proposal detail page's activity timeline to log owner-weight-change events in the chronological history

[thegreatfeez]

Frontend — Dashboard

Summary

When an owner's voting weight changes, that event should be visible in a proposal's history. This adds owner-weight-change events to the proposal detail page's activity timeline so the full sequence of governance actions is auditable in one place.

Background

The proposal detail page in frontend/src/pages/ProposalDetailPage.tsx is where a proposal's activity timeline lists each approve, revoke, and execute event in chronological order. The weighted-governance model emits an event whenever an owner's voting weight is updated, but that event type is not read into the timeline, so weight changes are invisible in the proposal's history.

What Needs to Be Done

1. Extend the proposal detail page's activity timeline so it also includes owner-weight-change events, interleaved in correct chronological order with the existing approve, revoke, and execute entries.
2. Render each weight-change entry with a clear label naming the affected owner and showing the old and new weight.
3. Make sure the timeline still reads correctly for proposals that mix approvals, revocations, execution, and weight-change events, as well as proposals with none.

Acceptance Criteria

• The activity timeline displays owner-weight-change events alongside approve, revoke, and execute events.
• Weight-change entries appear in the correct chronological position.
• Each weight-change entry names the affected owner and shows the old and new weight.
• Proposals with no weight-change events look unchanged.

Files to Look At

• frontend/src/pages/ProposalDetailPage.tsx — the proposal detail view and its activity timeline
• frontend/src/lib/contract.ts — on-chain event reads
• frontend/src/hooks/useContract.ts — assembles per-proposal data

Difficulty: Medium

[ByteForce-Labs]

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

Hello, I'm requesting an assignment for this issue and will make sure the implementation meets your standards.

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

[Silver36-ship-it]

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

I would love to work on this professionally, please assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Silver36-ship-it to this issue.

[drips-wave]

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

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