lwc/bin
SHA256
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(projekt-matching): final-review fixes — safe redeploy, poison-mail hardening, plan deviations note

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
tlg
2026-07-09 17:15:39 +02:00
parent 1863ce087c
commit 9ca7767208
6 changed files with 154 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/superpowers/plans/2026-07-09-langflow-projekt-matching.md
View File

@@ -25,6 +25,18 @@
- Langflow API auth (v1.10.0): flow CRUD + variables need Bearer JWT from `GET /api/v1/auto_login`; `POST /api/v1/run/...` and webhook need `x-api-key`. Responses are gzip → `curl --compressed`.
- Langflow data dir: host `~/.local/share/langflow_pod/langflow-data` = container `/app/langflow`. Deployed files need group-read (dir is `g+rwxs`, uid-1000/gid-0 process).
## Deviations discovered during execution
- `response_format json_schema` replaces `guided_json` (vLLM 0.22 ignores `guided_json`).
- `chat_template_kwargs` `enable_thinking: false` is required for structured calls.
- Component input `ctx` was renamed `ctx_in` (Langflow reserves `Component.ctx`).
- `PYTHONPATH=/app/langflow` env var replaces the `.pth`-file approach.
- Langfuse org/project provisioning goes through the session tRPC endpoint (the admin API is EE-gated).
- Flow 1 is a single `PMIngest` component (not the originally sketched multi-node graph).
- `PMNotify` calls `stage_notify` directly rather than going through an intermediate layer.
Task-level code snippets further below in this document were NOT retro-edited to reflect these deviations; the `projektmatch` package source under `/home/lwc/bin/projekt-matching/` is authoritative.
## File Structure
```