v0.9.0

Highlights

• A review on every pull request. glasir review [rev] prints what detect_changes and affected_tests know about a change, as Markdown: the risk level and its reasons, the changed symbols, their dependents by distance, the tests that reach the change, and the files the graph does not cover. --fail-on medium turns it into a merge gate. A GitHub Action in this repository (Attackwave/glasir@v0.9.0) runs it on each push to a pull request and keeps one comment current; the graph is built on the runner and no source leaves it.
• Five more coding assistants. glasir install registers with Copilot CLI, Roo Code, Kiro, Amp and Continue, each in its own project file. That makes 14 clients, from one command in the project directory.
• glasir export writes the graph as node-link JSON, the form glasir import reads: every symbol by name, every edge with the tier it was resolved at. For moving a graph into another tool, or comparing two builds.

Agents

• At the handshake, the server now tells a client when to reach for which tool: overview in an unfamiliar tree, query_graph for a question or a file's path, get_code_snippet instead of opening the file, impact or find_callers before a change, detect_changes and affected_tests before a commit. Clients speaking the newer protocol revision received no instructions before.

Install

• Homebrew: brew install attackwave/glasir/glasir
• Scoop: add the bucket Attackwave/scoop-glasir, then run scoop install glasir
• Archives for Linux (static, x86_64 and arm64), macOS (arm64 and x86_64) and Windows are attached, each with a SHA-256 checksum, the licences and an SBOM.