mono - chore: defense - add CODEOWNERS for high-risk paths

[jaredwray]

Summary

Add .github/CODEOWNERS for high-risk paths (defense-in-depth § 2) so lockdown-repo.sh --check can require a code-owner review.

Status update

DEFENSE_IN_DEPTH.md § 2: CODEOWNERS → (PR #1704 pending)

Changes

• Own /.github/, /.cursor/, /.devcontainer/, and /scripts/ as @jaredwray

Say if you want a different owner or a second reviewer.

Verification

• File matches the catalog template with {{OWNERS}} substituted

Reference: defense-in-depth-nodejs § 2

  

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (f50b770) to head (dabc61b).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1704   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           29        29           
  Lines         3513      3513           
  Branches       808       795   -13     
=========================================
  Hits          3513      3513           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.