Dc correction apply (#226)

* Fix production build: Remove hardcoded development mode from SWC config

The .swcrc file was forcing React development mode with jsxDEV transforms,
which caused 'jsxDEV is not a function' errors in production builds.
Removed the hardcoded development flag to let SWC determine mode from webpack.

* Save

* Save

* Format

* Update e2e/monitor-resize.spec.ts

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Update e2e/visualization-dev.seed.spec.ts

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: alexthemitchell

.github/FIRST_TIME_CONTRIBUTOR_CHECKLIST.md

@@ -183,7 +183,7 @@ Before submitting, verify:
 - [ ] Build succeeds
 - [ ] Documentation updated
 - [ ] Commit messages follow convention
-- [ ] No console.log statements (use console.warn/error)
+- [ ] No console.log statements (use console.info/warn/error)
 - [ ] Accessibility considered (if UI changes)
 
 ### 4. Add Yourself to Contributors

.github/agents/hardware.agent.md

@@ -12,14 +12,19 @@ You are an expert software engineering agent specializing in hardware integratio
 
 You have access to a Playwright MCP environment that is very special: it is a real, headed Chrome instance with support for all Web APIs. It also has a real HackRF One device attached.
 
+By default, the site is available at [https://localhost:8080](https://localhost:8080). Note the use of HTTPS, which is unusual for port 8080.
+
 Use all the tools available to you to accomplish the user's request. Use online documentation and search to find relevant information.
 
+Do not complete your turn until you can prove that you have fully satisfied the user's request. Use your tools to test, iterate, and validate your work, especially taking screenshots; you can analyze these photos to debug, but also to ask the user for confirmation that you have met their needs.
+
 ## Prime Directives
 
 - **Hardware Expertise**: Leverage your deep understanding of hardware protocols, interfaces, and best practices to provide accurate and efficient solutions.
 - **Problem Solving**: Approach each task methodically, breaking down complex problems into manageable parts.
 - **Code Quality**: Write clean, maintainable, and well-documented code that adheres to industry standards.
 - **Testing and Validation**: Rigorously test your solutions to ensure they work reliably with the intended hardware.
+- **Use Your Tools**: If the user asks you to look at something, be creative in how you use your tools to gather information. For example, if you need to inspect a web page, use the Playwright environment to navigate, interact with elements, and take screenshots as needed; this can be done even if the user does not explicitly request it, and in addition to reviewing code or documentation.
 - **Maximize Your Turns**: Each interaction with the User is precious. Strive to accomplish as much as possible within each turn, reducing the need for follow-up requests. If something is unclear, make a reasonable assumption based on existing documentation and proceed, rather than asking for clarification. In these cases, take as long as you need and think deeply while using all the tools available to you.
 
 ## User Request

.github/copilot-instructions.md

@@ -2,6 +2,9 @@
 - Use [`docs/decisions/`](../docs/decisions/) for architectural decision records that may inform your work.
 - Use [`docs/reference/`](../docs/reference/) for specialized domain knowledge about SDR and related technologies.
 
+- Look for existing implementations before writing new ones; there may be similar code used elsewhere and we want to minimize duplication.
+- Streamline duplicate implementations into a single, reusable implementation when possible.
+
 Check output of `npm start` to get deployed server URL (usually https://localhost:8080)
 
 - Always think step-by-step, be methodical and deliberate in your approach. Eliminate guesswork, assumptions, and shortcuts.