Exploring a local-only feedback flow for Tagtics — overkill or useful?

Tagtics Series #4 – Local Development & Feedback Flow

Today’s work was focused on improving the local development experience for Tagtics.
I started experimenting with a new package -> tentatively called tagtics-local. Its aimed at making local testing of the feedback flow smoother and safer.
The idea:
While developing locally, feedback collected from the frontend (also running on localhost) should:

• Stay on the local machine
• Be visible on a lightweight local dashboard
• Not be sent to the live backend or production dashboard
  This would let developers validate the entire feedback collection flow during development without polluting real project data.
  That said, I’m still unsure whether this needs to be a separate package or if it can (or should) live inside the existing setup. Right now, it’s an exploration more than a final decision.
  Building in public also means questioning assumption. So I’d love your thoughts:
  -> Is a dedicated local-only package useful, or am I over-engineering this?
  Still early. Still iterating. On to the next build.