Zenzic VS Code – Deterministic Markdown Analysis via LSP

Zenzic released a VS Code extension that brings deterministic markdown analysis to the editor via a thin client using the Language Server Protocol, ensuring sub-50ms feedback and parity with CI/CD pipelines. The extension requires the Zenzic Python binary v0.23.0 or higher and is available on the Visual Studio Marketplace.

Shift-Left to the Keystroke: The Zenzic VS Code Extension Since its inception, Zenzic has operated as a strict, deterministic gatekeeper for CI/CD pipelines. It ensures that no broken links, malformed topology, or hardcoded credentials ever reach production. Today, we are eliminating the latency between authoring a defect and discovering it. We are officially releasing the Zenzic VS Code Extension , bringing the deterministic precision of our engine directly into your authoring environment. The Thin Client Architecture ¶ the-thin-client-architecture Most documentation linters suffer from architectural bloat, bundling heavy Node.js parsers or embedding redundant logic directly into the editor extension. This leads to high memory consumption and fragmented rule sets where the editor behaves differently than the CI pipeline. We rejected this model. The Zenzic VS Code extension is a strictly Thin Client . It contains zero parsing logic, zero regex engines, and zero validation rules. Instead, it utilizes the Language Server Protocol LSP over standard I/O to communicate directly with your local Zenzic Python binary. The result is absolute parity. The exact same engine that governs your GitHub Actions pipeline is now validating your keystrokes in real-time. Sub-50ms Topological Feedback ¶ sub-50ms-topological-feedback By leveraging the zenzic.lsp module and the newly decoupled IncrementalAnalysisEngine introduced in Core v0.23.0 , the extension maintains an in-memory VirtualBufferOverlay . When a document is modified, the engine does not rebuild the entire workspace. It performs an $O K $ incremental patch on the Virtual Site Map VSM , re-evaluating only the modified file and its direct topological dependents. This guarantees sub-50ms latency while preserving graph-wide integrity. Z201 Credential Leak : Paste a GitHub token into your markdown, and it is flagged instantly. Z101 Missing Target : Type a link to a non-existent file, and the diagnostic appears before you save. Z102 Broken Anchor : Modify a heading in file b.md , and any open buffer linking to that specific anchor is immediately invalidated. How to Get Started ¶ how-to-get-started The extension is now publicly available on the Visual Studio Marketplace. Install the Core Engine: The extension requires the Zenzic Python binary v0.23.0 or higher to operate. uv tool install zenzic Install the Extension: Search for Zenzic in the VS Code Extensions panel, or install it via the command line: code --install-extension pythonwoods.zenzic-vscode Configure Optional : If you use a local virtual environment, point the extension to it in your VS Code settings.json : { "zenzic.executablePath": "${workspaceFolder}/.venv/bin/zenzic" } No cloud dependencies. No telemetry. No probabilistic AI guessing. Just deterministic rules enforcing structural integrity.