thePR0M3TH3ANandClaude Opus 5 75300b0c7a Use the build's own hash file, not shasum, which Windows does not have ...

With the Windows tests, build, smoke and npm-pack checks all green, the last
red on that platform was a step I wrote: `shasum -a 256`, a Unix tool.

build.mjs already writes dist/seedpass-js.mjs.sha256 over exactly the file
users execute, so the workflow reads that instead of computing it again with
whatever happens to be installed. Fewer assumptions and one fewer thing that
can differ per platform — which is the entire point of this workflow.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01Vtx94nXDmNgXEeThUZP4QN

2026-08-20 15:11:46 -04:00

..

workflows

Use the build's own hash file, not shasum, which Windows does not have

2026-08-20 15:11:46 -04:00

CODEOWNERS

Add repo memory layer and agent governance

2026-08-12 20:57:56 -04:00

dependabot.yml

chore: add dependency auditing

2025-08-03 08:32:57 -04:00