fix: Assert plugin always throws on defined values (GH #300)

[Koan-Bot]

Summary

Fixes the Template::Plugin::Assert vmethod which always threw "undefined value" errors even when the asserted value was defined.

Root cause: Template::Monad::Assert::AUTOLOAD passed $stash instead of $this to dotop(), causing lookups to search the root stash rather than the hash/list being asserted on.

# Before (broken):
my $value = $stash->dotop($stash, $item, \@args);

# After (fixed):
my $value = $stash->dotop($this, $item, \@args);

Example: [% foo.assert.bar %] where foo = { bar => 999 } would incorrectly throw because it looked for bar in the stash root instead of in foo.

Changes

• lib/Template/Plugin/Assert.pm: One-character fix in Template::Monad::Assert::AUTOLOAD
• t/assert.t: 6 new tests covering defined-value pass-through:
  • Hash value access (hash.assert.foo)
  • Nested hash access (nested.assert.name, nested.assert.deep.value)
  • Array vmethod (items.assert.size, items.assert.first)
  • Direct stash variable (assert.name)

Test plan

• All 6 new assert tests pass
• Full test suite: 2973 tests, all pass

Fixes #300

---

🤖 Generated by Kōan