remove TODO comments from internal/template package

Converted 9 TODO comments to tracked beans, then reviewed all 8 new beans:

- gozer-mgc0: Use implicitType (scrapped - already implemented)
- gozer-g7gc: Complete template dependency WIP (scrapped - already done)
- gozer-y8wz: Change generate.go log to file (scrapped - stdout is fine)
- gozer-dxhp: Proxy structures in generate.go (scrapped - feature enhancement)
- gozer-kbqm: Save generated code to file (scrapped - stdout is better UX)
- gozer-06x6: Add string comparison to test (scrapped - tests comprehensive)
- gozer-x69k: Move source_code.go (scrapped - file is actively used)
- gozer-9xrj: Add array test data (scrapped - minor enhancement)

All TODOs were either stale (functionality exists), optional enhancements
to build tools, or minor test improvements. None required bug fixes.

Author: Jason-Abbott

.beans/gozer-06x6--add-expected-string-comparison-to-tokenizer-test.md

@@ -0,0 +1,11 @@
+---
+# gozer-06x6
+title: Add expected string comparison to tokenizer test
+status: scrapped
+type: task
+priority: normal
+created_at: 2026-01-19T00:49:41Z
+updated_at: 2026-01-19T00:56:57Z
+---
+
+The tests are already comprehensive and passing. Adding expected string comparisons would be a minor enhancement but doesn't address any actual bug. The Content field already makes it clear what's being selected. Low priority.

.beans/gozer-0o0x--update-code-comments-in-internaltemplate-parser-an.md

@@ -0,0 +1,11 @@
+---
+# gozer-0o0x
+title: Update code comments in internal/template parser and analyzer
+status: completed
+type: task
+priority: normal
+created_at: 2026-01-19T00:03:59Z
+updated_at: 2026-01-19T00:09:48Z
+---
+
+Update code comments in parser and analyzer Go files to be descriptive, succinct, and helpful for engineers not familiar with parsers/analyzers.

.beans/gozer-2jbh--add-comprehensive-tests-for-internaltemplate-packa.md

@@ -0,0 +1,25 @@
+---
+# gozer-2jbh
+title: Add comprehensive tests for internal/template package
+status: completed
+type: task
+priority: normal
+created_at: 2026-01-19T00:01:02Z
+updated_at: 2026-01-19T00:11:50Z
+---
+
+Implement test coverage for the internal/template package which currently has significant gaps:
+- Parser: Zero coverage (most critical)
+- Lexer: Only position tests
+- Public API: Untested
+
+## Checklist
+- [x] Parser tests (parser/parser_test.go)
+- [x] Parser expression tests (parser/parser_expression_test.go)
+- [x] Parser scope tests (parser/parser_scope_test.go)
+- [x] Lexer tests (lexer/lexer_test.go)
+- [x] Public API tests (template_test.go)
+- [x] Integration tests (integration_test.go)
+- [ ] Test fixtures in testdata/ (tests use inline strings, no additional fixtures needed)
+- [x] Verify all tests pass
+- [x] Run golangci-lint (minor style warnings remaining in test files)

.beans/gozer-6c4m--move-createtemplatedefinition-near-its-type.md

@@ -1,11 +1,11 @@
 ---
 # gozer-6c4m
 title: Move CreateTemplateDefinition near its type
-status: todo
+status: completed
 type: task
 priority: low
 created_at: 2026-01-18T22:43:34Z
-updated_at: 2026-01-18T22:43:34Z
+updated_at: 2026-01-19T00:30:46Z
 ---
 
 Code organization improvement in template_dependencies_analysis.go:587.

.beans/gozer-8zde--add-readmemd-to-internaltemplate.md

@@ -0,0 +1,11 @@
+---
+# gozer-8zde
+title: Add README.md to internal/template
+status: completed
+type: task
+priority: normal
+created_at: 2026-01-19T00:14:22Z
+updated_at: 2026-01-19T00:29:10Z
+---
+
+Create a README.md explaining the template package code structure and purpose.

.beans/gozer-9xrj--add-test-data-for-additional-go-types.md

@@ -0,0 +1,11 @@
+---
+# gozer-9xrj
+title: Add test data for additional Go types
+status: scrapped
+type: task
+priority: normal
+created_at: 2026-01-19T00:49:51Z
+updated_at: 2026-01-19T00:57:45Z
+---
+
+The file already covers all major types except arrays. Arrays are handled in the analyzer code (analyzer_inference.go:533, analyzer_compat.go:185) and work similarly to slices in templates. This is a minor test coverage enhancement, not a bug.

.beans/gozer-cch3--refactor-analyzer-gocode-function.md

@@ -1,11 +1,11 @@
 ---
 # gozer-cch3
 title: Refactor analyzer go:code function
-status: todo
+status: completed
 type: task
 priority: normal
 created_at: 2026-01-18T22:43:34Z
-updated_at: 2026-01-18T22:43:34Z
+updated_at: 2026-01-19T00:17:10Z
 ---
 
 Code quality issue in analyzer.go:1666.

.beans/gozer-ccyf--integrate-with-gopls-to-discover-custom-template-f.md

@@ -1,10 +1,11 @@
 ---
 # gozer-ccyf
 title: Integrate with gopls to discover custom template functions
-status: in-progress
+status: completed
 type: feature
+priority: normal
 created_at: 2026-01-18T19:42:01Z
-updated_at: 2026-01-18T19:42:01Z
+updated_at: 2026-01-19T00:24:04Z
 ---
 
 Add support for discovering custom template functions (like Sprig functions or project-specific functions) so they aren't flagged as 'function undefined' errors.
@@ -21,4 +22,13 @@ After fixing builtin function false positives, custom functions added via templa
 ## Research Needed
 - How does gopls expose symbol/type information?
 - Can we find template.FuncMap assignments via LSP?
-- What's the best UX for configuration?
+- What's the best UX for configuration?
+
+## Resolution
+Implemented via direct AST parsing in `funcmap_scanner.go` (approach #1 without gopls dependency):
+- Scans Go source files for `template.FuncMap` definitions
+- Extracts function names from composite literals
+- Supports text/template and html/template imports
+- Handles aliased imports
+- Skips vendor, node_modules, and test files
+- Comprehensive tests in `funcmap_scanner_test.go`

.beans/gozer-dxhp--make-generatego-work-with-proxy-structures.md

@@ -0,0 +1,11 @@
+---
+# gozer-dxhp
+title: Make generate.go work with proxy structures
+status: scrapped
+type: task
+priority: normal
+created_at: 2026-01-19T00:49:33Z
+updated_at: 2026-01-19T00:56:40Z
+---
+
+This is a feature enhancement for a //go:build ignore code generator. The tool works as-is. Proxy structure support is a nice-to-have, not a bug.

.beans/gozer-eik8--fix-template-analysis-false-positives-in-gozer.md

@@ -1,16 +1,31 @@
 ---
 # gozer-eik8
 title: Fix template analysis false positives in gozer
-status: in-progress
+status: completed
 type: bug
+priority: normal
 created_at: 2026-01-18T21:08:34Z
-updated_at: 2026-01-18T21:08:34Z
+updated_at: 2026-01-19T00:26:20Z
 ---
 
 False positives still occurring when linting ../core/web:
 
 1. Method calls with arguments like `.Format "2006-01-02"` flagged as 'only function and method accepts arguments'
-2. Custom template function `timehtml` flagged as 'field or method not found'  
+2. Custom template function `timehtml` flagged as 'field or method not found'
 3. `.CloudLoggingURL $.ProjectID` flagged with both errors
 
-These are valid Go template constructs that should not be flagged.
+These are valid Go template constructs that should not be flagged.
+
+## Resolution
+All three issues have been addressed:
+
+1. **Method calls with arguments** - Fixed in `analyzer_typecheck.go:98-104`. When the receiver type is unknown (`any`), the analyzer no longer reports "only functions and methods accept arguments". Tests added in `integration_test.go`.
+
+2. **Custom template functions** - Fixed via `funcmap_scanner.go` which scans Go source files for `template.FuncMap` definitions and registers custom functions. Functions like `timehtml` can be discovered automatically.
+
+3. **Method calls with variable arguments** - Same fix as #1 handles this case.
+
+Tests confirm no false positives for:
+- `.CreatedAt.Format "Jan 2, 2006"`
+- `.Staff.CreatedAt.Format "Jan 2, 2006"`
+- `.CloudLoggingURL $.ProjectID`