fix deprecation warnings

[abdurrahman-nexthop]

No description provided.

[augment-app-staging]

Thanks for the update to address deprecations. I left a couple of high-confidence notes where the changes could introduce runtime issues.

[augment-app-staging]

Switching to client:notify(...) will pass the client table as the first argument, but Neovim’s LSP client client.notify is typically called with dot notation (client.notify(method, params)) and does not expect self; this can shift arguments and break the call. Consider keeping the dot call here.

🤖 React with 👍 or 👎 to let us know if the comment was useful.

[augment-app-staging]

Similarly, client:request(...) will pass self and shift parameters; Neovim LSP usage expects client.request(method, params, handler, bufnr) with dot notation. This change is likely to cause request failures at runtime.

🤖 React with 👍 or 👎 to let us know if the comment was useful.

[mgmonteleone]

^{Code Review Agent🛡️ with @mgmonteleone's authorization}

Verdict: APPROVE

Thanks for updating the Neovim LSP calls. The switch from vim.lsp.start_client to vim.lsp.start addresses the deprecation path for newer Neovim, and the use of colon notation for client:notify(...) / client:request(...) is appropriate for the Neovim 0.11+ client method surface.

I reviewed the small diff in lua/augment.lua and do not see a blocking compatibility issue in the updated call sites. This keeps the wrapper aligned with current Neovim APIs without changing the higher-level Vimscript-facing behavior.

[mgmonteleone]

Correct and proactive future-proofing for Neovim 0.11+. The colon notation is the documented replacement for the deprecated dot-form calls in Neovim 0.11 and is already supported in ≥0.10. Good work.