The logic for enabling modules is duplicated between lines 163-190 and the autocmd callback in setup_autocmds() (lines 201-228). This violates the DRY principle and makes maintenance harder.

Recommendation: Extract this logic into a separate helper function (e.g., enable_features_for_buffer()) that can be called from both places:

---Enable all loaded modules for the current buffer
---@return nil
local function enable_features_for_buffer()
  if M.list then
    M.list.enable()
  end
  if M.format then
    M.format.enable()
  end
  if M.headers then
    M.headers.enable()
  end
  if M.links then
    M.links.enable()
  end
  if M.images then
    M.images.enable()
  end
  if M.quotes then
    M.quotes.enable()
  end
  if M.callouts then
    M.callouts.enable()
  end
  if M.table then
    require("markdown-plus.table.keymaps").setup_buffer_keymaps(M.config.table or M.table.config)
  end
end

Then call this function from both locations (line 164 and in the autocmd callback).

This new lazy-loading behavior lacks test coverage. According to the custom coding guidelines, all new features must have accompanying tests, and the project aims to maintain minimum 80% coverage.

Recommendation: Add tests in spec/markdown-plus/config_spec.lua to verify:

1. When setup() is called with a markdown buffer already open, features are enabled immediately
2. When setup() is called without a markdown buffer, features are not enabled until FileType autocmd fires
3. Features work correctly in both scenarios (lazy-loaded vs. autocmd-triggered)