- Restructure .env.example with security-focused documentation, service-specific environment file references, and AWS Secrets Manager integration - Update CLI tests workflow to single Python 3.13 version, add pytest-mock dependency, and consolidate test execution with coverage - Add comprehensive security validation to package publishing workflow with manual approval gates, secret scanning, and release
2.0 KiB
2.0 KiB
Preflight Checklist (Before Implementation)
Use this checklist before starting Stage 20 development work.
Tools & Versions
- Circom v2.2.3+ installed (
circom --version) - snarkjs installed globally (
snarkjs --help) - Node.js + npm aligned with repo version (
node -v,npm -v) - Vitest available for JS SDK tests (
npx vitest --version) - Python 3.13+ with pytest (
python --version,pytest --version) - NVIDIA drivers + CUDA installed (
nvidia-smi,nvcc --version) - Ollama installed and running (
ollama list)
Environment Sanity
.envfiles present/updated for coordinator API- Virtualenvs active (
.venvfor Python services) - npm/yarn install completed in
packages/js/aitbc-sdk - GPU available and visible via
nvidia-smi - Network access for model pulls (Ollama)
Baseline Health Checks
npm testinpackages/js/aitbc-sdkpassespytestinapps/coordinator-apipassespytestinapps/blockchain-nodepassespytestinapps/wallet-daemonpassespytestinapps/pool-hubpasses- Circom compile sanity:
circom apps/zk-circuits/receipt_simple.circom --r1cs -o /tmp/zkcheck
Data & Backup
- Backup current
.envfiles (coordinator, wallet, blockchain-node) - Snapshot existing ZK artifacts (ptau/zkey) if any
- Note current npm package version for JS SDK
Scope & Branching
- Create feature branch for Stage 20 work
- Confirm scope limited to 01–04 task files plus testing/deployment updates
- Review success metrics in
00_nextMileston.md
Hardware Notes
- Target consumer GPU list ready (e.g., RTX 3060/4070/4090)
- Test host has CUDA drivers matching target GPUs
Rollback Ready
- Plan for reverting npm publish if needed
- Alembic downgrade path verified (if new migrations)
- Feature flags identified for new endpoints
Mark items as checked before starting implementation to avoid mid-task blockers.