Bench-testing, Embedded Networks, & Circuit Hacks: Centralized Open-source Research Engine
Reading paths behind BENCHCORE. Every guide below is implemented in
frontend/, api/ or runtime/ and mirrored by the checks in
Testing; TODO.md owns the roadmap.
| Goal | Read |
|---|---|
| Deliver a Node release | Node deployment and CI/CD, 0.8.0 preparation |
| Configure two-factor authentication | 0.8.0 setup and recovery |
| Run the project | Development, Troubleshooting |
| Write and publish | Authoring, Admin & themes |
| Build an API client | API, Threat model |
| Change implementation | Architecture, Testing, Contributing |
| Deploy or recover data | Operations, Security policy |
| Check the release review | Review and validation |
Documentation targets 0.8.0, with comment anti-spam, administrator TOTP, global session revocation and security history, alongside knowledge navigation and safe media maintenance. Public information, a reader guide, privacy and cookie inventory, localized error recovery and XML discovery complete the public navigation. The unified Node runtime and Vercel/private-R2 target retain their documented operational differences. Version bumps do not publish packages, tags, releases, or a hosted service automatically.
Revision tables are groundwork, not a revision product. Public moderated comments and anonymous likes are available. No email subscriptions, newsletter jobs, multi-user collaboration, or automatic revision history is promised by this documentation. Schema presence alone is not evidence of a working user-facing feature. TODO.md owns the roadmap; source and committed migrations own exact implementation details.
Examples use reserved domains and placeholder values. Never paste production passwords, cookies, private drafts, connection strings, or backups into issues.