midnightntwrk/midnight-passport-sdk/devenv

devenv — is the environment ready?

Guards the loop's step (a) (docs/development-workflow.md §3): a tranche does not start against a broken environment. Check everything, report a ready/not-ready table, and fix (or hand the user the fix) before proceeding.

Checks

1. Private debts repo — the security register's home:

``bash git -C ../mn-passport-sdk-debts ls-remote origin ``

Must exist beside this repo and be pushable. If missing, ask the user to clone their private mn-passport-sdk-debts repo at that path — mn-passport-skills:security-audit cannot record findings without it, which blocks the loop.

1. HTTPS secure context — passkey / WebAuthn PRF flows require a secure

context even locally; a plain http://localhost redirect will not do for the flows under test. Local TLS via mkcert or Caddy (or the dev server's HTTPS mode); confirm the dev origin actually serves HTTPS before testing ceremony code.

1. Devnet + proof server — use the midnight-tooling:devnet skill for

status/health, the midnight-tooling:proof-server skill for the proof server (port 6300), and the midnight-wallet localnet tools as needed.

1. Compact CLI — compact check and compact self check for versions

(upgrade before compiling any .compact); the midnight-tooling:doctor skill for a full installation diagnosis.

1. Node toolchain — Node version against .nvmrc / package.json

engines once they exist; lockfile present and clean.

Output

A short table: check · status · fix (if any). Blocking items — the debts repo, and whatever the current tranche actually exercises (devnet for E2E work, HTTPS for ceremony work) — must be green before implementation starts; the rest are warnings.