Backlog Cleanup Master Issue

[CeloHaiTiFreClean]

Backlog Cleanup Master Issue

This issue is the master tracking issue for backlog cleanup and issue normalization across the CeloHT ecosystem.

Objectives

• Identify and remove duplicate issues.
• Close obsolete or superseded requirements.
• Correct issues that contradict the current CeloHT product and architecture direction.
• Consolidate fragmented backlog items where appropriate.
• Ensure every active issue has a clear scope, owner, priority, dependencies, and acceptance criteria.
• Ensure issues reference the current canonical CeloHT architecture and documentation.
• Prevent outdated product requirements from remaining active in the backlog.

Current Cleanup Targets

• Establish Impact Measurement and Public Reporting Framework #53 - Correct scope from "Impact Dashboard" to impact measurement/public reporting.
• Establish CeloHT Community Feedback and Product Improvement Loop #40 / Establish CeloHT Community Feedback and Product Improvement Loop #41 - Resolve duplicate community feedback issues. Keep one canonical issue and close the duplicate.
• Audit other issues for obsolete, duplicated, contradictory, or underspecified requirements.
• Verify issue references against CANONICAL_TRUTH.md.
• Verify active issues do not reintroduce obsolete wallet, governance, branding, repository, or product requirements.
• Add implementation links and validation evidence where applicable.

Rules

1. Do not introduce requirements that contradict the current CeloHT canonical documentation.
2. The CeloHT dApp does not include an Impact Dashboard.
3. Impact measurement and public reporting are documentation/reporting concerns and must not be represented as a dApp dashboard requirement.
4. Do not invent metrics, partnerships, deployments, or production capabilities.
5. Obsolete or duplicate issues should be closed with a clear explanation and reference to the canonical issue when applicable.
6. Active issues must have actionable acceptance criteria.

Acceptance Criteria

• Duplicate issues are resolved.
• Obsolete requirements are removed or closed.
• Contradictory requirements are corrected.
• Impact measurement/public reporting is separated from dApp product scope.
• Active backlog items have clear acceptance criteria.
• Remaining issues are consistent with current CeloHT canonical documentation.
• Relevant implementation PRs or validation evidence are linked.