assura

Assura is a command-line validation tool for software projects, written in Rust and distributed under a dual MIT / Apache-2.0 license. Its stated goal is to catch project drift while a fix is still small, offering what it calls one fast local signal layer for repository structure, naming, file and section limits, Markdown, references, branch and worktree change pressure, and project-specific policy. The project frames its workflow as "Onboard once. Review while working. Explain when needed. Check before merge," separating Review (described as the radar) from Check (described as the gate). Capabilities described in the README include project-level validation of naming, placement, required or forbidden paths, child and file limits, Markdown, references and generated-output boundaries within one local policy; a compact project review showing configured checks, inactive capabilities, branch/worktree changes, hot directories and ranked next actions; output in text, JSON, YAML, advice, status and agent formats with rule-specific context; agent-ready onboarding that establishes a baseline and installs project-local guidance; reusable policy layers that start language-agnostic and add language or domain rules where needed; migration of supported LS-Lint 2.3 configuration; cold and warm performance evidence; and continuous local validation that keeps a prepared policy warm, coalesces edit bursts and reports coverage scope. Installation is offered through a public shell installer, prebuilt release archives for Linux, macOS and Windows (each containing both assura and an internal assura-full companion that must stay in the same directory), or a source build via cargo. A typical agent-oriented start is shown as agent onboard, review, explain, watch, check; a minimal structure-only start is init followed by check. Configuration lives in .assura/config.yml, with YAML blocks for file and directory naming conventions and exclusion globs. The README states the project is pre-1.0: v0.3.0 is the latest published release, while Review, Explain, onboarding, event-feedback and managed-host activation contracts are assigned to a v0.4.0 candidate that becomes publicly installable only after the tag passes the release gate. A support table marks check plus its output formats, init/status/migrate/hooks and performance reporting as supported in v0.3.0 and the v0.4.0 candidate, and marks review, doctor, explain, agent onboard, agent nudge, the agent integration lifecycle commands, Markdown/link/reference/guidance checks with local content/query/context packs, and watch/cache/daemon/sessions as v0.4.0-candidate surfaces. assura info, Markdown safe fixes and first-party extensions policy families remain experimental; hosted dashboards, automatic broad repair, remote plugin loading, plugin marketplaces and per-agent validation engines are explicitly listed as not supported release surfaces. Releases are tag-driven: version and notes are updated, release-candidate gates are passed, an annotated v* tag is pushed, and the release workflow builds Linux, macOS and Windows archives with checksums. Development uses tiered cargo xtask commands (fast, pr, release-size, release-smoke, release-live, full), and performance claims are tracked through cargo benchmarks, including an LS-Lint comparison. Documentation links cover getting started, configuration, CLI/API reference, support policy, release notes, contributing and security.