2 Commits

Include renames

Author	SHA1	Message	Date
Euisuh Jeongandbflatastic	8b7435890e	fix(mcp): prevent replay after lost attached replies (#211) ... The attached MCP backend no longer re-sends a request when its reply is lost: the app may already have applied it, so the error says the operation may have completed and to inspect the document before retrying; the next call reconnects, and a failed reconnect says the request was not sent. Fixes #194. Also: a connection the app already closed (it drops ones idle past its socket timeout) is noticed before the next request is written and replaced then, so a pause between calls is not an error. Co-authored-by: bflatastic <bflatastic@users.noreply.github.com>	2026-10-14 05:34:33 +07:00
Brandon ThomasandClaude Opus 5.5	b36fd771ab	M0.9: MCP server + figcraft-cli, PDF export, web app, release/CI packaging, vector edit mode, workspace lint cleanup ... - crates/mcp: JSON-RPC MCP server (18 tools, resources, prompts), headless and attached backends, end-to-end agent tests - apps/figcraft-cli: info/export/convert/render/run/commands/mcp/perf - crates/pdf: vector PDF export via krilla with embedded text; file.exportFramesPdf - apps/figcraft-web + packaging/{macos,windows,linux,freebsd,web} + release/ci workflows - engine vectoredit: edit points/handles/bend/add/delete-heal; canvas overlay and edit strip Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 13:31:53 -04:00