A hardened Neovim configuration for daily work — editing, projects, diagnostics, Git, and a Markdown/Obsidian workbench — built on the Radium colorscheme.
Built on the Radium colorscheme; hardened across the v0.2.x series of audits and patches.
A hardened Neovim configuration for daily work — editing, projects, diagnostics, Git, and a Markdown/Obsidian workbench — built on the Radium colorscheme.
Canonical facts
Domain
content-platform
Version
0.2.8.6
Updated
2026-07-02
Maintainer
azwerks
Proof
supported
!Requires Neovim 0.12+. Treesitter Markdown highlighting ships disabled by default for stability.
▸How the record thinks
02
Key decisions
04
▸Decision
Where does the editor's color come from?
ChosenVendor the Phase 1 Radium colorscheme as the single source of visual truth; nothing defines color outside it.
One color authority keeps the editor coherent with the rest of azwerks and makes theme changes a single edit.
Alternatives considered
×Hand-tune highlights per plugin — Drifts instantly and can't stay in sync with the web system.
Consequences accepted
→Every highlight resolves back to a Radium token.
→Theme metadata is pinned to a specific Radium version (v0.2.7.1).
Source
azwerks-radium.nvim
▸Decision
How much should the config lean on plugins?
ChosenPlugin restraint always — the dashboard, winbar, and Markdown workbench are native Lua, not imported UI frameworks.
A controlled config stays repairable and fast; every plugin is a maintenance and failure surface.
Alternatives considered
×Adopt a batteries-included distro — Sprawls, hides behavior, and is hard for the user to repair.
Consequences accepted
→More native Lua to maintain, but far fewer moving parts.
→The interface shell adds zero plugin dependencies.
Manager
lazy.nvim
▸Decision
Can the state colors be reused decoratively?
ChosenNo. State colors stay semantic, and authored marks stay outside operational editor UI.
If a state hue also decorates a heading, the signal stops meaning anything; the editor must read the same way as every other azwerks surface.
Alternatives considered
×Use state hues as generic accents — Erodes the meaning of the state signal.
Consequences accepted
→Decorative accents come from the neutral/brand ramp, never the state palette.
Doctrine
semantic state colors
▸Decision
What happens when something breaks on a user's machine?
ChosenThe config must be repairable by the user — a health command diagnoses it, and dangerous actions are confirmation-gated.
A daily-driver config people actually rely on has to fail legibly and be fixable without reading the whole source.
Alternatives considered
×Assume it just works and leave failures opaque — Leaves users stuck with no way to diagnose or recover.
Consequences accepted
→:checkhealth azwerks reports on every dependency and subsystem.
→Broad-root and write operations refuse by default until confirmed.
Command
:checkhealth azwerks
▸Lineage
03
History
Operations
feature
featurev0.2.0
completed
Workspace maintenance pack
Trouble, grug-far, todo-comments, aerial, overseer, and mini.surround — the daily-driver toolset.
Intent
Establish the core editing and workspace-navigation capability before any visual work.
Action
Curated a restrained plugin set and wired it through lazy.nvim.
Result
Introduced :AzwerksWorkspaceStatus to inspect the pack from inside Neovim.
featurev0.2.1
completed
Visual identity foundation
Hardened the visual layer without a new plugin stack: expanded Radium highlights, a state-strip Lualine, and per-plugin integration.
Intent
Make the editor unmistakably azwerks while keeping the colorscheme the single source of visual truth.
Action
Expanded Radium highlight coverage and added visual health checks.
Result
Added :AzwerksThemeStatus and :AzwerksVisualStatus.
featurev0.2.2
completed
Interface shell
A native, no-plugin dashboard and a window-local winbar/breadcrumb shell with Markdown heading awareness.
Intent
Provide structure and orientation without importing a heavy UI framework.
Action
Built the dashboard and winbar in native Lua.
Result
A consistent shell that adds no plugin dependencies.
featurev0.2.3
completed
Markdown / Obsidian workbench
Note creation, frontmatter, callouts, wikilinks, and generated TOC as a native Lua module.
Intent
Make Markdown and Obsidian workflows first-class without forcing Obsidian behavior on plain Markdown.
Action
Added a native workbench module gated to the right filetypes.
Result
Knowledge-work and code editing stay equally well-supported.
featurev0.2.4
completed
Project profiles
Scored workspace-root detection across nvim-config, obsidian, node, python, lua, markdown-workspace, and generic-git shapes.
Intent
Adapt behavior to the kind of project without manual configuration.
Action
Implemented a scored root-detection pass over eight project shapes.
Centralized special-surface close behavior, an unnamed-buffer visual regression fix, and a commands/actions safety patch for paths with spaces and broad-root archives.
Intent
Close the last edge cases in close behavior, visuals, and command safety.
Action
Shipped the v0.2.8.4–.6 safety patches.
Result
Current head — v0.2.8.6.
Active maintenance line; further safety patches are expected.
▸How do you know?
04
Evidence
03
:checkhealth azwerks
verified
A dedicated health module checks Neovim version, Git, ripgrep, fd, Node/npm, Python, the vendored Radium colorscheme, Treesitter posture, the Markdown render guard, and project-profile registration.
File:
lua/azwerks/health.lua
Command:
:checkhealth azwerks
Confirmation-gated dangerous actions
reviewed
Broad-root archive and scan operations are refused by default; write and external-script tasks require confirmation with the working directory shown. Documented in the safe-workflows baseline.
File:
docs/SAFE-WORKFLOWS-v0.2.8.md
Reference:
SAFE-WORKFLOWS-v0.2.8
Safety is enforced at runtime through the shared safety layer, not by an external test suite.
Audit-driven patch trail
reviewed
Each hardening release cites the audit that produced it — visual regression, commands/actions safety, project-root safety — with a dated patch-notes document under docs/.
File:
docs/
Location:
docs/*.md
Cadence:
per release
▸Links
06
Relations
Relations
How azwerks-nvim relates to the rest of the register.