test(e2e): Phase 23B — rebuild E2E infrastructure; fix 6 real prod defects it exposed

Phase 23 closed as PARTIAL: fake coverage was gone, but the E2E layer itself
was still empty — no conftest.py anywhere, ~15 fixtures that never existed,
6 files crashing at import on os.environ["E2E_PASSWORD"], and CI never ran E2E.
STATUS's "10 E2E files / ~80+ cases ✅" described files that had never executed.

Infrastructure delivered:
- tests/e2e/conftest.py: ApiClient (trust_env=False — a host http_proxy turns
  localhost calls into 502), operator_token(username) / new_user / admin_token
  fixtures, and a session probe that calls pytest.exit(4) when the stack is
  unreachable. NOT skip: skip would launder "did not run" into "passed".
- pytest.ini, tests/e2e/requirements.txt, and tests/e2e/sql/
  seed_e2e_operators.sql — migrations contain NO operator seed at all, so a
  fresh database has zero logins; the seed creates 6 e2e accounts with role
  bindings, idempotent, password injected via `psql -v pwd`.
- CI job `e2e`: compose up -> poll /health/live (timeout = fail) -> seed ->
  pytest -> always teardown. Gate D-23-D is now closed.
- 8 E2E files migrated off import-time env reads; tautological assertions
  (`x == t or not x`), a counselor token standing in for content_editor, and a
  bare `status_code == 200` claiming to prove INV-020 were replaced with real
  permission/behavior assertions.

Six real production defects found only by running against real PostgreSQL
(H2 has zero coverage for all of them):
- D-23B-A (Critical): stale V042__add_appointment_operator_register_permission.sql
  left in target/classes; src had replaced it with V042__add_service_location_
  announcements.sql. Packing without clean put two V042 in the jar -> Flyway
  "Found more than one migration with version 042" -> app would not start.
  Guard added: testBuildOutputHasNoDuplicateMigrationVersions scans build output
  (src is clean, so only this catches it).
- D-23B-B (High): non-UUID path variable reached the DB -> 500 + leaked
  `invalid input syntax for type uuid`. Now rejected at the controller.
- D-23B-C (High): 6 E2E files raised KeyError at import -> never collected.
- D-23B-E (Critical): permissions = 48, role_permissions for super_admin = 18,
  matchmaker = 0. V015's "grant all to super_admin" was a point-in-time snapshot;
  the 30 permissions added later were never granted. On a fresh stack an admin
  cannot create a service station and matchmakers can do nothing. V044 restores
  super_admin to its documented definition (not an expansion); the matchmaker
  permission set needs a product decision and is left as a residual.
- D-23B-I (Medium): IllegalArgumentException (e.g. invalid activity type) was
  unmapped -> 500. Now BAD_REQUEST.
- D-23B-J (High): `operator does not exist: uuid = character varying` — Java
  ids are String, columns are uuid, PostgreSQL does not implicitly cast in
  comparisons. Fixed at the source with JDBC `stringtype=unspecified` (docker
  profile); production datasource comes from deploy env and needs the same.

One judgement retracted: an initial read suggested service_appointment.register
was missing. It is not — the endpoint uses service.assisted_registration, seeded
in V029, and the code deliberately avoids a duplicate permission. Nothing was
changed on that basis.

Verification: 33 E2E passed against a live stack; unreachable stack and a
missing operator password both exit 4 (never skip/pass); backend regression
656 / 0 failures / 0 errors / 3 skipped (baseline 655, +1 guard, negatively
validated by injecting a duplicate V042 -> exactly one test turned red).

docs/STATUS.md

@@ -660,6 +660,36 @@ Invariant测试：10个（INV-011~020）→ **实测：原 14 个用例无任何
 
 **Phase 22（部署运维配置扩展）— 已完成** ✅
 
+### Phase 23B — E2E 测试基建重建（2026-09-18）✅ 已关闭
+
+> 本轮补齐的是 Phase 23 的两条遗留（D-23-C「E2E 整体不可执行」、D-23-D「CI 未串联 E2E」），
+> 与下方 **「Phase 24 — UAT增量」是不同工作**，不要混为一谈。
+
+| 交付 | 说明 |
+|---|---|
+| `tests/e2e/conftest.py` | fixture 体系：ApiClient、`operator_token(username)`、`new_user`、栈探活 |
+| `pytest.ini` / `tests/e2e/requirements.txt` | 收集范围与依赖 |
+| `tests/e2e/sql/seed_e2e_operators.sql` | 运营账号自举（**迁移里没有任何 operator 种子**，全新库无账号可登录） |
+| CI job `e2e` | 起真实栈 → 等就绪 → seed → pytest → 失败阻断 → 清理 |
+| 8 个 E2E 文件改造 | 消除 import 期 `KeyError`；替换恒真 / 名不副实的断言 |
+
+**核心设计**：栈不可达时 `pytest.exit(4)`，**不是 skip** —— skip 会把"未执行"伪装成"通过"。
+
+**验证**：本机真实活栈 **33 passed**；后端全量回归见本节末。
+
+**本轮暴露并修复的真实生产缺陷**（H2 测试库全部零覆盖，只有真 PostgreSQL 才现形）：
+
+| 编号 | 真相 |
+|---|---|
+| D-23B-A | 构建产物残留重复迁移版本号 042 → Flyway 报错 → **应用起不来** |
+| D-23B-B | 非 UUID path 参数 → 500 且泄漏数据库异常 |
+| D-23B-C | 6 个 E2E 文件 import 期崩溃 → **从未被执行过** |
+| D-23B-E | 权限 seed 缺口：`super_admin` 仅 18/48 条、`matchmaker` **0** 条（matchmaker 部分列为遗留） |
+| D-23B-I | 非法枚举参数 `IllegalArgumentException` 未映射 → 500（应 BAD_REQUEST） |
+| D-23B-J | `operator does not exist: uuid = character varying` → JDBC 增加 `stringtype=unspecified` |
+
+详见 `docs/Phase-23B-V11-E2E-Infrastructure-Completion-Report-2026-09-18.md`。
+
 ### Phase 24 — UAT增量 ✅ 已就绪（测试数据支持）
 | 任务 | 状态 |
 |------|------|