[Syed.Atyab@Codeline.rihal.om] Instant Gratification: Seed the Feedback Store with Dummy Data

[CodelineAtyab]

📝 User Story — Seed the Feedback Web-App with Dummy Data

📖 Description

As a backend developer, I want the feedback web-app to start up with a small, realistic set of dummy feedback so that UI teammates, testers and demo participants can interact with the “Went Well / Challenges / To Improve” board without having to wait for real submissions.

✔️ Acceptance Criteria

#	Requirement
1	Implement a pure Python function load_dummy_data() in feedback_seed.py that returns (does not print) a dictionary: { nickname ➜ [ feedback_str, … ] }.
2	The dictionary contains exactly three nicknames: alice, bob, and charlie.
3	Each nickname’s list contains three messages (one per column), prefixed as follows: • [WW] Went Well • [CH] Challenges • [TI] To Improve
4	No global variables are mutated; load_dummy_data() creates and returns a new dict on every call.
5	Add a lightweight unit test in tests/test_seed.py that asserts: • len(store) == 3 • all three category prefixes ([WW], [CH], [TI]) exist across the values.
6	Code resides on branch feature/CU-seed-dummy-data, includes docstring examples, passes pytest locally and in CI, and is merged via Pull Request after ≥ 4 reviewer approvals.
7	After merge: • Move the Sprint Backlog ticket to Done. • Post the PR link in the #dev Slack channel.

🌱 Example Returned Structure

{
    "alice":   ["[WW] Great team collaboration",
                "[CH] Difficulty setting up environment",
                "[TI] Automate deployment scripts"],

    "bob":     ["[WW] Fast code reviews",
                "[CH] Unclear API contracts",
                "[TI] Improve logging"],

    "charlie": ["[WW] Helpful documentation",
                "[CH] Flaky integration tests",
                "[TI] Reduce build time"]
}

---

Happy coding & testing!