feat: sync multi-tenant WebUI and channel connection support from upstream

.dockerignore

@@ -0,0 +1,25 @@
+.git
+.github
+.idea
+.vscode
+.DS_Store
+*.log
+*.swp
+
+bin/
+data/
+dist/
+coverage.out
+coverage.html
+*.test
+*.exe
+vendor/
+docs/site/
+**/__pycache__/
+
+# Never send populated deployment credentials to the Docker build context.
+deploy/service.env
+deploy/*.env
+
+**/node_modules/
+trpcservice/web/dist/

.gitattributes

@@ -0,0 +1,8 @@
+# Shell scripts must always use LF, otherwise bash fails with
+# "set: pipefail: invalid option name" on CRLF checkouts (e.g. Windows).
+*.sh text eol=lf
+*.go text eol=lf
+*.sql text eol=lf
+
+# GitHub Actions workflows
+*.yml text eol=lf

.github/ISSUE_TEMPLATE/00-bug.md

@@ -0,0 +1,36 @@
+---
+name: Bug report
+about: Report a reproducible problem in trpc-agent-service
+title: "[Bug] "
+labels: "type/bug"
+assignees: ""
+---
+
+## Description
+
+<!-- Please describe the problem and its impact. Remove secrets, tokens, personal data, and customer content. -->
+
+## Reproduction
+
+<!-- Provide the smallest reproducible example, request, configuration, or sequence of steps. -->
+
+1.
+2.
+3.
+
+## Expected behavior
+
+## Actual behavior
+
+## Environment
+
+- Go version:
+- Service commit or version:
+- Deployment mode (local, container, Kubernetes, etc.):
+- Storage backend and version:
+- IM channel/integration:
+- OS and architecture:
+
+## Logs and additional context
+
+<!-- Include relevant logs, traces, or screenshots after removing sensitive data. -->

.github/ISSUE_TEMPLATE/01-feature.md

@@ -0,0 +1,30 @@
+---
+name: Feature request
+about: Suggest an improvement or new capability
+title: "[Feature] "
+labels: "type/feature"
+assignees: ""
+---
+
+## Problem
+
+<!-- What user or operational problem does this solve? Who is affected? -->
+
+## Desired behavior or contract
+
+<!-- Describe the user-facing behavior, API/configuration contract, and acceptance criteria. -->
+
+## Alternatives considered
+
+## Integration and compatibility impact
+
+- Tenant isolation and authorization:
+- IM channels and message behavior:
+- Storage schema, retention, or migration:
+- Tools, model providers, or external integrations:
+- Audit, metrics, and tracing:
+- Backward compatibility:
+
+## Additional context
+
+<!-- Do not include secrets or identifiable user/customer data. -->

.github/ISSUE_TEMPLATE/02-question.md

@@ -0,0 +1,23 @@
+---
+name: Question
+about: Ask for help using or operating trpc-agent-service
+title: "[Question] "
+labels: "type/question"
+assignees: ""
+---
+
+## Question
+
+<!-- State one concrete question and the outcome you are trying to achieve. -->
+
+## Context
+
+- Service commit or version:
+- Deployment mode:
+- Relevant configuration:
+- Minimal request or code sample:
+- Relevant logs or error message:
+
+## What have you tried?
+
+<!-- Redact credentials, tokens, personal data, and customer content. -->

.github/ISSUE_TEMPLATE/03-proposal.md

@@ -0,0 +1,33 @@
+---
+name: Design proposal
+about: Propose an architectural or cross-cutting change
+title: "[Proposal] "
+labels: "type/proposal"
+assignees: ""
+---
+
+## Background
+
+<!-- Explain the current behavior, constraints, and problem with evidence where possible. -->
+
+## Proposal
+
+<!-- Describe the design, interfaces, data flow, and rollout or migration plan. -->
+
+## Goals
+
+-
+
+## Non-goals
+
+-
+
+## Alternatives and trade-offs
+
+<!-- Include operational cost, reliability, performance, security, and maintenance implications. -->
+
+## Open questions
+
+## Additional context
+
+<!-- Remove secrets and identifiable user/customer data before posting. -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Documentation
+    url: https://github.com/XnLemon/trpc-agent-service/tree/main/docs
+    about: Read the project documentation before opening an issue.
+  - name: Upstream trpc-agent-go
+    url: https://github.com/trpc-group/trpc-agent-go
+    about: Check upstream framework behavior and examples.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,43 @@
+<!-- Suggested title: package: lowercase summary -->
+<!-- Multiple primary packages: {package/a, package/b}: lowercase summary -->
+
+<!-- Use "Fixes #123" when this PR completes an issue; otherwise use "Updates #123". -->
+
+## What changed
+
+<!-- Summarize the implementation and link the issue or design proposal. -->
+
+## Why
+
+<!-- Explain the problem and why this approach is appropriate. -->
+
+## Scope and compatibility
+
+- API or configuration changes:
+- Data/schema or migration changes:
+- Deployment and rollout considerations:
+- Backward compatibility and failure behavior:
+
+## Testing
+
+- [ ] `./scripts/format.sh --check`
+- [ ] `./scripts/lint.sh`
+- [ ] `./scripts/build.sh`
+- [ ] `go test ./...` or `./scripts/coverage.sh`
+- [ ] Unit tests added or updated
+- [ ] Integration or end-to-end tests run where relevant
+- [ ] Race tests run for concurrency-sensitive packages
+- [ ] Manual verification performed (describe below)
+- [ ] git diff --check passes
+
+Test details:
+
+## Security and tenant isolation
+
+- [ ] Authorization and tenant boundaries were reviewed
+- [ ] Logs and errors do not expose secrets or user/customer data
+- [ ] External integrations and tool permissions were reviewed
+
+## Notes for reviewers
+
+<!-- Call out risky areas, follow-up work, migrations, or decisions needing review. -->