RAILIANCE-WP-0002 T02 blocked: vergabe-teilnahme missing issue-facade

uv sync in /home/worsch/vergabe-teilnahme fails because
universal-issue-tracker @ file:///home/worsch/issue-facade points at
an empty directory (only .claude/ remains). The container build
cannot proceed until the upstream dep resolves cleanly.

Documented three resolution options in the workplan; pausing T02
pending an upstream fix.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

workplans/railiance-apps-WP-0002-vergabe-teilnahme-on-railiance01.md

@@ -195,7 +195,7 @@ T04 below is now sequenced **after** that cluster reports healthy.
 
 ```task
 id: RAILIANCE-WP-0002-T02
-status: todo
+status: blocked
 priority: high
 repo: vergabe-teilnahme
 state_hub_task_id: "43ce85c4-0bdb-43c4-b0a5-81fa366800a6"
@@ -225,6 +225,39 @@ hub task and reference the PR/commit when complete.
 **Done when:** `docker build` against the vergabe-teilnahme repo produces
 a runnable image that responds to a smoke request locally.
 
+**Blocker found (2026-05-18):** vergabe-teilnahme cannot currently
+`uv sync` at all. `pyproject.toml` declares
+`universal-issue-tracker @ file:///home/worsch/issue-facade`, but
+`/home/worsch/issue-facade/` is effectively empty — only a `.claude/`
+directory exists; there is no `pyproject.toml` or `setup.py`.
+
+```
+error: Failed to generate package metadata for
+  `universal-issue-tracker==0.1.0 @ directory+../issue-facade`
+  Caused by: /home/worsch/issue-facade does not appear to be a Python
+  project, as neither `pyproject.toml` nor `setup.py` are present.
+```
+
+Related candidate sources investigated:
+- `/home/worsch/issue-core/` — a separate package (`issue-core`), not
+  the missing `universal-issue-tracker` facade.
+- `/home/worsch/markitect-main/_issue-tracking/issue-facade/` — does
+  not exist.
+
+This must be resolved upstream in `vergabe-teilnahme` (or by restoring
+`issue-facade`) before T02 can produce a buildable image. Options:
+
+1. **Restore `issue-facade`** — recover the missing source (git
+   reflog, backup, or recreate from `issue-core`'s public surface).
+2. **Repoint** `vergabe-teilnahme`'s dep to `issue-core` directly if
+   that's the intended replacement, then update `uv.lock`.
+3. **Vendor** a minimal stub interface in `vergabe-teilnahme/vendor/`
+   to unblock the container build; restore the real dep later.
+
+Recommendation: route to whoever owns `issue-facade` (likely a
+`markitect` or `personhood` domain task) and pause T02 until the dep
+resolves cleanly outside Docker.
+
 ---
 
 ### T03 — Build and publish image to Gitea container registry