jdbc-ctp-verify-reportlisted

# CUBRID JDBC driver verify (CTP) → report (one-shot) Build the CUBRID JDBC driver, run the **CTP** JDBC suite against CUBRID, diff vs a baseline, classify broken cases, and **always** generate the Word 비교 분석 report. Mirrors `hhh-dialect-verify-report` for the JDBC side. Needs the JDBC repo, CTP, a CUBRID install (`$CUBRID`), Docker/server running, `python3`, and (for the report) `node`+`docx`. ## Step 0: Prereqs - JDBC driver source: `~/Devel/JDBC/devel` (ant `build.xml` via `./build.sh`). - CTP: `~/Devel/JDBC/jdbc-verification/cubrid-testtools/CTP` (`bin/ctp.sh jdbc -c conf/jdbc.conf`); test cases under `cubrid-testcases-private/interface/JDBC/test_jdbc`. - A CUBRID install at `$CUBRID` (the built jar deploys to `$CUBRID/jdbc/cubrid_jdbc.jar`) with the server/broker reachable. - Installed `report` skill + its deps (see report Step 0). ## Step 1: Run the orchestrator (build + CTP + diff) ```bash bash <skill-base-dir>/assets/run_ctp.sh \ --baseline ~/Devel/JDBC/jdbc-verification/cubrid-testtools/CTP/result/jdbc/current_runtime_logs \ --cubrid "$CUBRID" # add --no-build to reuse the deployed jar ``` It builds the driver (`./build.sh`), deploys `cubrid_jdbc.jar` to `$CUBRID/jdbc/`, runs `ctp.sh jdbc`, parses `result/jdbc/current_runtime_logs/test-jdbc.xml`, and diffs vs the baseline. Writes `ctp-out/after.json`, `baseline.json`, `diff.txt`. The **change under test** is in the working tree: a driver code change, or a build-target change (the javac `source`/`