feat: add reusable status system (#182)

[Justine-Ifedozie]

Description

Related Issue: Closes #

Type of Change:

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (changes to documentation only)
• Refactor (code restructuring with no functional changes)
• CI/CD (changes to build process or automation)

---

Evidence Checklist

Every pull request must satisfy the following checklist before it can be reviewed and merged.
Replace each placeholder with actual evidence. If a section is not applicable, provide a brief justification.

1. Issue Reference

• This PR references a tracked issue (e.g., Closes #123)
• Issue Link: #

2. Implementation Summary

• A clear summary of what was changed and why is provided above
• Files Changed:
  • path/to/file

3. Testing

• Tests have been added or updated to cover the changes
• All existing tests pass locally
• If tests are not applicable, explain why:

Test Commands Run:

# Paste the exact commands you ran
npm run lint
npm run build

Test Output (summary or screenshot):

4. Commands Run

• The following commands were executed locally to validate the change:

# Example:
npm install
npm run dev
npm run build
npm run lint

5. CI Status

• All CI checks pass on this PR
• No new warnings or errors were introduced
• CI Pipeline Link (if available):

6. Acceptance Criteria Coverage

• All acceptance criteria from the linked issue have been satisfied
• Criteria Mapping:

  Acceptance Criterion	Evidence
  Criterion 1	How it was met
  Criterion 2	How it was met

7. Self-Assessment

• The Contributor Self-Assessment Form has been completed and attached to this PR
• Form Location:

---

Screenshots / Recordings

Before	After

---

Reviewer Notes