Two workstation settings did not do what they looked like they did. Both were verified against the live box, not memory.
1. LazyVim had never been installed
~/.config/nvim contained one orphaned lua/matugen.lua (a base16 palette nothing loaded) and no init.lua; ~/.local/share/nvim/ was empty — no plugin tree, ever. pacman.log has no lazyvim line and shell history shows the command typed twice (2026-10-09, 2026-10-15) and dropped: LazyVim is a config framework, not a launcher. nvim has been vanilla the whole time; vim runs Vim 9.2 stock defaults.
Landed (dotfiles tier, direct to main per the live-sync tier law):
dotfiles/lazyvim/ — LazyVim starter, symlinked to ~/.config/lazyvim, with lua/matugen.lua (the palette, now actually applied through RRethy/base16-nvim on ColorScheme, SIGUSR1 reload kept) and lua/plugins/matugen.lua.
dotfiles/zz-blankpad/zsh/.zshrc — lazyvim() = NVIM_APPNAME=lazyvim nvim, so bare nvim stays a vanilla quick-edit editor.
Docs for the prose tier land in the companion PR: omp-docs/tools/neovim.md, tools index, applications.md row, log entry.
2. Auto-speak starts unarmed, and narrates only at the settle
~/.omp/cache/dankvoice.json carried no auto key, and arming is session-scoped (/say on never persists) — so every session began silent. /say start is not a subcommand: it speaks the literal word start. Fixed by "auto": true in the settings file (verified: fresh session reports auto-speak on and one pw-play per segment at turn end).
The cadence problem is in the plugin, not here: auto-speak listened only to agent_end, which fires once per prompt when the loop settles — nothing while the agent works. Tracked and fixed upstream: dank/dankvoice#2.
Two workstation settings did not do what they looked like they did. Both were verified against the live box, not memory.
## 1. LazyVim had never been installed
`~/.config/nvim` contained one orphaned `lua/matugen.lua` (a base16 palette nothing loaded) and no `init.lua`; `~/.local/share/nvim/` was empty — no plugin tree, ever. `pacman.log` has no `lazyvim` line and shell history shows the command typed twice (2026-10-09, 2026-10-15) and dropped: LazyVim is a config framework, not a launcher. `nvim` has been vanilla the whole time; `vim` runs Vim 9.2 stock defaults.
Landed (dotfiles tier, direct to `main` per the live-sync tier law):
- `dotfiles/lazyvim/` — LazyVim starter, symlinked to `~/.config/lazyvim`, with `lua/matugen.lua` (the palette, now actually applied through `RRethy/base16-nvim` on `ColorScheme`, `SIGUSR1` reload kept) and `lua/plugins/matugen.lua`.
- `dotfiles/zz-blankpad/zsh/.zshrc` — `lazyvim()` = `NVIM_APPNAME=lazyvim nvim`, so bare `nvim` stays a vanilla quick-edit editor.
Docs for the prose tier land in the companion PR: `omp-docs/tools/neovim.md`, tools index, `applications.md` row, log entry.
## 2. Auto-speak starts unarmed, and narrates only at the settle
`~/.omp/cache/dankvoice.json` carried no `auto` key, and arming is session-scoped (`/say on` never persists) — so every session began silent. `/say start` is not a subcommand: it speaks the literal word `start`. Fixed by `"auto": true` in the settings file (verified: fresh session reports `auto-speak on` and one `pw-play` per segment at turn end).
The cadence problem is in the plugin, not here: auto-speak listened only to `agent_end`, which fires once per prompt when the loop settles — nothing while the agent works. Tracked and fixed upstream: dank/dankvoice#2.
---
cwd: /home/blank/.omp/wt/wt-20261019-125509-7c8a99d · session: 01a155bb-6474-7366-be9d-629f74af0e05
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two workstation settings did not do what they looked like they did. Both were verified against the live box, not memory.
1. LazyVim had never been installed
~/.config/nvimcontained one orphanedlua/matugen.lua(a base16 palette nothing loaded) and noinit.lua;~/.local/share/nvim/was empty — no plugin tree, ever.pacman.loghas nolazyvimline and shell history shows the command typed twice (2026-10-09, 2026-10-15) and dropped: LazyVim is a config framework, not a launcher.nvimhas been vanilla the whole time;vimruns Vim 9.2 stock defaults.Landed (dotfiles tier, direct to
mainper the live-sync tier law):dotfiles/lazyvim/— LazyVim starter, symlinked to~/.config/lazyvim, withlua/matugen.lua(the palette, now actually applied throughRRethy/base16-nvimonColorScheme,SIGUSR1reload kept) andlua/plugins/matugen.lua.dotfiles/zz-blankpad/zsh/.zshrc—lazyvim()=NVIM_APPNAME=lazyvim nvim, so barenvimstays a vanilla quick-edit editor.Docs for the prose tier land in the companion PR:
omp-docs/tools/neovim.md, tools index,applications.mdrow, log entry.2. Auto-speak starts unarmed, and narrates only at the settle
~/.omp/cache/dankvoice.jsoncarried noautokey, and arming is session-scoped (/say onnever persists) — so every session began silent./say startis not a subcommand: it speaks the literal wordstart. Fixed by"auto": truein the settings file (verified: fresh session reportsauto-speak onand onepw-playper segment at turn end).The cadence problem is in the plugin, not here: auto-speak listened only to
agent_end, which fires once per prompt when the loop settles — nothing while the agent works. Tracked and fixed upstream: dank/dankvoice#2.cwd: /home/blank/.omp/wt/wt-20261019-125509-7c8a99d · session: 01a155bb-6474-7366-be9d-629f74af0e05