bug: cwd of task not recognized after created with overseer.wrap_template

[SteveWolligandt]

Neovim version (nvim -v)

NVIM v0.10.0-dev-2451+g8b4e26915

Operating system/version

Linux

Describe the bug

Add a template that specifies some cwd:

local tmpl = {
  -- ...
  cwd = vim.fn.getcwd() .. '/../foo'
  -- ...
end} 

return {
  -- ...
  generator = function(opts, cb)
    local templates = {}
    vim.list_extend(templates, create_templates(vim.env.HOME .. '/sim-collection', opts))
    cb({overseer.wrap_template(tmpl, {}, {})})
  end,
  -- ...

Create the task with :OverseerRun and observe this message:

[ERROR] Strategy 'terminal' failed to start for task '<taskname>': Vim:E475: Invalid value for argument cmd: '<cmd>' is not executable

Now I have a pending task. By editing the task, not changing anything, saving and restarting it works then.

What is the severity of this bug?

tolerable (can work around it)

Steps To Reproduce

see describe the bug

Expected Behavior

cwd should work

Minimal example file

No response

Minimal init.lua

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  { "stevearc/dressing.nvim", config = true },
  {
    "stevearc/overseer.nvim",
    config = function()
      require("overseer").setup({
        -- add your overseer config here
      })
    end,
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Additional context

No response