Introduce MAL/LAL/Hierarchy V2 engine — replace Groovy DSL runtime with ANTLR4 + Javassist

.claude/skills/ci-e2e-debug/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: ci-e2e-debug
+description: Download and inspect CI e2e test logs from GitHub Actions artifacts. Use when investigating e2e test failures in CI.
+argument-hint: "<RUN_ID or GitHub Actions URL>"
+---
+
+# CI E2E Debug Skill
+
+Download test log artifacts from a GitHub Actions CI run and inspect them for errors.
+
+## Steps
+
+1. **Find the artifact**: Use `gh api` to list artifacts for the given CI run:
+   ```bash
+   gh api repos/apache/skywalking/actions/runs/<RUN_ID>/artifacts --jq '.artifacts[] | {id: .id, name: .name}'
+   ```
+
+2. **Download and extract**: Download the artifact zip and extract it:
+   ```bash
+   cd /tmp && rm -rf e2e-debug-logs && mkdir e2e-debug-logs && cd e2e-debug-logs
+   gh api repos/apache/skywalking/actions/artifacts/<ARTIFACT_ID>/zip > artifact.zip
+   unzip -o artifact.zip
+   ```
+
+3. **Inspect OAP logs**: Look for errors in the OAP server logs:
+   ```bash
+   # Find OAP log files
+   find /tmp/e2e-debug-logs -name "skywalking-oap-*.log" -o -name "oap.log"
+   # Check for errors
+   grep -E "ERROR|Exception|FATAL|CannotCompileException" <log_file> | head -30
+   ```
+
+4. **Inspect other component logs**: Check BanyanDB, UI, and other pod logs as needed.
+
+5. **Report findings**: Summarize the root cause error from the logs.
+
+## Notes
+- CI artifacts are automatically uploaded by the e2e test framework to `$SW_INFRA_E2E_LOG_DIR`
+- Log files are organized by namespace/pod name
+- OAP init pods may have different errors than the main OAP pod — check all of them
+- Common errors: MAL/LAL/OAL compilation failures, storage connection issues, module initialization errors

.claude/skills/compile/SKILL.md

@@ -0,0 +1,109 @@
+---
+name: compile
+description: Build SkyWalking OAP server, run javadoc checks, and verify checkstyle. Use to validate changes before submitting a PR.
+argument-hint: "[all|backend|javadoc|checkstyle|module-name]"
+---
+
+# Compile & Verify
+
+Build the project and run static checks matching CI.
+
+## Prerequisites
+
+- JDK 11, 17, or 21 (LTS versions)
+- Maven 3.6+ (use `./mvnw` wrapper)
+
+## Maven profiles
+
+- `backend` (default): Builds OAP server modules
+- `ui` (default): Builds web application
+- `dist` (default): Creates distribution packages
+- `all`: Builds everything including submodule initialization
+
+## Commands by argument
+
+### `all` or no argument — full CI build
+
+```bash
+./mvnw clean flatten:flatten install javadoc:javadoc -B -q -Pall \
+  -Dmaven.test.skip \
+  -Dcheckstyle.skip \
+  -Dgpg.skip
+```
+
+### `backend` — backend only (faster)
+
+```bash
+./mvnw clean flatten:flatten package -Pbackend,dist -Dmaven.test.skip
+```
+
+### `javadoc` — javadoc check only
+
+Javadoc requires delombok output, so `install` must run first:
+
+```bash
+./mvnw clean flatten:flatten install javadoc:javadoc -B -q -Pall \
+  -Dmaven.test.skip \
+  -Dcheckstyle.skip \
+  -Dgpg.skip
+```
+
+Running `javadoc:javadoc` alone without `install` will miss errors because `${delombok.output.dir}` won't be populated.
+
+### `checkstyle` — checkstyle only
+
+```bash
+./mvnw -B -q clean flatten:flatten checkstyle:check
+```
+
+### Module name — single module build
+
+```bash
+./mvnw clean flatten:flatten package -pl oap-server/analyzer/<module-name> -Dmaven.test.skip
+```
+
+## Reading javadoc output
+
+Maven prefixes all javadoc output with `[ERROR]`, but the actual severity is in the message after the line number. Only lines containing `error:` fail the build; lines with `warning:` do not.
+
+```
+[ERROR] Foo.java:42: error: bad use of '>'        ← ACTUAL ERROR (must fix)
+[ERROR] Foo.java:50: warning: no @param for <T>   ← WARNING (does not fail build)
+```
+
+### Common javadoc errors
+
+| Error | Cause | Fix |
+|-------|-------|-----|
+| `bad use of '>'` | Bare `>` in javadoc HTML (e.g., `->` in `<pre>` blocks) | Use `{@code ->}` or `-&gt;` |
+| heading out of sequence | Heading level skips the expected hierarchy | See heading rules below |
+| reference not found | `{@link Foo#bar()}` with wrong signature | Match exact parameter types: `{@link Foo#bar(ArgType)}` |
+
+### Javadoc heading rules (JDK 13+)
+
+Strict heading validation was introduced in JDK 13. JDK 11 does **not** enforce it, but JDK 17/21/25 do. Write headings correctly for forward compatibility:
+
+| Javadoc location | Start heading at |
+|---|---|
+| Class, interface, enum, package, module | `<h2>` |
+| Constructor, method, field | `<h4>` |
+| Standalone HTML files (`doc-files/`) | `<h1>` |
+
+The generated javadoc page uses `<h1>` for the class name and `<h3>` for member sections (Methods, Fields, etc.), so class-level subsections must use `<h2>` and method-level subsections must use `<h4>` to maintain proper nesting.
+
+## CI reference
+
+CI uses JDK 11 on Linux. The `dist-tar` job runs:
+
+```bash
+./mvnw clean flatten:flatten install javadoc:javadoc -B -q -Pall \
+  -Dmaven.test.skip \
+  -Dcheckstyle.skip \
+  -Dgpg.skip
+```
+
+The `code-style` job runs:
+
+```bash
+./mvnw -B -q clean flatten:flatten checkstyle:check
+```

.claude/skills/generate-classes/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: generate-classes
+description: Generate bytecode classes from DSL scripts (MAL, OAL, LAL, Hierarchy). Runs the compiler and dumps .class files for inspection.
+argument-hint: "<mal|oal|lal|hierarchy|all>"
+---
+
+# Generate DSL Classes
+
+Run the v2 compiler (ANTLR4 + Javassist) to generate bytecode classes from DSL scripts and dump `.class` files to disk for inspection.
+
+## Commands by argument
+
+### `mal` — MAL expression classes
+
+```bash
+./mvnw test -pl test/script-cases/script-runtime-with-groovy/mal-lal-v1-v2-checker \
+  -Dtest=MalComparisonTest -DfailIfNoTests=false -Dcheckstyle.skip
+```
+
+Output location: `test/script-cases/scripts/mal/**/*.generated-classes/`
+
+### `oal` — OAL metrics/dispatcher/builder classes
+
+```bash
+./mvnw test -pl oap-server/oal-rt \
+  -Dtest=RuntimeOALGenerationTest -DfailIfNoTests=false -Dcheckstyle.skip
+```
+
+Output location: `oap-server/oal-rt/target/test-classes/metrics/`, `metrics/builder/`, `dispatcher/`
+
+### `lal` — LAL filter/extractor classes
+
+```bash
+./mvnw test -pl test/script-cases/script-runtime-with-groovy/mal-lal-v1-v2-checker \
+  -Dtest=LalComparisonTest -DfailIfNoTests=false -Dcheckstyle.skip
+```
+
+Output location: `test/script-cases/scripts/lal/**/*.generated-classes/`
+
+### `hierarchy` — Hierarchy rule classes
+
+```bash
+./mvnw test -pl test/script-cases/script-runtime-with-groovy/hierarchy-v1-v2-checker \
+  -Dtest=HierarchyRuleComparisonTest -DfailIfNoTests=false -Dcheckstyle.skip
+```
+
+Output location: `test/script-cases/scripts/hierarchy-rule/*.generated-classes/`
+
+### `all` or no argument — generate all DSLs
+
+Run all four commands above sequentially.
+
+## After generation
+
+Print the output location for the requested DSL so the user knows where to find the generated `.class` files. Use `javap` to decompile:
+
+```bash
+javap -c -p <path-to-class-file>
+```
+
+## Cleaning generated classes
+
+```bash
+./mvnw clean -pl test/script-cases/script-runtime-with-groovy/mal-lal-v1-v2-checker,test/script-cases/script-runtime-with-groovy/hierarchy-v1-v2-checker
+```

.claude/skills/gh-pull-request/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: gh-pull-request
+description: Verify, commit, and push changes on a PR branch. Runs pre-flight checks (compile, checkstyle, license headers) before every push. Also creates the PR if one doesn't exist yet.
+---
+
+# PR Branch Workflow
+
+Run pre-flight checks, commit, push, and optionally create a PR.
+
+## Pre-flight checks
+
+Run these checks before every commit+push and fix any failures:
+
+### 1. Compile and checkstyle
+
+```bash
+# Checkstyle
+./mvnw -B -q clean checkstyle:check
+
+# Full build (compile + javadoc)
+./mvnw clean flatten:flatten install javadoc:javadoc -B -q -Pall \
+  -Dmaven.test.skip \
+  -Dcheckstyle.skip \
+  -Dgpg.skip
+```
+
+### 2. License header check
+
+```bash
+license-eye header check
+```
+
+If invalid files are found, fix with `license-eye header fix` and re-check.
+
+## Commit and push
+
+After checks pass, commit and push:
+
+```bash
+git add <files>
+git commit -m "<message>"
+git push -u origin <branch-name>
+```
+
+### Branch strategy
+- **Never work directly on master branch**
+- If on master, create a new branch first: `git checkout -b feature/<name>` or `git checkout -b fix/<name>`
+
+## Create PR (if not yet created)
+
+Check whether a PR already exists for the current branch:
+
+```bash
+gh pr view --json number 2>/dev/null
+```
+
+If no PR exists, create one:
+
+### PR title
+Summarize the changes concisely. Examples:
+- `Fix BanyanDB query timeout issue`
+- `Add support for OpenTelemetry metrics`
+
+### PR description
+
+Read `.github/PULL_REQUEST_TEMPLATE` and use its **exact format with checkboxes**. Do NOT use a custom summary format.
+
+Key template sections — uncomment the relevant one:
+
+**For Bug Fixes:**
+```
+### Fix <bug description or issue link>
+- [ ] Add a unit test to verify that the fix works.
+- [ ] Explain briefly why the bug exists and how to fix it.
+```
+
+**For New Features:**
+```
+### <Feature description>
+- [ ] If this is non-trivial feature, paste the links/URLs to the design doc.
+- [ ] Update the documentation to include this new feature.
+- [ ] Tests(including UT, IT, E2E) are added to verify the new feature.
+- [ ] If it's UI related, attach the screenshots below.
+```
+
+**For Performance Improvements:**
+```
+### Improve the performance of <class or module or ...>
+- [ ] Add a benchmark for the improvement.
+- [ ] The benchmark result.
+- [ ] Links/URLs to the theory proof or discussion articles/blogs.
+```
+
+**Always include:**
+```
+- [ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #<issue number>.
+- [ ] Update the [`CHANGES` log](https://github.com/apache/skywalking/blob/master/docs/en/changes/changes.md).
+```
+
+### Create command
+
+```bash
+gh pr create --title "<title>" --body "$(cat <<'EOF'
+<PR body from template>
+EOF
+)"
+```
+
+### Post-creation
+- Add `copilot` as a reviewer: `gh pr edit <number> --add-reviewer copilot`
+- Do NOT add AI assistant as co-author. Code responsibility is on the committer's hands.
+- Return the PR URL when done.

.claude/skills/license/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: license
+description: Check and fix Apache 2.0 license headers and dependency licenses using skywalking-eyes. Use before submitting a PR.
+argument-hint: "[check|fix|deps]"
+---
+
+# License Checks
+
+Check and fix license compliance using [skywalking-eyes](https://github.com/apache/skywalking-eyes). Two CI jobs use this tool:
+
+1. **license-header** — verifies all source files have Apache 2.0 headers
+2. **dependency-license** — verifies the LICENSE file matches current dependencies
+
+## Steps
+
+### Header check (default, or `check` argument)
+
+```bash
+license-eye header check
+```
+
+- **All valid**: Output shows `valid: N, invalid: 0` — nothing to do.
+- **Invalid files found**: Fix with `license-eye header fix`, then re-check.
+
+### Header fix (`fix` argument)
+
+```bash
+license-eye header fix
+license-eye header check
+```
+
+### Dependency license check (`deps` argument)
+
+This regenerates the LICENSE file from dependency metadata and checks for drift:
+
+```bash
+license-eye dependency resolve --summary ./dist-material/release-docs/LICENSE.tpl || exit 1
+if [ ! -z "$(git diff -U0 ./dist-material/release-docs/LICENSE)" ]; then
+  echo "LICENSE file is not updated correctly"
+  git diff -U0 ./dist-material/release-docs/LICENSE
+fi
+```
+
+If the LICENSE file changed, review the diff and commit it. **Important**: CI runs on Linux — some dependencies have platform-specific variants. If you're on macOS/Windows, the LICENSE diff may be a platform artifact. Verify before committing.
+
+## Rules
+
+Configuration is in `.licenserc.yaml`:
+- Java, XML, YAML/YML files require Apache 2.0 headers
+- JSON and Markdown files are excluded (JSON doesn't support comments)
+- Generated files and certain vendor paths are excluded
+- SPI service files (`META-INF/services/`) require headers (use `#` comment style)
+
+## Installation
+
+```bash
+# Same version as CI (pinned commit)
+go install github.com/apache/skywalking-eyes/cmd/license-eye@5b7ee1731d036b5aac68f8bd3fc9e6f98ada082e
+
+# Or via Homebrew (macOS)
+brew install license-eye
+```