Fix/router

.devproxy.yaml

@@ -0,0 +1,9 @@
+dns:
+  port: 1053
+http:
+  port: 80
+
+routes:
+  - pattern: "debug"
+    target: "localhost:8082"
+    path: "/debug"

.github/agents/lava-reviewer.agent.md

@@ -0,0 +1,60 @@
+---
+name: Lava Reviewer
+description: "Use when: reviewing Lava pull requests, auditing Go backend changes, checking architectural boundaries, and producing actionable fix recommendations with verification steps."
+tools: [read, search, execute, todo]
+argument-hint: "Provide PR context, changed files, or review focus (e.g., concurrency, API compatibility, proto workflow)."
+user-invocable: true
+disable-model-invocation: false
+---
+
+You are a specialist code reviewer for the Lava repository.
+
+Your job is to assess change quality, identify concrete risks, and return concise, actionable fixes with a verification plan aligned to this repository.
+
+## Constraints
+
+- Focus on review and recommendations first; do not perform broad refactors unless explicitly requested.
+- Keep comments evidence-based and tie findings to specific files/symbols/behaviors.
+- Preserve public API and architectural boundaries unless change intent requires otherwise.
+- Do not suggest editing generated protobuf files (`*.pb.go`) directly.
+- Prefer minimal, high-signal findings over exhaustive low-value commentary.
+
+## Repository-Specific Guardrails
+
+- Treat `Taskfile.yml` as local workflow source of truth.
+- For standard verification, prioritize:
+  1. `task test`
+  2. `task lint`
+- If `.proto` or `protobuf.yaml` is touched, require:
+  1. `task proto:fmt`
+  2. `task proto:lint`
+  3. `task proto:gen`
+  4. then `task test` and `task lint`
+- Check module placement decisions against Lava boundaries:
+  - `lava/` abstractions
+  - `core/` runtime capabilities
+  - `servers/` serving behavior
+  - `clients/` outbound clients
+  - `pkg/` reusable public components
+  - `internal/` internal-only implementation
+
+## Review Approach
+
+1. Inspect changed areas and summarize intent in 3-6 bullets.
+2. Evaluate correctness risks (concurrency, lifecycle, error handling, resource leaks, API behavior changes).
+3. Evaluate design fit (module boundary placement, reuse of existing patterns, compatibility impact).
+4. Evaluate operability (logs, metrics/tracing implications, failure modes).
+5. Propose minimal fixes with rationale and impact.
+6. Return a prioritized verification checklist and expected pass criteria.
+
+## Output Format
+
+Use this structure:
+
+- **Scope understood**: what was reviewed.
+- **Top findings**: prioritized list (`critical` / `high` / `medium` / `low`).
+- **Suggested fixes**: minimal patch strategy per finding.
+- **Validation plan**: exact commands and what success looks like.
+- **Residual risks**: anything not fully verifiable from current context.
+
+When there are no material issues, explicitly state **"No blocking issues found"** and still provide a short validation summary.

.github/copilot-instructions.md

@@ -0,0 +1,69 @@
+# Project Guidelines for Lava
+
+## Scope
+
+These instructions are project-wide defaults for this repository. Keep changes focused, minimal, and aligned with existing patterns.
+
+## Architecture
+
+- `lava/`: core public interfaces and contracts (`Middleware`, routers, request/response abstractions).
+- `core/`: runtime capabilities (supervisor, scheduler, tunnel, logging/metrics/tracing, debug, DI builder).
+- `servers/`: service hosts (`https` on Fiber, `grpcs` with gateway integration).
+- `clients/`: outbound client implementations (`grpcc`, `resty`).
+- `pkg/`: reusable public utilities/components (including gateway and helpers).
+- `internal/`: repository-internal implementation details/examples; avoid exposing as public API.
+
+Place new code by responsibility:
+- Cross-protocol abstractions -> `lava/`
+- Runtime framework capability -> `core/<module>/`
+- HTTP/gRPC serving behavior -> `servers/`
+- Reusable public helper/component -> `pkg/`
+- Internal-only implementation -> `internal/`
+
+## Build and Test
+
+Run commands from repository root.
+
+Primary local workflow (source of truth: `Taskfile.yml`):
+- `task test` (Go tests: short + race + cover)
+- `task lint` (golangci-lint)
+
+When `.proto` files or `protobuf.yaml` change, run:
+- `task proto:fmt`
+- `task proto:lint`
+- `task proto:gen`
+- then `task test` and `task lint`
+
+CI reference is `.github/workflows/lint-test.yml` (lint + gotestsum-based tests).
+
+## Conventions
+
+- Follow standard Go formatting and idioms (`gofmt`, package naming, error-last returns).
+- Prefer wrapping errors with context (project commonly uses `github.com/pkg/errors`).
+- Keep public APIs and behavior stable unless the task explicitly requires breaking changes.
+- Do not edit generated protobuf files (`*.pb.go`) manually; regenerate via proto tasks.
+- Prefer updating existing module patterns instead of introducing new architectural styles.
+
+## Pitfalls to Avoid
+
+- `Taskfile.yml` is authoritative for local commands; docs are guidance.
+- Lint settings may apply automatic fixes (`.golangci.yaml` has `issues.fix: true`), so re-check diffs after lint.
+- Go toolchain target is defined in `go.mod` (`go 1.25.0`).
+- For protobuf generation, keep `protobuf.yaml` base module aligned with Go module path (`github.com/pubgo/lava/v2/pkg`).
+
+## Key References
+
+- `README.md`
+- `docs/architecture-v2.md`
+- `docs/design-v2.md`
+- `docs/development.md`
+- `Taskfile.yml`
+- `.github/workflows/lint-test.yml`
+
+## Representative Examples
+
+- Service lifecycle and management: `core/supervisor/`
+- DI registration patterns: `core/lavabuilder/`
+- HTTP server composition: `servers/https/server.go`
+- gRPC + gateway composition: `servers/grpcs/server.go`
+- Gateway behavior and routing: `pkg/gateway/`

.github/instructions/backend-go.instructions.md

@@ -0,0 +1,38 @@
+---
+name: backend-go
+description: "Use when: editing Go backend code in Lava (core/servers/clients/pkg/lava/cmds/internal), including refactors, bug fixes, and tests."
+applyTo: "{core,servers,clients,pkg,lava,cmds,internal}/**/*.go"
+---
+
+# Lava Backend Go Instructions
+
+- Keep changes minimal and consistent with existing patterns in the target module.
+- Place code by responsibility:
+  - Cross-protocol contracts -> `lava/`
+  - Runtime framework capabilities -> `core/<module>/`
+  - Service hosting behavior -> `servers/`
+  - Outbound client behavior -> `clients/`
+  - Reusable public helpers/components -> `pkg/`
+  - Internal-only implementation -> `internal/`
+- Preserve public APIs unless the task explicitly requires a breaking change.
+- Prefer contextual error wrapping; this repository commonly uses `github.com/pkg/errors`.
+- Never hand-edit generated protobuf files (`*.pb.go`); regenerate via proto tasks.
+- Follow Go idioms (`gofmt`, package naming, error-last returns).
+- Reuse existing module patterns before introducing new architectural styles.
+
+## Validation
+
+- Run from repository root.
+- Standard verification flow:
+  - `task test`
+  - `task lint`
+- If `.proto` or `protobuf.yaml` changes are involved, run first:
+  - `task proto:fmt`
+  - `task proto:lint`
+  - `task proto:gen`
+
+## Pitfalls
+
+- Treat `Taskfile.yml` as the local source of truth.
+- Lint may auto-fix files (`.golangci.yaml` sets `issues.fix: true`); re-check diffs after lint.
+- Keep Go toolchain aligned with `go.mod` (`go 1.25.0`).

.github/workflows/lint-test.yml

@@ -21,7 +21,6 @@ jobs:
       - name: golangci-lint
         uses: golangci/golangci-lint-action@v8
         with:
-          skip-go-installation: true
           args: --timeout 3m --verbose
 
   test:

.gitignore

@@ -28,3 +28,5 @@ bin
 /example/bin
 .proto
 proto-vendor
+.local
+/internal/examples/grpcweb/frontend/node_modules

.lava.yaml.example

@@ -0,0 +1,84 @@
+# lava 配置文件示例
+# 配置文件可以放在以下位置（按优先级从高到低）：
+# 1. .lava/lava.yaml
+# 2. .lava.yaml
+# 3. lava.yaml
+
+# watch 命令配置
+watch:
+  # watcher 列表，可以配置多个 watcher
+  watchers:
+    # watcher 1：监控 proto 文件
+    - name: "proto"
+      directory: "./proto"
+      patterns:
+        - "*.proto"
+      commands:
+        - "protobuild gen"
+      ignore:
+        - ".git"
+        - "vendor"
+      ignore_patterns:
+        - "*.tmp"
+        - "*~"
+      run_on_startup: false
+      timeout: 30
+
+    # watcher 2：监控 go 文件
+    - name: "go"
+      directory: "."
+      patterns:
+        - "*.go"
+      commands:
+        - "go build ./..."
+      ignore:
+        - ".git"
+        - "node_modules"
+        - "vendor"
+        - "dist"
+        - "build"
+      ignore_patterns:
+        - "*.tmp"
+        - "*~"
+        - ".DS_Store"
+      run_on_startup: false
+      timeout: 30
+
+    # watcher 3：监控配置文件
+    - name: "config"
+      directory: "./internal/configs"
+      patterns:
+        - "*.yaml"
+      commands:
+        - "echo 'Config changed, reloading...'"
+      ignore:
+        - ".git"
+      run_on_startup: false
+      timeout: 10
+
+# curl 命令配置
+curl:
+  # 网关地址
+  addr: "http://127.0.0.1:8080"
+
+  # 网关前缀
+  prefix: "/api"
+
+  # 请求超时时间
+  timeout: "15s"
+
+  # 是否跳过 TLS 校验
+  insecure: false
+
+  # 是否对 JSON 响应进行格式化
+  pretty: true
+
+  # gateway 路由信息的 expvar 名称
+  vars_name: "grpc-server-info"
+
+  # 默认的请求头
+  headers:
+    - "Content-Type: application/json"
+
+  # 默认的查询参数
+  queries: {}