🤓 Latest Submissions
SameBuild
Developers often have a green test log open while continuing to edit the file it tested. The log records a past success, but does not tell them whether that success still applies to the files in front of them. Matching logs, versions, commands and outputs by hand creates avoidable confusion during testing and release preparation. SameBuild is a local test receipt tool for developers working with a standalone Node test and one artifact file. It runs the real test process against copies of the declared files, saves their SHA-256 fingerprints with the command, outcome and output, and checks the receipt against the current files. The interface makes the distinction visible: CURRENT, STALE, FAILED or INVALID. The included sample demonstrates the full workflow. Run its tests to create a passing receipt. Change the sample artifact and the old receipt becomes stale. Run the changed version to capture a real failure. Restore the sample and run it again to obtain a new passing result. Developers can use the same runner on their own trusted files through the CLI and inspect the results in the local dashboard. The practical improvement is automatic detection of a mismatch between a past test result and the current declared inputs, with the relevant output beside it. The demonstration shows this error being caught on synthetic files; it does not claim a measured speedup. SameBuild requires Node 22 or later, has no third-party runtime dependencies, and uses no cloud service, API key, subscription or paid inference. Receipts are authenticated to the local store to detect edits. It is intentionally a small, complete workflow: trusted local tests and file drift, without claiming secure isolation, test coverage, native application certification or protection against the machine's owner.
27 Sep 2026
