nw-cicd-and-deployment

# CI/CD Pipeline Design and Deployment Strategies ## Local Quality Gates Catch issues at the developer's machine before they reach CI. Local gates mirror the remote commit stage for fast feedback (seconds vs minutes). ### Gate Taxonomy | Gate | Trigger | Checks | Tools | |------|---------|--------|-------| | Pre-commit | `git commit` | Formatting, linting, unit tests, secrets scan | pre-commit, husky, lefthook | | Pre-push | `git push` | Integration tests, acceptance tests, coverage threshold | pre-commit (push stage), git hooks | | Local CI | Manual | Full pipeline locally | act (GitHub Actions), gitlab-runner exec | ### Design Principles - **Mirror, not duplicate**: local gates run the same checks as the remote commit stage, not additional ones. Keeps developer experience consistent with CI. - **Fast by default**: pre-commit gates target < 30 seconds. Move slow checks (integration, acceptance) to pre-push. - **Escapable with audit trail**: allow `--no-verify` for emergencies but log skips. CI remains the authoritative gate. - **Framework selection**: prefer `pre-commit` (Python ecosystem) or `lefthook` (polyglot, fast parallel execution) over raw git hooks. Husky for JS/TS-heavy projects. ### Hook Stage Assignment ``` pre-commit (< 30s): formatting | linting | unit tests (fast subset) | secrets scan pre-push (< 5 min): full unit suite | integration tests | coverage check | type checking ``` ## Pipeline Stages ### Commit Stage (target: < 10 minutes) Compile...