القائمة
Web server architecture and SvelteKit frontend details
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Catalogue of every covalence-* crate — what each one wraps/provides and which layer it lives in. Consult when deciding which crate to use, where new code belongs, or how the workspace is structured.
Performance of the Metamath → HOL import (covalence-metamath + covalence-hol metalogic) — pipeline, hotspots, the bench, and the history of super-linearity fixes
How to profile and optimize covalence — flamegraphs, callgrind/cachegrind, and the scaling-first methodology for finding super-linear work
VSCode extension architecture and LSP server details
Covalence repo layout, dependency graph, and key architectural rules
Performance of the Metamath → HOL import (covalence-metamath + covalence-hol metalogic) — pipeline, hotspots, the bench, and the history of super-linearity fixes
| name | web-server |
| description | Web server architecture and SvelteKit frontend details |
| disable-model-invocation | true |
cov serve)cov serve [--port PORT] [--open] [--api] [--store [PATH]]
→ axum HTTP server on 127.0.0.1:PORT + Unix socket
→ serves embedded SvelteKit static files (rust-embed, requires "static" feature)
→ REST API (see below)
→ --api: serve API only, skip static frontend
→ --store: SQLite persistence
→ SPA fallback: unmatched routes serve index.html
covalence-serve features (all default):
static — embeds SvelteKit build output via rust-embed; disable with --no-default-features to skip static assets entirelyThe SvelteKit app uses adapter-static (pure SPA, ssr = false) so it compiles to plain HTML/JS/CSS that gets embedded into the Rust binary at compile time.
The frontend API base URL is configurable via VITE_COV_API_BASE (defaults to empty = same-origin). To host the static site separately (e.g. GitHub Pages) pointing at a remote backend:
VITE_COV_API_BASE=https://cov.example.com bun run build:web