Frontend UX: add draft-available indicator for editable preference sections

[CMI-James]

Background

Contributors need implementation-ready frontend backlog items so UI work can be picked up with clear scope and test expectations.

Feature Focus

Add the UI behavior or platform support described in the title.

Where to Implement (Exact Targets)

• apps/web/src/pages/*
• apps/web/src/components/*
• apps/web/src/styles/*
• apps/web/src/tests/*

What to Implement

• Build the feature, component, or UI pattern described in the issue title.
• Reuse shared UI or platform primitives where the change obviously belongs there.
• Handle empty, loading, disabled, and missing-data states explicitly.
• Preserve responsive behavior and accessibility expectations.

Interface / Endpoint / Method Details

• Prefer extending shared components and state primitives over page-local one-offs where practical.
• Keep props and state interfaces narrow and predictable.
• Avoid regressions in navigation, focus management, and error handling.

Acceptance Criteria

• The new UI behavior is reachable through a clear user entry point.
• Responsive and accessibility behavior remain intact.
• Existing page flows remain backward compatible.

Required Tests

• Add targeted component or integration coverage for the primary success path.
• Add at least one regression or edge-case test for empty, blocked, or fallback behavior.

Definition of Done

• The UI change is implemented and covered by tests.
• Any shared utility or component introduced by the change is exercised through representative usage.

[Johnsmichael150]

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

I would like to work on this issue.

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

[drips-wave]

Congratulations, @Johnsmichael150! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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

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