0816 update

.github/copilot-instructions.md

@@ -0,0 +1,48 @@
+# Copilot instructions for dev-sidecar
+
+## Commands
+
+- Dependency management:
+  - Install dependencies for the entire workspace from the repository root using `pnpm install`. Avoid using `npm install` for dependency installation in this project.
+  - If `pnpm install` reports dependency conflicts or version mismatches, update the relevant `package.json` entries to compatible versions (or adjust `peerDependencies`), then re-run `pnpm install`.
+
+- Linting:
+  - Lint the repository from the root with `pnpm lint`.
+  - Auto-fix lint issues from the root with `pnpm lint:fix`.
+  - If `pnpm lint` or `pnpm lint:fix` fails, review the reported errors and manually fix the files indicated by the linter, then re-run the command.
+
+- Testing:
+  - Run package tests where they live:
+    - `pnpm --filter @docmirror/dev-sidecar test`
+    - `pnpm --filter @docmirror/mitmproxy test`
+  - Run a single test file by passing it after `--`, for example:
+    - `pnpm --filter @docmirror/dev-sidecar test -- test/regex.test.js`
+    - `pnpm --filter @docmirror/mitmproxy test -- test/proxyTest.js`
+
+- GUI development and packaging (from `packages/gui`):
+  - `npm run electron`
+  - `npm run electron:build`
+  - `npm run serve`
+  - `npm run lint`
+  - For GUI debugging: run `npm run electron` and open the Electron developer tools (application menu View → Toggle Developer Tools or the platform shortcut) to inspect renderer pages, console logs, and IPC traffic.
+
+## High-level architecture
+
+- This is a pnpm workspace monorepo with four packages:
+  - `packages/core`: shared app logic, config, shell helpers, system proxy handling, and plugin/module code.
+  - `packages/mitmproxy`: the HTTP(S) proxy, DNS, interception, PAC, and response/request rewrite layer.
+  - `packages/gui`: the Electron + Vue 2 desktop app.
+  - `packages/cli`: a small CLI entrypoint that loads user config and starts the proxy service.
+- `packages/core/src/index.js` exposes the main API and owns process-level error handling plus config/state wiring.
+- `packages/mitmproxy/src/index.js` creates the proxy server(s), applies proxy options, and reports status/errors back to the host process.
+- `packages/gui/src/background.js` is the Electron main process: it loads config, creates the main window, tray, IPC bridges, and Windows-specific power-monitor behavior.
+- Renderer code lives under `packages/gui/src/view/`; IPC/bridge code lives under `packages/gui/src/bridge/`.
+- The CLI reads `packages/cli/src/user_config.json5`, prints a banner, and starts the core API with the mitmproxy service path.
+
+## Repo-specific conventions
+
+- Most runtime code in `core`, `mitmproxy`, and `cli` uses CommonJS; GUI code is the Electron/Vue app and is organized around the Electron main process plus renderer/bridge split.
+- Keep GUI source imports aligned with the existing file layout and `.js` module naming used in the Electron entrypoints.
+- Preserve the startup/shutdown flow: ensure the sequence remains where `core` initializes and manages the proxy lifecycle, `mitmproxy` performs network interception, and the GUI communicates exclusively through IPC bridges and the `core` API; avoid direct cross-component calls that bypass these boundaries.
+- Native/module setup matters here: the repo uses a root `.npmrc` with a PhantomJS mirror and C++17 build flags for native modules.
+- The project documents Node 22.x, Python 3.11/setuptools, and VS 2022 C++ tooling as the expected local environment for Windows builds.

.github/workflows/build-cli.yml

@@ -0,0 +1,101 @@
+name: "Build CLI (SEA)"
+
+on:
+  push:
+    branches:
+      - release*
+    tags:
+      - 'v*'
+    paths:
+      - "packages/cli/**"
+      - "packages/core/**"
+      - "packages/mitmproxy/**"
+      - "pnpm-workspace.yaml"
+      - "pnpm-lock.yaml"
+      - "package.json"
+      - ".github/workflows/build-cli.yml"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    env:
+      ELECTRON_CACHE: ${{ github.workspace }}/.cache/electron
+      ELECTRON_BUILDER_CACHE: ${{ github.workspace }}/.cache/electron-builder
+    steps:
+      - name: "Checkout"
+        uses: actions/checkout@v4.1.7
+
+      - name: "Setup pnpm"
+        uses: pnpm/action-setup@v4
+
+      - name: "Setup Node.js 22.x"
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          registry-url: https://npm.pkg.github.com/
+          cache: pnpm
+
+      - name: "Install dependencies"
+        run: pnpm install
+
+      - name: "Test CLI"
+        run: pnpm --filter @docmirror/dev-sidecar-cli test
+
+      - name: "Cache Node.js binaries (node-bin)"
+        uses: actions/cache@v4
+        with:
+          path: packages/cli/dist/node-bin
+          key: cli-node-bin-${{ runner.os }}-${{ hashFiles('packages/cli/scripts/build.js') }}
+
+      - name: "Build all platforms (SEA)"
+        run: node packages/cli/scripts/build.js --all
+
+      - name: "Generate SHA256SUMS"
+        run: |
+          cd packages/cli/dist
+          sha256sum ds-cli-* > SHA256SUMS.txt
+          cat SHA256SUMS.txt
+
+      - name: "Print dist"
+        run: |
+          ls -lah packages/cli/dist/ds-cli-*
+          file packages/cli/dist/ds-cli-* 2>/dev/null || true
+
+      - name: "Upload artifacts"
+        uses: actions/upload-artifact@v4.4.0
+        with:
+          name: ds-cli-${{ github.sha }}
+          path: |
+            packages/cli/dist/ds-cli-*
+            packages/cli/dist/SHA256SUMS.txt
+          if-no-files-found: error
+
+  release:
+    runs-on: ubuntu-latest
+    needs: build
+    if: startsWith(github.ref, 'refs/tags/v')
+    steps:
+      - name: "Download artifacts"
+        uses: actions/download-artifact@v4.1.8
+        with:
+          pattern: ds-cli-*
+          merge-multiple: true
+          path: release
+
+      - name: "Print release dir"
+        run: |
+          chmod +x release/ds-cli-*
+          ls -lah release/
+
+      - name: "Create release"
+        uses: wangliang181230/github-action-ghr@master
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
+          GHR_PATH: release/
+          GHR_TITLE: ${{ github.ref_name }}
+          GHR_REPLACE: true
+          GHR_DRAFT: true

.github/workflows/codeql.yml

@@ -0,0 +1,103 @@
+# For most projects, this workflow file will not need changing; you simply need
+# to commit it to your repository.
+#
+# You may wish to alter this file to override the set of languages analyzed,
+# or to provide custom queries or build logic.
+#
+# ******** NOTE ********
+# We have attempted to detect the languages in your repository. Please check
+# the `language` matrix defined below to confirm you have the correct set of
+# supported CodeQL languages.
+#
+name: "CodeQL Advanced"
+
+on:
+  push:
+    branches: [ "master" ]
+  pull_request:
+    branches: [ "master" ]
+  schedule:
+    - cron: '37 23 * * *'
+  workflow_dispatch:
+
+
+jobs:
+  analyze:
+    name: Analyze (${{ matrix.language }})
+    # Runner size impacts CodeQL analysis time. To learn more, please see:
+    #   - https://gh.io/recommended-hardware-resources-for-running-codeql
+    #   - https://gh.io/supported-runners-and-hardware-resources
+    #   - https://gh.io/using-larger-runners (GitHub.com only)
+    # Consider using larger runners or machines with greater resources for possible analysis time improvements.
+    runs-on: ${{ (matrix.language == 'swift' && 'macos-latest') || 'ubuntu-latest' }}
+    permissions:
+      # required for all workflows
+      security-events: write
+
+      # required to fetch internal or private CodeQL packs
+      packages: read
+
+      # only required for workflows in private repositories
+      actions: read
+      contents: read
+
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+        - language: actions
+          build-mode: none
+        - language: javascript-typescript
+          build-mode: none
+        # CodeQL supports the following values keywords for 'language': 'actions', 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'rust', 'swift'
+        # Use `c-cpp` to analyze code written in C, C++ or both
+        # Use 'java-kotlin' to analyze code written in Java, Kotlin or both
+        # Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
+        # To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
+        # see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
+        # If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
+        # your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+
+    # Add any setup steps before running the `github/codeql-action/init` action.
+    # This includes steps like installing compilers or runtimes (`actions/setup-node`
+    # or others). This is typically only required for manual builds.
+    # - name: Setup runtime (example)
+    #   uses: actions/setup-example@v1
+
+    # Initializes the CodeQL tools for scanning.
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v4
+      with:
+        languages: ${{ matrix.language }}
+        build-mode: ${{ matrix.build-mode }}
+        # If you wish to specify custom queries, you can do so here or in a config file.
+        # By default, queries listed here will override any specified in a config file.
+        # Prefix the list here with "+" to use these queries and those in the config file.
+
+        # For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
+        # queries: security-extended,security-and-quality
+
+    # If the analyze step fails for one of the languages you are analyzing with
+    # "We were unable to automatically build your code", modify the matrix above
+    # to set the build mode to "manual" for that language. Then modify this step
+    # to build your code.
+    # ℹ️ Command-line programs to run using the OS shell.
+    # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
+    - name: Run manual build steps
+      if: matrix.build-mode == 'manual'
+      shell: bash
+      run: |
+        echo 'If you are using a "manual" build mode for one or more of the' \
+          'languages you are analyzing, replace this with the commands to build' \
+          'your code, for example:'
+        echo '  make bootstrap'
+        echo '  make release'
+        exit 1
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v4
+      with:
+        category: "/language:${{matrix.language}}"

.github/workflows/defender-for-devops.yml

@@ -0,0 +1,51 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+#
+# Microsoft Security DevOps (MSDO) is a command line application which integrates static analysis tools into the development cycle.
+# MSDO installs, configures and runs the latest versions of static analysis tools
+# (including, but not limited to, SDL/security and compliance tools).
+#
+# The Microsoft Security DevOps action is currently in beta and runs on the windows-latest queue,
+# as well as Windows self hosted agents. ubuntu-latest support coming soon.
+#
+# For more information about the action , check out https://github.com/microsoft/security-devops-action
+#
+# Please note this workflow do not integrate your GitHub Org with Microsoft Defender For DevOps. You have to create an integration
+# and provide permission before this can report data back to azure.
+# Read the official documentation here : https://learn.microsoft.com/en-us/azure/defender-for-cloud/quickstart-onboard-github
+
+name: "Microsoft Defender For Devops"
+
+permissions:
+  contents: read
+  security-events: write
+
+on:
+  push:
+    branches: [ "master" ]
+  pull_request:
+    branches: [ "master" ]
+  schedule:
+    - cron: '36 8 * * 1'
+
+jobs:
+  MSDO:
+    # currently only windows latest is supported
+    runs-on: windows-latest
+
+    steps:
+    - uses: actions/checkout@v4
+    - uses: actions/setup-dotnet@v4
+      with:
+        dotnet-version: |
+          5.0.x
+          6.0.x
+    - name: Run Microsoft Security DevOps
+      uses: microsoft/security-devops-action@v1.6.0
+      id: msdo
+    - name: Upload results to Security tab
+      uses: github/codeql-action/upload-sarif@v3
+      with:
+        sarif_file: ${{ steps.msdo.outputs.sarifFile }}