使用问题反馈

1.审计任务启动后无法取消(老版本支持，新版本找不到取消按钮了)
2.把源码以压缩包形式上传，文件数量仅识别出50个(实际文件数>50)
3.审计任务控制台输出窗口关闭后就没有入口可以打开了(新老版本都存在该问题)
4.网络中断会导致审计任务卡在运行中，且审计记录无法删除
5.新版本前后端分离后部署成本飙升(python很重，依赖较多，拉取缓慢，叠加国内docker访问艰难)，希望可以保留老版本纯前端构建启动的模式
6.服务器部署“docker-compose up -d”一键启动并不一键，登陆注册发现前端访问的是localhost:8000，需要手动修改docker-compose.yml配置
7.backend构建时内存占用高(特别是gcc这块)，使用deepseek优化了下dockerfile分段构建，请参考：

# 第一阶段：构建环境
FROM python:3.13-slim AS builder

WORKDIR /app

# 安装编译依赖
RUN rm -f /etc/apt/apt.conf.d/proxy.conf 2>/dev/null || true && \
    unset http_proxy https_proxy HTTP_PROXY HTTPS_PROXY all_proxy ALL_PROXY && \
    apt-get update && \
    apt-get install -y --no-install-recommends \
        gcc \
        libpq-dev \
        libffi-dev \
        libpango-1.0-0 \
        libpangocairo-1.0-0 \
        libcairo2 \
        libgdk-pixbuf-2.0-0 \
        libglib2.0-0t64 \
        shared-mime-info \
        pkg-config

# 安装 uv 和 Python 依赖
COPY --from=ghcr.io/astral-sh/uv:latest /uv /usr/local/bin/uv
COPY pyproject.toml uv.lock ./
RUN unset http_proxy https_proxy HTTP_PROXY HTTPS_PROXY all_proxy ALL_PROXY && \
    uv sync --frozen --no-dev

# 第二阶段：运行环境
FROM python:3.13-slim

WORKDIR /app

# 只安装运行时依赖（无 gcc）
RUN rm -f /etc/apt/apt.conf.d/proxy.conf 2>/dev/null || true && \
    unset http_proxy https_proxy HTTP_PROXY HTTPS_PROXY all_proxy ALL_PROXY && \
    apt-get update && \
    apt-get install -y --no-install-recommends \
        libpq-dev \
        libffi-dev \
        libpango-1.0-0 \
        libpangocairo-1.0-0 \
        libcairo2 \
        libgdk-pixbuf-2.0-0 \
        libglib2.0-0t64 \
        shared-mime-info \
        fontconfig \
        fonts-wqy-microhei \
    && fc-cache -fv \
    && rm -rf /var/lib/apt/lists/*

# 从构建阶段复制 Python 依赖
COPY --from=builder /app/.venv .venv

# 复制应用代码
COPY . .

# 设置 PATH 使用虚拟环境
ENV PATH="/app/.venv/bin:$PATH"

# 创建上传目录
RUN mkdir -p /app/uploads/zip_files

EXPOSE 8000
CMD ["uvicorn", "app.main:app", "--host", "0.0.0.0", "--port", "8000"]

Split the seven reports into separate investigations, starting with docker-compose.yml and the frontend/backend deployment entry points. Reproduce the audit cancellation, archive file-count, console reopening, network interruption, configuration, and backend build issues before choosing a focused change. Done means each selected behavior is reproducible, corrected, and verified without regressing deployment or audit workflows.