From 71b837533366bd38d3fdeee6651876e0d7de835d Mon Sep 17 00:00:00 2001 From: Vadym Samoilenko Date: Fri, 15 May 2026 11:40:02 +0100 Subject: [PATCH] wiki: auto-compile 2026-05-15 (1 log(s), 263 articles) --- wiki/client-knowledge/baic.md | 4 ++-- .../fastapi-asyncio-container-restart-recovery.md | 3 +++ wiki/concepts/figma-mcp-tools-reference.md | 13 ++++++++++++- wiki/log.md | 8 ++++++++ 4 files changed, 25 insertions(+), 3 deletions(-) diff --git a/wiki/client-knowledge/baic.md b/wiki/client-knowledge/baic.md index e45d25c..6c792b7 100644 --- a/wiki/client-knowledge/baic.md +++ b/wiki/client-knowledge/baic.md @@ -3,7 +3,7 @@ title: "BAIC — Client Knowledge" aliases: [baic-dashboard, baic-deploy] tags: [client-knowledge, baic, deploy, rsync, azure-ad] created: 2026-05-06 -updated: 2026-05-10 +updated: 2026-05-15 --- # BAIC @@ -46,7 +46,7 @@ ssh baic "sudo systemctl status baic_dashboard.service" |-------|--------| | No `.env` file needed | Backend reads env vars with OS defaults directly in `app.py` — do not create `.env` on server | | rsync "failed to set times" warning | `rsync` warns about directory timestamp permission — **benign**; content copies correctly | -| `deploy.sh` is initial setup only | Script in repo targets first-time setup (wrong service name, interactive prompts) — never use for updates | +| `deploy.sh` is initial setup only | Script in repo targets first-time setup (wrong service name, interactive prompts) — never use for updates. It runs Alembic migrations automatically as step 5 of 6 — useful to know when debugging a first-time deploy on `10.220.72.13` | | Old Vite hashes accumulate | `assets/` on the server grows with each deploy (old content-hash files never cleaned); manually prune if needed | ## Known Gotchas diff --git a/wiki/concepts/fastapi-asyncio-container-restart-recovery.md b/wiki/concepts/fastapi-asyncio-container-restart-recovery.md index fc7b81d..40a7230 100644 --- a/wiki/concepts/fastapi-asyncio-container-restart-recovery.md +++ b/wiki/concepts/fastapi-asyncio-container-restart-recovery.md @@ -77,6 +77,9 @@ app = FastAPI(lifespan=lifespan) Smart-resume requires each document/chunk to have its own `status` column so recovery can skip `completed` ones. +> [!warning] `parsing` ≠ `parsed` — do not skip interrupted documents +> Documents in `parsing` state (interrupted mid-parse by the restart) must be **reset to `pending`**, not skipped. Only `parsed`/`completed` documents (finished before the restart) are safe to skip. A `parsing`-interrupted document may have partial or missing output — re-running it is mandatory. + --- ## UI Deadlock Root Cause diff --git a/wiki/concepts/figma-mcp-tools-reference.md b/wiki/concepts/figma-mcp-tools-reference.md index 2c39a3d..28865d7 100644 --- a/wiki/concepts/figma-mcp-tools-reference.md +++ b/wiki/concepts/figma-mcp-tools-reference.md @@ -6,7 +6,7 @@ sources: - "raw/Tools and prompts Developer Docs.md" - "raw/Guide to the Figma MCP server.md" created: 2026-05-13 -updated: 2026-05-13 +updated: 2026-05-15 --- # Figma MCP Server — Tool Reference @@ -15,6 +15,17 @@ Complete list of the 18 tools exposed by the Figma MCP server. The primary 3 are ## Core Design-to-Code Tools +## Tool Auto-Selection Warning + +> [!warning] AI does not reliably auto-select the right tool as the toolset grows +> As the Figma MCP toolset expands, the AI may fire `get_design_context` when `get_variable_defs` is needed (or vice versa). Both produce plausible-looking but **wrong** output — generated code instead of token values, silently. There is no error. +> +> **Fix:** prompt through the artifact name, not the intent: +> - `"Get the variable names and values used in this frame"` → reliably triggers `get_variable_defs` +> - `"Get the design context for this selection"` → reliably triggers `get_design_context` + +--- + ### **`get_design_context`** ← use first Returns structured React + Tailwind code, a screenshot, and component context for the selected node. This is the primary tool for implementing Figma designs. If Code Connect mappings exist for components in the selection, it returns real component snippets instead of generated code. diff --git a/wiki/log.md b/wiki/log.md index ac525a2..05a7f3b 100644 --- a/wiki/log.md +++ b/wiki/log.md @@ -1,6 +1,14 @@ # Build Log +## [2026-05-15T21:30:00+02:00] compile | daily/2026-05-15.md — pass 2 (nuance extraction) +- Source: daily/2026-05-15.md (re-pass after context compaction) +- Articles updated (3): + - [[wiki/client-knowledge/baic]] — deploy.sh runs Alembic migrations as step 5 of 6 (initial setup context) + - [[wiki/concepts/fastapi-asyncio-container-restart-recovery]] — smart-resume nuance: `parsing`-state docs must reset to `pending` (not skip); only `parsed`/`completed` docs are safe to skip + - [[wiki/concepts/figma-mcp-tools-reference]] — tool auto-selection failure warning: prompt artifact name not intent to force correct tool +- No new articles created — all new knowledge fits as targeted updates to existing articles + ## [2026-05-15T21:00:00+02:00] compile | daily/2026-05-15.md - Source: daily/2026-05-15.md - Sessions: Barclays KB processing (asyncio task loss + startup recovery), Figma Code Connect API (plugin API gotchas), Figma skill invocation reliability, Mailgun domain silent failure, Figma design-system variable lookup