+
+[Archify](https://github.com/tt-a1i/archify), adapted for the ZCode side panel: this plugin bundles Archify's diagram engine (v3.2.0) and brings architecture, workflow, sequence, dataflow, state machine, ERD, class, tree, timeline and waterfall diagrams into the ZCode side panel with full interaction and export.
+
+> Source repository: [tt-a1i/archify](https://github.com/tt-a1i/archify) — the upstream diagram engine (Apache-2.0).
+
+> 中文文档：[README_CN.md](README_CN.md)
+
+## Features
+
+- Agent-driven rendering: describe a diagram in natural language; the agent renders it with the bundled Archify runtime
+- Interactive side panel: results open in the ZCode side panel in full-interaction mode
+- Export: PNG, SVG and share cards from the diagram's own export menu, saved into the workspace
+
+## Install
+
+Install from the ZCode Plugin Marketplace (**Settings → Plugins → Plugin Marketplace**), search for Archify.
+
+## Usage
+
+After installation, just ask the agent to draw, for example:
+
+- "Draw an architecture diagram of this repository's frontend and backend"
+- "Show the login request flow as a sequence diagram"
+
+The agent renders via the bundled skill `archify-panel`; the result opens in the side panel automatically.
+
+## Security & side effects
+
+- **MCP server**: registers a local stdio MCP server `archify` that provides the diagram rendering tools
+- **File writes**: rendered artifacts are written to the workspace `.archify-panel/` (exports go to `exports/`)
+- **Browser use**: the render pipeline launches the local browser for a measurement step; data stays on the machine
+- **Network access**: none. Rendering is fully local; the plugin calls no external services
+- **Telemetry**: none
+
+## Build from source
+
+Plugin source lives in `ui-plugins/archify-panel/` in this repository; the install directory contents (`dist/` and `vendor/`) are generated by the repository build:
+
+```bash
+pnpm install --frozen-lockfile
+pnpm build
+```
+
+The build produces `dist/server.mjs` and `dist/ui/panel.html`; `vendor/` is copied into the install directory by the stage script.
+
+Tests (after building):
+
+```bash
+node ui-plugins/archify-panel/test/smoke.mjs /tmp/archify-smoke # server: render and read artifacts
+node ui-plugins/archify-panel/test/panel-run.mjs # panel: export bridge end to end
+```
+
+### Local development (inline loading)
+
+To develop without the marketplace, load the plugin directory directly via `plugins.dirs` in `~/.zcode/cli/config.json`:
+
+```json
+{ "plugins": { "dirs": ["/absolute/path/to/archify-panel"] } }
+```
+
+- **Use an absolute path.** The desktop app expands `~/`, CLI tools do not.
+- **Each `plugins.dirs` entry is a plugin root** (containing `.zcode-plugin/plugin.json` directly), not a parent directory of several plugins.
+- **Do not install this plugin from a marketplace at the same time.** The host deduplicates by `name@marketplace`; `archify-panel@inline` and `archify-panel@` are separate keys and both would load — two MCP processes, duplicate panel registrations and skills.
+
+## Structure
+
+```text
+.zcode-plugin/plugin.json manifest: MCP server + side panel declaration
+skills/archify-panel/SKILL.md skill: how the agent renders and drives the panel
+dist/ build output: MCP server and panel frontend
+vendor/archify/ bundled Archify runtime (Apache-2.0)
+assets/icon.png plugin icon
+```
+
+Source (`src/`, `test/` and build scripts) lives in `ui-plugins/archify-panel/` in this repository.
+
+## How it works
+
+The agent calls `render_diagram`; the server runs Archify's `finalize` pipeline (validation, delivery, static checks, browser measurement) and writes the artifact to the workspace `.archify-panel/`, registering it as the current diagram. The side panel reads the artifact HTML via an MCP resource and embeds it in full-interaction mode inside an inner iframe `srcdoc`; the shell renders no toolbar and keeps no status bar, surfacing only a brief toast on errors and export results.
+
+Exports go through the diagram's own "Export" menu. Sandboxed iframes block native downloads, so the panel keeps a permanent export bridge: it intercepts the binary export output, saves it to `.archify-panel/exports/` via `save_export`, and asks the host to open a save dialog.
+
+## Upstream & third-party components
+
+- Upstream source repository: [tt-a1i/archify](https://github.com/tt-a1i/archify). Bundled runtime is Archify v3.2.0, Apache-2.0 (historical MIT grants for pre-transition contributions remain in effect). See [NOTICE.md](NOTICE.md), including modifications declared under Apache-2.0 §4(b).
+- `@modelcontextprotocol/sdk` and `@modelcontextprotocol/ext-apps` (MIT): build-time dependencies, bundled into `dist/`.
+- The icon is original artwork generated for this plugin; no Archify trademark is used.
+
+This plugin is not affiliated with or endorsed by the Archify project.
+
+## License
+
+Apache-2.0
diff --git a/external_plugins/archify-panel/README_CN.md b/external_plugins/archify-panel/README_CN.md
new file mode 100644
index 00000000..1d60846e
--- /dev/null
+++ b/external_plugins/archify-panel/README_CN.md
@@ -0,0 +1,98 @@
+# Archify 侧栏画板（archify-panel）
+
+
+
+
+
diff --git a/ui-plugins/archify-panel/stage.mjs b/ui-plugins/archify-panel/stage.mjs
new file mode 100644
index 00000000..b6c55a86
--- /dev/null
+++ b/ui-plugins/archify-panel/stage.mjs
@@ -0,0 +1,11 @@
+import { cp } from "node:fs/promises";
+import { join } from "node:path";
+
+// 把打包的 Archify 运行时复制进安装目录
+const installDir = process.env.ZCODE_PLUGIN_INSTALL_DIR;
+if (!installDir) throw new Error("ZCODE_PLUGIN_INSTALL_DIR is not set");
+
+await cp(join(import.meta.dirname, "vendor"), join(installDir, "vendor"), {
+ recursive: true,
+ dereference: true,
+});
diff --git a/ui-plugins/archify-panel/test/cdp.mjs b/ui-plugins/archify-panel/test/cdp.mjs
new file mode 100644
index 00000000..8400d61d
--- /dev/null
+++ b/ui-plugins/archify-panel/test/cdp.mjs
@@ -0,0 +1,115 @@
+import { spawn } from 'node:child_process';
+
+const CHROME = '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome';
+
+export async function launchChrome(port = 9333) {
+ const child = spawn(
+ CHROME,
+ [
+ '--headless=new',
+ '--disable-gpu',
+ '--no-sandbox',
+ '--hide-scrollbars',
+ `--remote-debugging-port=${port}`,
+ '--user-data-dir=/tmp/archify-cdp-profile',
+ 'about:blank',
+ ],
+ { stdio: ['ignore', 'pipe', 'pipe'] },
+ );
+
+ const endpoint = await new Promise((resolve, reject) => {
+ let buffer = '';
+ const timer = setTimeout(() => reject(new Error('Chrome 没有报告调试端口')), 30000);
+ child.stderr.on('data', (chunk) => {
+ buffer += String(chunk);
+ const match = buffer.match(/DevTools listening on (ws:\/\/\S+)/);
+ if (match) {
+ clearTimeout(timer);
+ resolve(match[1]);
+ }
+ });
+ });
+
+ const socket = new WebSocket(endpoint);
+ await new Promise((resolve, reject) => {
+ socket.addEventListener('open', resolve, { once: true });
+ socket.addEventListener('error', reject, { once: true });
+ });
+
+ let nextId = 1;
+ const pending = new Map();
+ const listeners = [];
+
+ socket.addEventListener('message', (event) => {
+ const message = JSON.parse(String(event.data));
+ if (message.id && pending.has(message.id)) {
+ const { resolve, reject } = pending.get(message.id);
+ pending.delete(message.id);
+ if (message.error) reject(new Error(message.error.message));
+ else resolve(message.result);
+ return;
+ }
+ for (const listener of listeners) listener(message);
+ });
+
+ const send = (method, params = {}, sessionId) =>
+ new Promise((resolve, reject) => {
+ const id = nextId++;
+ pending.set(id, { resolve, reject });
+ socket.send(JSON.stringify({ id, method, params, ...(sessionId ? { sessionId } : {}) }));
+ });
+
+ return {
+ send,
+ on(listener) {
+ listeners.push(listener);
+ },
+ close() {
+ socket.close();
+ child.kill();
+ },
+ };
+}
+
+export async function openPage(client, url) {
+ const { targetId } = await client.send('Target.createTarget', { url: 'about:blank' });
+ const { sessionId } = await client.send('Target.attachToTarget', { targetId, flatten: true });
+ const logs = [];
+ client.on((message) => {
+ if (message.sessionId !== sessionId) return;
+ if (message.method === 'Runtime.consoleAPICalled') {
+ logs.push(
+ `${message.params.type}: ${message.params.args.map((arg) => arg.value ?? arg.description ?? '').join(' ')}`,
+ );
+ }
+ if (message.method === 'Runtime.exceptionThrown') {
+ logs.push(`exception: ${message.params.exceptionDetails.text} ${message.params.exceptionDetails.exception?.description ?? ''}`);
+ }
+ });
+ await client.send('Runtime.enable', {}, sessionId);
+ await client.send('Page.enable', {}, sessionId);
+ await client.send('Page.navigate', { url }, sessionId);
+ return { sessionId, logs };
+}
+
+export async function evaluate(client, sessionId, expression) {
+ const result = await client.send(
+ 'Runtime.evaluate',
+ { expression, awaitPromise: true, returnByValue: true },
+ sessionId,
+ );
+ if (result.exceptionDetails) {
+ throw new Error(result.exceptionDetails.exception?.description ?? result.exceptionDetails.text);
+ }
+ return result.result.value;
+}
+
+export async function waitFor(client, sessionId, expression, timeoutMs = 30000, intervalMs = 300) {
+ const deadline = Date.now() + timeoutMs;
+ while (Date.now() < deadline) {
+ const value = await evaluate(client, sessionId, expression);
+ if (value) return value;
+ await new Promise((resolve) => setTimeout(resolve, intervalMs));
+ }
+ return undefined;
+}
diff --git a/ui-plugins/archify-panel/test/panel-harness.mjs b/ui-plugins/archify-panel/test/panel-harness.mjs
new file mode 100644
index 00000000..5f587246
--- /dev/null
+++ b/ui-plugins/archify-panel/test/panel-harness.mjs
@@ -0,0 +1,115 @@
+import { mkdirSync, readFileSync, writeFileSync } from 'node:fs';
+import { dirname, join } from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const root = dirname(dirname(fileURLToPath(import.meta.url)));
+const outputDir = process.argv[2] || '/tmp/archify-panel-harness';
+mkdirSync(outputDir, { recursive: true });
+
+const artifactPath = process.argv[3];
+if (!artifactPath) {
+ console.error('用法：node test/panel-harness.mjs <输出目录> <产物 html>');
+ process.exit(1);
+}
+
+const artifact = readFileSync(artifactPath, 'utf8');
+const artifactBase64 = Buffer.from(artifact, 'utf8').toString('base64');
+const panel = readFileSync(join(root, 'dist', 'ui', 'panel.html'), 'utf8');
+writeFileSync(join(outputDir, 'panel.html'), panel, 'utf8');
+
+const diagram = {
+ id: 'test-diagram',
+ title: '测试图',
+ type: 'workflow',
+ quality: 'showcase',
+ bytes: artifact.length,
+ createdAt: new Date().toISOString(),
+ gates: { validate: 'pass', deliver: 'pass', check: 'pass', 'browser-check': 'pass' },
+ degraded: false,
+ htmlPath: artifactPath,
+};
+
+const harness = `
+WAITING
+
+
+`;
+
+writeFileSync(join(outputDir, 'harness.html'), harness, 'utf8');
+console.log(join(outputDir, 'harness.html'));
diff --git a/ui-plugins/archify-panel/test/panel-run.mjs b/ui-plugins/archify-panel/test/panel-run.mjs
new file mode 100644
index 00000000..2a0ed412
--- /dev/null
+++ b/ui-plugins/archify-panel/test/panel-run.mjs
@@ -0,0 +1,40 @@
+import { createServer } from 'node:http';
+import { readFile } from 'node:fs/promises';
+import { extname, join } from 'node:path';
+import { evaluate, launchChrome, openPage, waitFor } from './cdp.mjs';
+
+const harnessDir = process.argv[2] || '/tmp/archify-panel-harness';
+
+const types = { '.html': 'text/html; charset=utf-8', '.js': 'text/javascript; charset=utf-8' };
+const server = createServer(async (request, response) => {
+ const name = (request.url ?? '/').split('?')[0] === '/' ? '/harness.html' : request.url;
+ try {
+ const body = await readFile(join(harnessDir, name));
+ response.writeHead(200, { 'content-type': types[extname(name)] ?? 'application/octet-stream' });
+ response.end(body);
+ } catch {
+ response.writeHead(404);
+ response.end('not found');
+ }
+});
+await new Promise((resolve) => server.listen(8732, '127.0.0.1', resolve));
+
+const client = await launchChrome();
+const { sessionId, logs } = await openPage(client, 'http://127.0.0.1:8732/harness.html');
+
+const title = await waitFor(
+ client,
+ sessionId,
+ "document.title.startsWith('RESULT') || document.title.startsWith('ERROR') ? document.title : ''",
+ 60000,
+);
+console.log('面板结果：', title);
+console.log('控制台输出：');
+for (const line of logs.slice(0, 25)) console.log(' ', line);
+
+const status = await evaluate(client, sessionId, 'document.title');
+console.log('最终标题：', status);
+
+client.close();
+server.close();
+process.exit(0);
diff --git a/ui-plugins/archify-panel/test/smoke.mjs b/ui-plugins/archify-panel/test/smoke.mjs
new file mode 100644
index 00000000..df5dfed3
--- /dev/null
+++ b/ui-plugins/archify-panel/test/smoke.mjs
@@ -0,0 +1,53 @@
+import { mkdir, readFile } from 'node:fs/promises';
+import { dirname, join } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { Client } from '@modelcontextprotocol/sdk/client/index.js';
+import { StdioClientTransport } from '@modelcontextprotocol/sdk/client/stdio.js';
+
+const root = dirname(dirname(fileURLToPath(import.meta.url)));
+const workspace = process.argv[2] || root;
+await mkdir(workspace, { recursive: true });
+
+const transport = new StdioClientTransport({
+ command: process.execPath,
+ args: [join(root, 'dist', 'server.mjs')],
+ cwd: workspace,
+ env: { ...process.env, ZCODE_WORKSPACE_ROOT: workspace },
+});
+
+const client = new Client({ name: 'smoke', version: '0.1.0' });
+await client.connect(transport);
+
+const tools = await client.listTools();
+console.log('工具：', tools.tools.map((tool) => tool.name).join(', '));
+
+const spec = JSON.parse(
+ await readFile(join(root, 'vendor', 'archify', 'examples', 'agent-tool-call.workflow.json'), 'utf8'),
+);
+const rendered = await client.callTool({
+ name: 'render_diagram',
+ arguments: { type: 'workflow', spec, title: '冒烟测试图' },
+});
+console.log('渲染：', JSON.stringify(rendered.structuredContent));
+
+const diagramId = rendered.structuredContent?.diagram?.id;
+const artifact = await client.readResource({ uri: `archify://artifact-interactive/${diagramId}` });
+const html = artifact.contents[0]?.text ?? '';
+console.log('产物长度：', html.length, '含导出菜单：', html.includes('exportMenu'));
+
+const current = await client.callTool({ name: 'get_current_diagram', arguments: {} });
+console.log('当前图：', JSON.stringify(current.structuredContent));
+
+const saved = await client.callTool({
+ name: 'save_export',
+ arguments: {
+ name: '冒烟测试.png',
+ data: Buffer.from('png-bytes').toString('base64'),
+ encoding: 'base64',
+ directory: '.archify-panel/exports',
+ },
+});
+if (saved.isError) throw new Error(`save_export 失败：${JSON.stringify(saved.content)}`);
+console.log('导出：', JSON.stringify(saved.structuredContent));
+
+await client.close();
diff --git a/ui-plugins/archify-panel/tsconfig.json b/ui-plugins/archify-panel/tsconfig.json
new file mode 100644
index 00000000..92cc1c79
--- /dev/null
+++ b/ui-plugins/archify-panel/tsconfig.json
@@ -0,0 +1,21 @@
+{
+ "compilerOptions": {
+ "target": "ES2022",
+ "module": "ESNext",
+ "moduleResolution": "bundler",
+ "lib": ["ES2022", "DOM", "DOM.Iterable"],
+ "types": ["node"],
+ "strict": true,
+ "noUncheckedIndexedAccess": true,
+ "noImplicitOverride": true,
+ "noUnusedLocals": true,
+ "noUnusedParameters": true,
+ "skipLibCheck": true,
+ "esModuleInterop": true,
+ "resolveJsonModule": true,
+ "isolatedModules": true,
+ "verbatimModuleSyntax": true,
+ "noEmit": true
+ },
+ "include": ["src/**/*.ts"]
+}
diff --git a/ui-plugins/archify-panel/vendor/archify/LICENSE b/ui-plugins/archify-panel/vendor/archify/LICENSE
new file mode 100644
index 00000000..d6456956
--- /dev/null
+++ b/ui-plugins/archify-panel/vendor/archify/LICENSE
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/ui-plugins/archify-panel/vendor/archify/LICENSE-MIT b/ui-plugins/archify-panel/vendor/archify/LICENSE-MIT
new file mode 100644
index 00000000..0f9f9397
--- /dev/null
+++ b/ui-plugins/archify-panel/vendor/archify/LICENSE-MIT
@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2026 tt-a1i (Archify)
+Copyright (c) 2025 Cocoon AI
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/ui-plugins/archify-panel/vendor/archify/NOTICE b/ui-plugins/archify-panel/vendor/archify/NOTICE
new file mode 100644
index 00000000..b63fbccc
--- /dev/null
+++ b/ui-plugins/archify-panel/vendor/archify/NOTICE
@@ -0,0 +1,26 @@
+Archify
+Copyright (c) 2026 tt-a1i (Archify)
+Copyright (c) 2025 Cocoon AI
+
+Archify is distributed under the Apache License, Version 2.0 (LICENSE),
+except where a file, package manifest, or third-party notice specifies otherwise.
+The separately versioned DeepSeek Harness adapter remains MIT; its bundled
+Skill retains the license of the immutable source selected in release.json.
+
+Code and contributions received under the MIT License through pre-transition
+commit 25cf37080fc8b1dbe758a4efc3935b55f3327083 remain available under their
+original terms. Previously published releases keep their existing licenses. The complete historical MIT
+copyright and permission notice is preserved in LICENSE-MIT. This transition
+does not revoke existing MIT grants or assert a new patent grant on behalf
+of historical contributors.
+
+Archify originated from Cocoon-AI/architecture-diagram-generator:
+https://github.com/Cocoon-AI/architecture-diagram-generator
+
+Third-party components retain their own licenses; see THIRD_PARTY_NOTICES.md
+and the license files beside those components. Names and logos do not imply
+official endorsement, and the software license grants no general trademark
+permission.
+
+These software licenses cover Archify's embedded runtime and templates, not
+ownership of a user's authored content, business data, or source repository.
diff --git a/ui-plugins/archify-panel/vendor/archify/SKILL.md b/ui-plugins/archify-panel/vendor/archify/SKILL.md
new file mode 100644
index 00000000..380de2c1
--- /dev/null
+++ b/ui-plugins/archify-panel/vendor/archify/SKILL.md
@@ -0,0 +1,137 @@
+---
+name: archify
+description: "Create validated architecture, workflow, sequence, data-flow, lifecycle/state, ERD, class, tree, timeline, and waterfall diagrams as explorable standalone HTML with dark/light themes, motion and image/SVG/WebM export. Accept requirements or Mermaid; inspect repository evidence for code-backed diagrams. Use when visualizing systems, API calls, pipelines, schemas, histories, timings, or everyday steps, parts, relationships and states. Also turn an answer into a one-page explainer, with the conclusion first, structured panels, native diagrams and charts, when the user asks for a page, an explainer or an answer to share (做成一页, 用页面讲), or proactively when the user's rules opt in with an [archify explainer: ...] line. Not for dashboards."
+license: Apache-2.0
+metadata:
+ version: "3.2"
+ author: tt-a1i
+---
+
+# Archify
+
+Create checked standalone HTML as a native diagram or a one-page explainer that answers a question.
+
+Run commands from your working directory. Unless the user names another location, give each new artifact request its own folder `.archify/--/` there (local time, chosen once): keep the candidate and `.html` in it and reuse it for repairs. Native diagrams use `candidate.json` with `meta.output` relative to the working directory; explainers may use `candidate.archify.md` and a portable output filename. A later request gets a new folder. Replace `bin/archify.mjs` in every command with the installed package's absolute path, or its path relative to your working directory; CLI input and output paths resolve from that directory.
+
+For a native diagram of a real codebase, read [Repository authoring](references/repository-authoring.md) while tracing the requested behavior. A system description uses the native steps below; a frozen candidate uses the handoff path.
+
+## Choose the artifact
+
+- When the user asks to draw or visualize a system, flow, schema or history, use a native diagram and the Type router.
+- Use `explainer` when the user asks for the answer as a page: a page, one page, an explainer, something to share (“做成一页”, “用页面讲”, “answer with a page”). Without such a request, answer in text or draw the requested diagram. A page made on request ends its reply with the one-line mode offer under Output.
+- A rules line in context changes this. `[archify explainer: proactive]`: also make a page, unasked, for an explanation, comparison, trade-off, decision, diagnosis, review or plan that needs a table, steps or several sections. `[archify explainer: always-on]`: every reply that reaches a conclusion also gets a compact page of at most four panels, delivered without opening it, its link closing the reply. `[archify explainer: on-demand]`: only when asked, and never offer a mode.
+- In every mode a page needs a conclusion with some structure behind it: chat, one-line answers, raw command output and text-only requests get none.
+- For `explainer`, read [Explainer authoring](references/explainer-authoring.md) for its conclusion, reasons, scope, board layout and optional native diagrams. Write the complete draft, then run `finalize explainer` for validation, atomic delivery and artifact checks. Use panel patch for local content revisions.
+
+## Existing candidate handoff
+
+When the user supplies a frozen candidate, run `finalize` first as one CLI invocation. Its passing receipt completes the automated gates; follow any visual review recommendation under Delivery before claiming visual quality. For repair, follow step 5.
+
+`finalize` includes a bounded update check in its delivery receipt; see Update awareness.
+
+## Native diagram authoring
+
+Use this path for ordinary generation. Read branch references only when their stated trigger applies.
+
+1. Choose `architecture`, `workflow`, `sequence`, `dataflow`, `lifecycle`, `erd`, `class`, `tree`, `timeline`, or `waterfall` from the question.
+2. Use the exact schema and example paths in the Type router without listing their directories. Read [Authoring defaults](references/authoring-defaults.md) and the mode's example in a bounded batch separate from project documents and complete schemas so neither is truncated; recover any missing section before writing. For Architecture, use the matching showcase example. For every mode except Architecture, also read the mode and common schemas. Read the relevant schema definition before choosing any new field, enum, or constrained text, especially boundary kinds. Examples teach shape, not facts. Use fresh IDs, wording, and layout. Go directly to the candidate without preliminary help, doctor, starter validation, temporary diagrams, or output-path listing. Query brands only for an explicitly requested mark; read [Brand marks](references/brand-marks.md) for an unknown mark with a user-provided URL.
+3. Once the requested scope and, for a real codebase, [source evidence](references/repository-authoring.md) are covered, write the complete candidate directly without planning coordinates in prose. Choose Architecture abstraction and connected placement using Authoring defaults before coordinates: show the main user journey and necessary branches, preserve control roles and behavior-changing conditions, and leave enough room for actual relationship labels. No node, relationship, source, view, card, or boundary count is a target or ceiling. Use automatic routes first; add explicit routing only for necessary branch, return, supplied geometry, or measured repair. Set `meta.quality_profile` to `"showcase"` unless the user requests dense `standard`. For ERD, use a table-first layout: show every physical column in `entities[].attributes`, keep its SQL type and source comment, state every key role a column carries (`key` takes a role or a list, so a junction column is `["pk", "fk"]`, and every `fk` column also needs `references` like `"orders.id"`), and never move columns into cards as a substitute for the table. Classify tables into functional domains before placement, give each domain a concise `tag`, and place its members in one solid rectangle of grid cells — a single row, a single column, or a filled rectangular block, not an L or diagonal. A tagged table always needs `row`/`col`, because absolute coordinates have no grid cells and a domain whose tables do not fill one rectangle cannot be drawn as a band: the renderer reports `erd/domain-not-drawn` instead of publishing a diagram that cannot name the domain. A multi-domain schema reads best as one domain per column — each `tag` a vertical run — because the reader scales a wide canvas up to the reader width and shrinks a tall one until the page fits, so the wide arrangement is the one that stays complete and legible inside a laptop viewport. A schema-first ERD over roughly 8 tables or 50 fields is itself a dense map: author its first complete-field pass at `standard` and upgrade only once the layout still reads.
+4. Once the complete first candidate is written, run `finalize` directly. Its first gate is showcase validation; successful first drafts need no separate pre-validation. Keep the candidate unchanged while the command runs:
+
+ ```bash
+ node bin/archify.mjs finalize --quality showcase --json
+ ```
+
+ For a repository-backed candidate, include evidence on the first draft and use the complete first command: `node bin/archify.mjs finalize --repo-root --quality showcase --json`. Pass the `--quality` that matches `meta.quality_profile`, such as `standard` for a dense first ERD pass.
+
+ A passing receipt proves the included `validate`, `deliver`, strict `check`, and real-browser `browser-check` gates passed. Use its compact summary; run standalone commands only for a separate request or focused failure diagnosis.
+
+5. A non-zero exit is never success. Read compact stdout or `evidence.summaryReceipt`, then [repair the failed gate](references/delivery-contract.md#failed-finalize-and-candidate-repair), including its repair limit. Preserve requested meaning and source evidence. For several tangled Architecture routes, read [Architecture layout repair](references/architecture-layout-repair.md); for measured field or geometry failures, read [Authoring contract](references/authoring-contract.md). Edit the connected neighborhood and rerun the complete `finalize` command from step 4. Once a run has reached `browser-check`, the output path owns that evidence: give every later run its own `--out-dir /review-`.
+
+## Update awareness
+
+`finalize` and standalone `deliver` include `update` in their receipts. Do not run a separate check for the same delivery. If `update.noticeRequired` is true, read `references/update-awareness.md` and keep one compact update notice in your final response to the user, even after a quality gate fails. For a task with several diagrams, mention the update once in the final response. Snooze or ignore a reminder only when the user explicitly asks; never install or update on your own initiative.
+
+Before the first candidate, use the authoring references and relevant repository source, not Archify implementation or tests. Inspect Archify implementation if diagnostics remain unactionable after focused repairs.
+
+
+## Type router
+
+| Type | Use for | Schema | Example |
+|---|---|---|---|
+| `architecture` | Components, services, cloud/security boundaries, infrastructure; what something everyday is made of | `schemas/architecture.schema.json` | System descriptions, services, libraries, and CLI repos: `examples/web-app.architecture.json`; deployment repos: `examples/production-deployment.architecture.json` |
+| `workflow` | Processes, approval gates, tool calls, runbooks, CI/CD; plans and step-by-step life processes | `schemas/workflow.schema.json` | `examples/agent-tool-call.workflow.json` |
+| `sequence` | API call chains, request lifecycles, async traces, returns; back-and-forth between people | `schemas/sequence.schema.json` | `examples/cache-miss-request.sequence.json` |
+| `dataflow` | Pipelines, ETL/ELT, lineage, governance, consumers; where money or documents go | `schemas/dataflow.schema.json` | `examples/product-analytics.dataflow.json` |
+| `lifecycle` | State/status transitions, retries, waiting and terminal states; where an application or order stands | `schemas/lifecycle.schema.json` | `examples/deployment-release.lifecycle.json` |
+| `erd` | Tables/entities, attributes, primary/foreign/unique keys, cardinality between them | `schemas/erd.schema.json` | `examples/orders.erd.json` |
+| `tree` | Single-parent containment: repository/module trees, capability or feature breakdowns, org-style decomposition | `schemas/tree.schema.json` | `examples/payment-platform.tree.json` |
+| `class` | Classes, interfaces, selected members, and dependency/association/inheritance/realization/composition between types | `schemas/class.schema.json` | `examples/payments.class.json` |
+| `timeline` | When things happened: incident reviews, release histories, timestamped events on a proportional clock with source lanes | `schemas/timeline.schema.json` | `examples/payment-incident.timeline.json` |
+| `waterfall` | Where the time went: span durations, overlap, and nesting of one request or agent run on a common time axis | `schemas/waterfall.schema.json` | `examples/checkout-request.waterfall.json` |
+
+When choosing among native diagram types is ambiguous, run `node bin/archify.mjs guide "" --json`. Scenario proof examples are structural references, not facts to copy.
+
+For an everyday subject, keep the same diagram modes and semantic types, then name them for the reader: use everyday `icon` values and `meta.legend` labels as in [Node icons](references/authoring-contract.md#node-icons). Ask for missing personal facts instead of inventing dates, amounts, or rules.
+
+## Mermaid input
+
+Read Mermaid for topology and meaning, then author fresh Archify JSON; do not mechanically render Mermaid styling.
+
+- `flowchart` / `graph` → `workflow`, or `architecture` for a component map.
+- `sequenceDiagram` → `sequence`; participants become semantic participants and arrows become messages.
+- `stateDiagram` → `lifecycle`; states and transitions retain meaning, not Mermaid style.
+- `erDiagram` → `erd`; entity and relationship names, keys, and cardinality retain meaning, not Mermaid style.
+- `classDiagram` → `class`; type kinds, selected members, and relationship kinds retain meaning, not Mermaid style.
+
+## Delivery
+
+Use the `finalize` command above for the first candidate and after a repair.
+
+`finalize` stops at the first non-passing gate. Its compact stdout and `.finalize-summary.json` are ordinary evidence. A passing run creates no screenshots and reports `visualReview: "not-requested"`.
+
+When a passing Architecture receipt reports `visualReviewRecommendation.signals.resolvedCrossovers`, copy the candidate aside and apply the hints in one edit that changes only node positions and sizes: every node, relationship (including its `from` and `to`), label, and source stays as it was. Rerun the complete `finalize` once with `--out-dir /review-2`, because the previous HTML already owns its browser evidence. `--out-dir` relocates the new browser-check and default finalize receipts, not the HTML or its delivery receipt. Successful delivery rewrites that pair at the requested output path; earlier review evidence remains bound to its original artifact bytes. See [review evidence paths](references/delivery-contract.md#a-new-candidate-at-an-existing-output-path). If that run fails, reports more crossings, or reports the same crossings with more `signals.routesOverSuggestedBends`, restore the copy and finalize it with `--out-dir /review-3`. Do not start a second placement round. Hints about extra bends alone are optional.
+
+When `layoutReviewRecommendation.action` is `inspect-sequence-width`, follow [Sequence width review](references/delivery-contract.md#sequence-width-review) before handing off a newly authored Sequence.
+
+Perceptual review is optional for ordinary generation, including a newly positioned Architecture. Use [Optional capture evidence](references/delivery-contract.md#optional-capture-evidence), with `--out-dir /visual-check`, when the user requests visual review, during development audits, or for a concrete route/browser concern. `visualReviewRecommendation` is advisory. Inspect captures before claiming visual quality; qualify any check claim as automated when perceptual review has not occurred.
+
+Read [Delivery contract](references/delivery-contract.md) for failed gates, standalone commands, provenance/recovery, repeated delivery, exports, or opening. Native diagram recovery follows `deliver` → strict provenance `check` → `browser-check`; captures require strict provenance. Explainer delivery uses validate, deliver and check as described in its authoring guide.
+
+For workflow viewport overflow, read [Workflow viewport repair](references/authoring-contract.md#workflow-viewport-repair) before the next layout edit.
+
+When reporting verification details, distinguish artifact checks, browser evidence, captures, and actual perceptual review. For an explicitly requested immediate preview or active desktop loop, see [Optional opening](references/delivery-contract.md#optional-opening).
+
+## Optional viewer capabilities
+
+Live motion is enabled by default for every rendered diagram; omit `meta.animation`. The Viewer’s Live/Still button controls playback.
+
+Read `references/viewer-runtime.md` only when the user explicitly asks for Share Cards, Route/Reach cards, motion, deep links, presentation, search/focus, or another Viewer Runtime feature.
+
+## Setup and fallback
+
+No install is required inside the skill package. For setup diagnosis, verify with:
+
+```bash
+node bin/archify.mjs doctor
+node bin/archify.mjs demo
+```
+
+For native diagrams, when shell access is unavailable, hand-place architecture SVG into `assets/template.html`, use CSS semantic classes rather than inline colors, and follow the visual review contract in `references/delivery-contract.md`. Explainers require their renderer and real delivery gates; if those are unavailable, report the limitation and give a text answer when useful, without claiming HTML delivery.
+
+## Output
+
+Reply in the user's language, as briefly as the result allows; the diagram carries the content, so a single diagram usually needs one line.
+
+- Lead with a clickable Markdown link to the HTML: a descriptive title, not the file name, and its absolute path, wrapped in `<...>` when it contains spaces.
+- When the user wants to understand a system or codebase rather than draw a described subject, add one or two sentences with the key takeaway. Skip sentences that only restate what the diagram obviously shows.
+- State anything that changes how the diagram should be read: the abstraction level or deliberately omitted parts when a reader might expect them, illustrative rather than measured values, missing source evidence, or requested content dropped or merged during repair.
+- For several diagrams, report completion once with a link to an existing overview or compact per-diagram links, not a directory path.
+
+Do not recap commands, repair rounds, hashes, quality profiles, or check lists; they stay in the receipts. If asked whether the diagram was verified, answer in one line, such as “Automated checks passed; not visually reviewed.” Give receipt links and details only for reproducibility or troubleshooting. Disclose requested visual review that could not run, and claim visual inspection only when performed. Keep the required update notice under Update awareness.
+
+Example: `Created [Checkout request timing](/abs/path/checkout-timing.html). Durations are illustrative, not measured.`
+
+For an explainer, reply in two or three lines: the conclusion and the page link. Mention gates only when one failed or writing warnings remain; do not paste the draft.
+
+After an explainer made on request, when no `[archify explainer: ...]` line is in context, end the reply with one optional line offering the proactive mode, once per conversation, for example: “需要的话，以后遇到解释、对比、排查这类问题，我可以主动做成这样的页面，要开启吗？” If the user accepts, add `[archify explainer: proactive] Make an Archify explainer page, unasked, for explanations, comparisons, decisions, diagnoses, reviews and plans that need a table, steps or several sections.` to the global rules file of the current agent (such as `~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md` or `~/.config/devin/AGENTS.md`) and name the file; deleting the line turns it off. If the user declines, offer to add `[archify explainer: on-demand]` so the question does not return.
diff --git a/ui-plugins/archify-panel/vendor/archify/THIRD_PARTY_NOTICES.md b/ui-plugins/archify-panel/vendor/archify/THIRD_PARTY_NOTICES.md
new file mode 100644
index 00000000..4060ce3d
--- /dev/null
+++ b/ui-plugins/archify-panel/vendor/archify/THIRD_PARTY_NOTICES.md
@@ -0,0 +1,78 @@
+# Third-party notices
+
+Archify includes optional vector data for third-party brand marks. These marks
+are provided only to identify technologies and services in user-authored
+diagrams. Their inclusion does not imply sponsorship, endorsement, partnership,
+or affiliation with Archify.
+
+Archify's license and historical MIT grants are described in LICENSE, NOTICE,
+and LICENSE-MIT. The software license does not
+replace the copyright licenses, trademark policies, or brand guidelines that
+apply to third-party marks. Users are responsible for confirming that their
+particular use is permitted.
+
+## Simple Icons
+
+Most of the built-in vector paths and their metadata were generated from
+[Simple Icons 16.28.0](https://github.com/simple-icons/simple-icons/tree/16.28.0).
+Simple Icons makes its collection work available under
+[CC0 1.0 Universal](https://github.com/simple-icons/simple-icons/blob/16.28.0/LICENSE.md).
+
+As Simple Icons explains in its
+[disclaimer](https://github.com/simple-icons/simple-icons/blob/16.28.0/DISCLAIMER.md),
+CC0 for the collection does not mean that every underlying icon is CC0. License
+and brand-guideline metadata may be incomplete or change over time. The absence
+of an individual license entry is not a grant of permission.
+
+Archify embeds the selected icons as vector-path data and may render them in a
+user-selected color. The following individual licenses were recorded in the
+pinned Simple Icons 16.28.0 metadata:
+
+| Mark | Recorded source | Recorded license | Archify treatment |
+|---|---|---|---|
+| Angular | [Angular press kit](https://angular.dev/press-kit) | [`CC-BY-4.0`](https://creativecommons.org/licenses/by/4.0/) | Embedded as vector-path data; color may be changed by the authored diagram. |
+| Apache Airflow | [Apache logos](https://apache.org/logos) | [`Apache-2.0`](https://www.apache.org/licenses/LICENSE-2.0) | Embedded as vector-path data; Apache trademarks remain subject to the [ASF trademark policy](https://www.apache.org/foundation/marks/). |
+| Apache Kafka | [Apache logos](https://apache.org/logos) | [`Apache-2.0`](https://www.apache.org/licenses/LICENSE-2.0) | Embedded as vector-path data; Apache trademarks remain subject to the [ASF trademark policy](https://www.apache.org/foundation/marks/). |
+| .NET | [.NET brand repository](https://github.com/dotnet/brand/blob/c7d0f51b8ec59531332d05fb27a5b758a7a3d689/logo/dotnet-logo.svg) | [`CC0-1.0`](https://creativecommons.org/publicdomain/zero/1.0/) | Embedded as vector-path data; color may be changed by the authored diagram. |
+| JavaScript | [JS community logo](https://github.com/voodootikigod/logo.js/blob/1544bdeed6d618a6cfe4f0650d04ab8d9cfa76d9/js.svg) | [`MIT`](https://github.com/voodootikigod/logo.js/blob/1544bdeed6d618a6cfe4f0650d04ab8d9cfa76d9/LICENSE) | Embedded as vector-path data; color may be changed by the authored diagram. |
+| Jenkins | [Jenkins artwork source](https://get.jenkins.io/art/) | [`CC-BY-SA-3.0`](https://creativecommons.org/licenses/by-sa/3.0/) | Embedded as vector-path data; color may be changed by the authored diagram. Jenkins retains its trademark rights. |
+| Rust | [Rust project](https://www.rust-lang.org) | [`CC-BY-SA-4.0`](https://creativecommons.org/licenses/by-sa/4.0/) | Embedded as vector-path data; color may be changed by the authored diagram. See the [Rust media guide](https://www.rust-lang.org/policies/media-guide). |
+| Vue.js | [Vue logo source](https://github.com/vuejs/art/blob/a1c78b74569b70a25300925b4eacfefcc143b8f6/logo.svg) | [`CC-BY-NC-SA-4.0`](https://creativecommons.org/licenses/by-nc-sa/4.0/) | Embedded as vector-path data; color may be changed by the authored diagram. The non-commercial and share-alike conditions remain applicable; see the [Vue artwork terms](https://github.com/vuejs/art/blob/a1c78b74569b70a25300925b4eacfefcc143b8f6/README.md). |
+
+The source, guideline, and known license fields for every packaged mark are
+preserved in `renderers/shared/generated-brand-marks.mjs`.
+
+## OpenAI mark
+
+The OpenAI vector path is recorded from the
+[OpenAI brand guidelines](https://openai.com/brand/), not from Simple Icons.
+Use remains subject to those current guidelines and any applicable trademark
+rights. Its inclusion does not state or imply endorsement by OpenAI.
+
+## JetBrains Mono
+
+Delivered Archify viewer artifacts embed the JetBrains Mono variable font
+subsets served by Google Fonts. For characters covered by these subsets, font
+selection does not depend on a network request or a locally installed copy.
+Uncovered characters (including CJK) still use the system fallback stack;
+browser and operating-system rasterization can differ.
+JetBrains Mono is maintained at
+[github.com/JetBrains/JetBrainsMono](https://github.com/JetBrains/JetBrainsMono)
+and is distributed under the SIL Open Font License 1.1. The complete license
+text is preserved in `assets/JetBrainsMono-OFL.txt` in the packaged Skill and
+in the font CSS carried by standalone HTML and SVG exports.
+
+## Pele
+
+The explainer renders Mermaid chart fences with an unmodified subset of
+[Pele 1.3.0](https://github.com/obsidianmd/pele), copyright (c) 2026 kepano,
+distributed under the MIT License. The subset and its license text are in
+`explainer/vendor/pele/` in the packaged Skill. Charts are rendered to static
+SVG when a page is built; delivered pages contain no Pele code.
+
+## No additional rights granted
+
+Brand names, logos, and trademarks remain the property of their respective
+owners. This notice records provenance and known terms; it does not grant rights
+that Archify does not hold, and it does not state that every packaged mark has
+been cleared for every commercial, promotional, or redistributive use.
diff --git a/ui-plugins/archify-panel/vendor/archify/assets/JetBrainsMono-OFL.txt b/ui-plugins/archify-panel/vendor/archify/assets/JetBrainsMono-OFL.txt
new file mode 100644
index 00000000..675d198b
--- /dev/null
+++ b/ui-plugins/archify-panel/vendor/archify/assets/JetBrainsMono-OFL.txt
@@ -0,0 +1,93 @@
+Copyright 2020 The JetBrains Mono Project Authors (https://github.com/JetBrains/JetBrainsMono)
+
+This Font Software is licensed under the SIL Open Font License, Version 1.1.
+This license is copied below, and is also available with a FAQ at:
+https://openfontlicense.org
+
+
+-----------------------------------------------------------
+SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded,
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.
diff --git a/ui-plugins/archify-panel/vendor/archify/assets/template.html b/ui-plugins/archify-panel/vendor/archify/assets/template.html
new file mode 100644
index 00000000..51da6984
--- /dev/null
+++ b/ui-plugins/archify-panel/vendor/archify/assets/template.html
@@ -0,0 +1,14768 @@
+
+
+
+
+
+
+
+ [PROJECT NAME] Architecture Diagram
+
+
+
+
+
+
+
+