feat(java): add list variant template filters

.air.toml

@@ -0,0 +1,46 @@
+root = "."
+testdata_dir = "testdata"
+tmp_dir = "tmp"
+
+[build]
+  args_bin = ["serve", "--port", "8080"]
+  bin = "./tmp/main"
+  cmd = "go build -o ./tmp/main ./cmd/apigear"
+  delay = 1000
+  exclude_dir = ["assets", "tmp", "vendor", "testdata", "web", "node_modules", "bin", "docs"]
+  exclude_file = []
+  exclude_regex = ["_test.go"]
+  exclude_unchanged = false
+  follow_symlink = false
+  full_bin = ""
+  include_dir = []
+  include_ext = ["go", "tpl", "tmpl", "html"]
+  include_file = []
+  kill_delay = "0s"
+  log = "build-errors.log"
+  poll = false
+  poll_interval = 0
+  post_cmd = []
+  pre_cmd = []
+  rerun = false
+  rerun_delay = 500
+  send_interrupt = false
+  stop_on_error = false
+
+[color]
+  app = ""
+  build = "yellow"
+  main = "magenta"
+  runner = "green"
+  watcher = "cyan"
+
+[log]
+  main_only = false
+  time = false
+
+[misc]
+  clean_on_exit = false
+
+[screen]
+  clear_on_rebuild = false
+  keep_scroll = true

.claude/commands/git-finish.md

@@ -0,0 +1,76 @@
+# Git Finish - Complete Feature Branch
+
+Finalize the feature branch and prepare for merging or creating a pull request.
+
+## Instructions
+
+1. Run `git status` to ensure all changes are committed
+2. If there are uncommitted changes, prompt user to commit them first (suggest using `/git-step`)
+3. Run `git log main..HEAD` to show all commits on this branch
+4. Ask the user what they want to do:
+   - Create a pull request
+   - Merge directly to main (if allowed by workflow)
+   - Push branch without merging
+   - Cancel
+5. Based on user choice:
+
+### Option A: Create Pull Request
+1. Ensure branch is pushed to remote: `git push -u origin <branch-name>`
+2. Analyze all commits to generate PR title and description
+3. Use `gh pr create` to create the pull request with:
+   - Title: Summarize the feature/fix
+   - Body: Include conventional commit format with:
+     - Summary section (bullet points of main changes)
+     - Detailed description
+     - Test plan (checklist of testing steps)
+     - Related issues (if any)
+4. Return the PR URL
+
+### Option B: Merge to Main
+1. Switch to main branch
+2. Pull latest changes: `git pull origin main`
+3. Merge feature branch: `git merge --no-ff <branch-name>`
+4. Push to remote: `git push origin main`
+5. Optionally delete feature branch locally and remotely
+6. Confirm merge successful
+
+### Option C: Push Only
+1. Push branch to remote: `git push -u origin <branch-name>`
+2. Provide instructions for creating PR manually
+3. Confirm push successful
+
+## Pull Request Template
+
+```markdown
+## Summary
+- <bullet point of main change>
+- <bullet point of another change>
+
+## Description
+<Detailed description of what was done and why>
+
+## Test Plan
+- [ ] Unit tests pass
+- [ ] Integration tests pass
+- [ ] Manual testing completed
+- [ ] Documentation updated
+
+## Related Issues
+Closes #<issue-number>
+```
+
+## Pre-Merge Checklist
+
+Before finishing, verify:
+- [ ] All tests pass
+- [ ] Code follows project conventions
+- [ ] Documentation is updated
+- [ ] No merge conflicts with main
+- [ ] Commit messages follow conventional commits
+- [ ] No sensitive data in commits
+
+## Branch Cleanup
+
+After successful merge, optionally:
+- Delete local branch: `git branch -d <branch-name>`
+- Delete remote branch: `git push origin --delete <branch-name>`

.claude/commands/git-start.md

@@ -0,0 +1,38 @@
+# Git Start - Create Feature Branch
+
+Create a new feature branch from the main branch following best practices.
+
+## Instructions
+
+1. Ask the user for a feature name/description if not provided as an argument
+2. Generate a branch name using the format: `feature/<descriptive-name>` or `fix/<descriptive-name>`
+   - Use kebab-case for the branch name
+   - Keep it concise but descriptive
+   - Suggest the branch name to the user for approval
+3. Check the current git status to ensure working directory is clean
+4. If there are uncommitted changes, ask the user what to do (commit, stash, or abort)
+5. Switch to main branch and pull latest changes
+6. Create and checkout the new feature branch
+7. Confirm the new branch has been created and is active
+
+## Example Usage
+
+```
+/git-start user-authentication
+/git-start fix login bug
+/git-start
+```
+
+## Branch Naming Convention
+
+- `feature/<name>` - For new features
+- `fix/<name>` - For bug fixes
+- `refactor/<name>` - For refactoring
+- `docs/<name>` - For documentation changes
+- `test/<name>` - For test improvements
+
+## Best Practices
+
+- Always start from an updated main branch
+- Use descriptive branch names that reflect the work
+- Ensure working directory is clean before branching

.claude/commands/git-step.md

@@ -0,0 +1,69 @@
+# Git Step - Commit Changes with Conventional Commits
+
+Commit current changes using conventional commit format.
+
+## Instructions
+
+1. Run `git status` to check for changes
+2. Run `git diff` to see the changes
+3. Analyze the changes and determine the appropriate conventional commit type
+4. Draft a conventional commit message following the format:
+   ```
+   <type>(<scope>): <description>
+
+   [optional body]
+
+   [optional footer]
+   ```
+5. Present the commit message to the user for approval
+6. Stage the relevant files using `git add`
+7. Create the commit with the approved message
+8. Confirm the commit was successful with `git log -1`
+
+## Conventional Commit Types
+
+- `feat` - A new feature
+- `fix` - A bug fix
+- `docs` - Documentation only changes
+- `style` - Changes that don't affect code meaning (formatting, etc.)
+- `refactor` - Code change that neither fixes a bug nor adds a feature
+- `perf` - Performance improvement
+- `test` - Adding or correcting tests
+- `build` - Changes to build system or dependencies
+- `ci` - Changes to CI configuration
+- `chore` - Other changes that don't modify src or test files
+
+## Scope Examples
+
+- Package names: `cfg`, `gen`, `mcp`, `idl`, etc.
+- Component names: `filters`, `parser`, `commands`
+- Feature areas: `auth`, `templates`, `monitoring`
+
+## Message Guidelines
+
+- Use imperative mood in description ("add" not "added" or "adds")
+- Don't capitalize first letter of description
+- No period at the end of description
+- Keep description under 72 characters
+- Use body to explain what and why (not how)
+- Reference issues in footer: `Fixes #123` or `Closes #456`
+
+## Examples
+
+```
+feat(gen): add support for external types in JNI filter
+fix(mcp): correct tool annotations for registry operations
+docs: add comprehensive package documentation
+test(helper): add unit tests for string utilities
+refactor(cmd): simplify command flag parsing
+```
+
+## Breaking Changes
+
+For breaking changes, add `!` after type/scope and include `BREAKING CHANGE:` in footer:
+```
+feat(api)!: change configuration file format
+
+BREAKING CHANGE: Configuration files now use YAML instead of JSON.
+Migration guide available in docs/migration.md
+```

.github/workflows/release.yml

@@ -17,10 +17,30 @@ jobs:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
-      - uses: actions/setup-go@v4
+
+      - uses: actions/setup-go@v5
+        with:
+          go-version: "1.26.x"
+
+      - uses: pnpm/action-setup@v4
+        with:
+          version: 9
+
+      - uses: actions/setup-node@v4
         with:
-          go-version: 1.24.x
-      - run: go test ./...
+          node-version: '20'
+          cache: 'pnpm'
+          cache-dependency-path: 'web/pnpm-lock.yaml'
+
+      - name: Install frontend dependencies
+        run: cd web && pnpm install --frozen-lockfile
+
+      - name: Build frontend
+        run: cd web && pnpm build
+
+      - name: Run backend tests
+        run: go test ./...
+
       - uses: goreleaser/goreleaser-action@v5
         with:
           distribution: goreleaser

.github/workflows/tests.yml

@@ -17,14 +17,34 @@ jobs:
   test:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/setup-go@v4
-        with:
-          go-version: "1.24.x"
       - uses: actions/checkout@v4
+
+      - uses: actions/setup-go@v5
+        with:
+          go-version: "1.26.x"
+
       - uses: actions/cache@v4
         with:
           path: |
             ~/go/pkg/mod
             ~/.cache/go-build
-          key: ${{ runner.os }}-${{ hashFiles('**/go.sum') }}
-      - run: go test ./...
+          key: ${{ runner.os }}-go-${{ hashFiles('**/go.sum') }}
+
+      - uses: pnpm/action-setup@v4
+        with:
+          version: 9
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'pnpm'
+          cache-dependency-path: 'web/pnpm-lock.yaml'
+
+      - name: Install Task
+        uses: arduino/setup-task@v2
+        with:
+          version: 3.x
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Run CI checks
+        run: task ci:all

.gitignore

@@ -41,3 +41,14 @@ coverage.txt
 
 **/__debug*
 apigear
+
+# Web UI
+web/node_modules/
+web/dist/*
+!web/dist/.gitkeep
+web/.vite/
+web/.pnpm-store
+
+# Development tools
+.overmind.sock
+build-errors.log