sdlc-agent-4-enterprise-server 1.53.0 → 1.53.1

package/Dockerfile

@@ -100,6 +100,23 @@ ARG MARKITDOWN_MCP_VERSION=0.0.1a7
 # markdown-exporter-mcp-local has no PyPI release — pin the exact upstream
 # commit (main @ 2026-04-07) for a hermetic build (git-source analogue of SEC-02).
 ARG MARKDOWN_EXPORTER_MCP_REF=1429b6a94767a709f7f5119219ca5951042d9d3c
+# SA4E-360 follow-up: Debian's python3-venv/ensurepip bundles setuptools
+# 66.1.1 into EVERY venv it creates, and setuptools itself VENDORS
+# jaraco.context/wheel under setuptools/_vendor — Trivy flags BOTH layers:
+#   - setuptools 66.1.1 (ensurepip bundle): CVE-2024-6345 (fix 70.0.0) +
+#     CVE-2025-47273 (fix 78.1.1) — 2 HIGH per venv
+#   - setuptools 78.1.1 (first bump): vendored jaraco.context 5.3.0
+#     (CVE-2026-23949, fix 6.1.0) + vendored wheel 0.45.1 (CVE-2026-24049,
+#     fix 0.46.2) — 2 more HIGH per venv, surfaced by a fresh Trivy DB
+# 84.0.0 clears all four: it is free of the two setuptools CVEs and vendors
+# jaraco.context 6.1.0 + wheel 0.46.3 (>= both fix versions). setuptools >=81
+# removed pkg_resources; a grep of both /opt venvs (SA4E-360) showed NO
+# runtime package imports pkg_resources — only setuptools internals and
+# unreachable onnxruntime benchmark scripts — so the removal is safe here.
+# The version is asserted via importlib.metadata (robust across setuptools
+# versions). Drop the override once the pinned base image bundles a fixed
+# setuptools.
+ARG SETUPTOOLS_VERSION=84.0.0
 # `python3` already exists in base (build toolchain); only the venv/ensurepip
 # support is missing. One venv per server: independent dependency trees that
 # are pinned, upgraded and Trivy-scanned separately.
@@ -111,17 +128,34 @@ RUN python3 -m venv /opt/markitdown-venv \
       "markitdown-mcp==${MARKITDOWN_MCP_VERSION}" \
  && test -x /opt/markitdown-venv/bin/markitdown-mcp \
  && /opt/markitdown-venv/bin/python -c "import markitdown_mcp" \
+ && /opt/markitdown-venv/bin/pip install --no-cache-dir "setuptools==${SETUPTOOLS_VERSION}" \
+ && /opt/markitdown-venv/bin/python -c "from importlib.metadata import version; assert version('setuptools') == '${SETUPTOOLS_VERSION}'" \
  && /opt/markitdown-venv/bin/python -m pip uninstall -y pip
 # `mcp<2` constraint: upstream declares `mcp>=1.27.0` (unbounded) but its code
 # imports `mcp.server.fastmcp` — an API REMOVED in mcp 2.x (FastMCP → MCPServer).
 # The import probe below fails the build on exactly this class of drift
 # (verified: unconstrained pip resolved mcp 2.3.0 → ModuleNotFoundError).
+# `pillow==12.3.0` override (SA4E-360): upstream pins `pillow~=12.1.1`, which
+# resolves to 12.1.1 — carrying 16 HIGH CVEs that fail the production Trivy
+# gate. PEP 440 `~=12.1.1` means >=12.1.1,<12.2, so it does NOT admit the
+# fixed 12.3.0 (which markitdown-venv already runs on the same Python 3.11
+# base). The force-upgrade AFTER the main install therefore triggers a pip
+# metadata conflict warning ("markdown-exporter-mcp-local 0.1.0 requires
+# pillow~=12.1.1 ... incompatible") — EXPECTED and non-fatal: pip installs
+# the requested version and exits 0. Trivy reads the installed 12.3.0
+# metadata, clearing all 16 CVEs. The PIL version probe fails the build if
+# resolution ever regresses to 12.1.1. Remove this override once upstream
+# releases an officially fixed pin (e.g. pillow~=12.3).
 RUN python3 -m venv /opt/markdown-exporter-venv \
  && /opt/markdown-exporter-venv/bin/pip install --no-cache-dir \
       "markdown-exporter-mcp-local @ git+https://github.com/Zac-Chen-2001/markdown-exporter-mcp-local@${MARKDOWN_EXPORTER_MCP_REF}" \
       "mcp>=1.27.0,<2.0.0" \
  && test -x /opt/markdown-exporter-venv/bin/markdown-exporter-mcp-local \
  && /opt/markdown-exporter-venv/bin/python -c "import markdown_exporter_mcp.server, md_exporter" \
+ && /opt/markdown-exporter-venv/bin/pip install --no-cache-dir "pillow==12.3.0" \
+ && /opt/markdown-exporter-venv/bin/python -c "import PIL; assert PIL.__version__ == '12.3.0'" \
+ && /opt/markdown-exporter-venv/bin/pip install --no-cache-dir "setuptools==${SETUPTOOLS_VERSION}" \
+ && /opt/markdown-exporter-venv/bin/python -c "from importlib.metadata import version; assert version('setuptools') == '${SETUPTOOLS_VERSION}'" \
  && /opt/markdown-exporter-venv/bin/python -m pip uninstall -y pip
 # Both venvs are copied root-owned READ-ONLY; stripping their bundled pip keeps
 # the runtime image free of ANY package manager (SEC-05) and out of Trivy scans.

package/README.md

@@ -6,7 +6,7 @@
 </p>
 
 <p align="center">
-  <img src="https://img.shields.io/badge/version-1.48.0-blue?style=for-the-badge" alt="Version">
+  <img src="https://img.shields.io/badge/version-1.53.0-blue?style=for-the-badge" alt="Version">
   <img src="https://img.shields.io/badge/tools-66+-teal?style=for-the-badge" alt="Tools">
   <img src="https://img.shields.io/badge/node-%3E%3D18-green?style=for-the-badge" alt="Node">
 </p>
@@ -38,7 +38,7 @@ Server starts at **http://localhost:48721**. Verify it's running:
 
 ```bash
 curl http://localhost:48721/health
-# → {"status":"healthy","version":"1.48.0","uptime":5,"tools_loaded":52}
+# → {"status":"healthy","version":"1.53.0","uptime":5,"tools_loaded":52}
 ```
 
 ### Development Mode (auto-reload)
@@ -233,6 +233,7 @@ The embedding model is expected at `.code-intel/models/model.onnx`. Download it:
 
 | Version | Date | Ticket | Changes |
 |---------|------|--------|---------|
+| 1.53.0 | 2026-10-15 | SA4E-360 | Version sync with extension release v1.53.0 (Multi-Resolution Context Supply P1 — skeleton + agentic loading, UAT-verified; backend runtime unchanged).
 | 1.48.0 | 2026-10-10 | SA4E-341 | Version sync (E2E testing framework delivered in standalone `e2e/` package — no backend runtime changes). Also includes SA4E-335 DB-layer 6 bugfixes (memoized id-column check, literal-safe placeholder translation, identifier quoting SQLi guard, safeExec SQLSTATE filter, writable test-backend data dir), SA4E-349 auth 401 fail-loud fixes, SA4E-350 Pega '@baseclass' appliesTo passthrough fix, enrichment retry scoped via X-Project-Id + runtime settings module. |
 | 1.47.1 | 2026-10-04 | — | Fix Docker CI fail (Trivy CVE-2026-103111 libpcre2-8-0 HIGH), defensive JSON parse on `/auth/refresh`, SA4E-100 Pega BELONGS_TO edges. |
 | 1.47.0 | 2026-10-02 | — | New endpoint `GET /api/v1/enrichment/failures?limit=N` (clamp 1–1000, default 200) returns full FAILED enrichment task list from `pending_tasks` with resolved source, error, retry count, timestamp (`PendingTaskRepository.listFailedDetailed`). Surfaces ingest failures to the extension beyond the 10-item status tooltip. |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sdlc-agent-4-enterprise-server",
-  "version": "1.53.0",
+  "version": "1.53.1",
   "description": "Code Intelligence MCP Server — multi-agent SDLC pipeline with semantic memory, code graph, and draw.io integration",
   "main": "dist/index.js",
   "bin": {

package/src/engine/tools/__tests__/code-extract.test.ts

@@ -110,9 +110,16 @@ describe('code_extract_signatures — fail-soft batch + caps (E2E-API-06)', () =
 });
 
 // STC E2E-API-07 — backend containment twin, 4 attack vectors (SEC-360-04)
+// NOTE (platform): `C:\...` absolute and `..\..` backslash-traversal vectors
+// only carry attack semantics on a win32 host — on posix, backslashes are
+// literal filename characters, so those inputs resolve STRICTLY INSIDE the
+// root (path.resolve posix semantics) and rejecting them would be wrong.
+// Cross-platform vectors (`/etc/passwd`, `//server/share`, `sub/../../x`)
+// stay unguarded and run on every platform.
+const IS_WIN = process.platform === 'win32';
 describe('SEC-360-04 — resolveContainedFile rejects all 4 attack layers', () => {
   it('BV-03: absolute path outside the workspace root is rejected', () => {
-    expect(resolveContainedFile(root, 'C:\\projects\\secrets.txt')).toBeNull();
+    if (IS_WIN) expect(resolveContainedFile(root, 'C:\\projects\\secrets.txt')).toBeNull();
     expect(resolveContainedFile(root, '/etc/passwd')).toBeNull();
   });
 
@@ -126,7 +133,7 @@ describe('SEC-360-04 — resolveContainedFile rejects all 4 attack layers', () =
   });
 
   it('BV-06: dotdot traversal is rejected (lexical isWithin, layer 3)', () => {
-    expect(resolveContainedFile(root, '..\\..\\secrets.txt')).toBeNull();
+    if (IS_WIN) expect(resolveContainedFile(root, '..\\..\\secrets.txt')).toBeNull();
     expect(resolveContainedFile(root, 'sub/../../secrets.txt')).toBeNull();
   });