main
14
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 kazeyukiro
|
8af3d34589 | docs: fix website URLs (/guide not /docs/guide) | ||
|
kazeyukiro
|
7bdf35ba5b |
docs: point technical guides at 3m-ui.top; keep docs/readme/
Full documentation lives on the VitePress site (zh + en). Repository docs/*.md are short stubs with links. Multilingual README files remain under docs/readme/. Offline AI install prompts (.txt) are retained. |
||
|
kazeyukiro
|
96d4a8a432 |
feat(routing): Mihomo rule-providers with hot update
Store rule-providers on server-routing, emit official rule-providers
block into serving config, and expose PUT hot-update via core
/providers/rules/{name}. Panel UI on Routing → Server egress.
|
||
|
kazeyukiro
|
fec9733baa |
docs: remove third-party panel name references from copy
Drop and external m-ui product names from docs, UI strings, and code comments. Keep functional descriptions of server egress and WARP. docs: remove third-party panel name references from copy Drop and external m-ui product names from docs, UI strings, and code comments. Keep functional descriptions of server egress and WARP. docs: remove third-party panel name references from copy Drop and external m-ui product names from docs, UI strings, and code comments. Keep functional descriptions of server egress and WARP. docs: remove third-party panel name references from copy Drop and external m-ui product names from docs, UI strings, and code comments. Keep functional descriptions of server egress and WARP. docs: remove third-party panel name references from copy Drop and external m-ui product names from docs, UI strings, and code comments. Keep functional descriptions of server egress and WARP. docs: remove third-party panel name references from copy Drop and external m-ui product names from docs, UI strings, and code comments. Keep functional descriptions of server egress and WARP. docs: remove third-party panel name references from copy Drop and external m-ui product names from docs, UI strings, and code comments. Keep functional descriptions of server egress and WARP. docs: remove third-party panel name references from copy Drop and external m-ui product names from docs, UI strings, and code comments. Keep functional descriptions of server egress and WARP. docs: remove third-party panel name references from copy Drop and external m-ui product names from docs, UI strings, and code comments. Keep functional descriptions of server egress and WARP. docs: remove third-party panel name references from copy Drop and external m-ui product names from docs, UI strings, and code comments. Keep functional descriptions of server egress and WARP. docs: remove third-party panel name references from copy Drop and external m-ui product names from docs, UI strings, and code comments. Keep functional descriptions of server egress and WARP. docs: remove third-party panel name references from copy Drop and external m-ui product names from docs, UI strings, and code comments. Keep functional descriptions of server egress and WARP. |
||
|
kazeyukiro
|
0beaf396d1 |
docs(api): align OpenAPI with server-routing and WARP account
Replace obsolete inject-warp; document GET/PUT server-routing, GET/POST/DELETE system/warp, and templates/warp register nosave. docs(api): align OpenAPI with server-routing and WARP account Replace obsolete inject-warp; document GET/PUT server-routing, GET/POST/DELETE system/warp, and templates/warp register nosave. docs(api): align OpenAPI with server-routing and WARP account Replace obsolete inject-warp; document GET/PUT server-routing, GET/POST/DELETE system/warp, and templates/warp register nosave. docs(api): align OpenAPI with server-routing and WARP account Replace obsolete inject-warp; document GET/PUT server-routing, GET/POST/DELETE system/warp, and templates/warp register nosave. docs(api): align OpenAPI with server-routing and WARP account Replace obsolete inject-warp; document GET/PUT server-routing, GET/POST/DELETE system/warp, and templates/warp register nosave. docs(api): align OpenAPI with server-routing and WARP account Replace obsolete inject-warp; document GET/PUT server-routing, GET/POST/DELETE system/warp, and templates/warp register nosave. docs(api): align OpenAPI with server-routing and WARP account Replace obsolete inject-warp; document GET/PUT server-routing, GET/POST/DELETE system/warp, and templates/warp register nosave. docs(api): align OpenAPI with server-routing and WARP account Replace obsolete inject-warp; document GET/PUT server-routing, GET/POST/DELETE system/warp, and templates/warp register nosave. docs(api): align OpenAPI with server-routing and WARP account Replace obsolete inject-warp; document GET/PUT server-routing, GET/POST/DELETE system/warp, and templates/warp register nosave. docs(api): align OpenAPI with server-routing and WARP account Replace obsolete inject-warp; document GET/PUT server-routing, GET/POST/DELETE system/warp, and templates/warp register nosave. docs(api): align OpenAPI with server-routing and WARP account Replace obsolete inject-warp; document GET/PUT server-routing, GET/POST/DELETE system/warp, and templates/warp register nosave. docs(api): align OpenAPI with server-routing and WARP account Replace obsolete inject-warp; document GET/PUT server-routing, GET/POST/DELETE system/warp, and templates/warp register nosave. |
||
|
kazeyukiro
|
ca2d4a3192 |
docs: sync routing (server egress) and WARP limits
Document Client vs Server tabs, server-routing API, and that WARP register is manual (no auto AI/streaming unlock pipeline). docs: sync routing (server egress) and WARP limits Document Client vs Server tabs, server-routing API, and that WARP register is manual (no auto AI/streaming unlock pipeline). docs: sync routing (server egress) and WARP limits Document Client vs Server tabs, server-routing API, and that WARP register is manual (no auto AI/streaming unlock pipeline). docs: sync routing (server egress) and WARP limits Document Client vs Server tabs, server-routing API, and that WARP register is manual (no auto AI/streaming unlock pipeline). docs: sync routing (server egress) and WARP limits Document Client vs Server tabs, server-routing API, and that WARP register is manual (no auto AI/streaming unlock pipeline). docs: sync routing (server egress) and WARP limits Document Client vs Server tabs, server-routing API, and that WARP register is manual (no auto AI/streaming unlock pipeline). docs: sync routing (server egress) and WARP limits Document Client vs Server tabs, server-routing API, and that WARP register is manual (no auto AI/streaming unlock pipeline). docs: sync routing (server egress) and WARP limits Document Client vs Server tabs, server-routing API, and that WARP register is manual (no auto AI/streaming unlock pipeline). docs: sync routing (server egress) and WARP limits Document Client vs Server tabs, server-routing API, and that WARP register is manual (no auto AI/streaming unlock pipeline). docs: sync routing (server egress) and WARP limits Document Client vs Server tabs, server-routing API, and that WARP register is manual (no auto AI/streaming unlock pipeline). docs: sync routing (server egress) and WARP limits Document Client vs Server tabs, server-routing API, and that WARP register is manual (no auto AI/streaming unlock pipeline). docs: sync routing (server egress) and WARP limits Document Client vs Server tabs, server-routing API, and that WARP register is manual (no auto AI/streaming unlock pipeline). |
||
|
kazeyukiro
|
feb8d6889a |
docs: document Cloudflare WARP (v1.3.6) across READMEs and routing
Add docs/warp.md, link from all language READMEs / feature tables, and clarify routing is client-only (WARP is Settings YAML, not server exit). docs: document Cloudflare WARP (v1.3.6) across READMEs and routing Add docs/warp.md, link from all language READMEs / feature tables, and clarify routing is client-only (WARP is Settings YAML, not server exit). docs: document Cloudflare WARP (v1.3.6) across READMEs and routing Add docs/warp.md, link from all language READMEs / feature tables, and clarify routing is client-only (WARP is Settings YAML, not server exit). docs: document Cloudflare WARP (v1.3.6) across READMEs and routing Add docs/warp.md, link from all language READMEs / feature tables, and clarify routing is client-only (WARP is Settings YAML, not server exit). docs: document Cloudflare WARP (v1.3.6) across READMEs and routing Add docs/warp.md, link from all language READMEs / feature tables, and clarify routing is client-only (WARP is Settings YAML, not server exit). docs: document Cloudflare WARP (v1.3.6) across READMEs and routing Add docs/warp.md, link from all language READMEs / feature tables, and clarify routing is client-only (WARP is Settings YAML, not server exit). docs: document Cloudflare WARP (v1.3.6) across READMEs and routing Add docs/warp.md, link from all language READMEs / feature tables, and clarify routing is client-only (WARP is Settings YAML, not server exit). docs: document Cloudflare WARP (v1.3.6) across READMEs and routing Add docs/warp.md, link from all language READMEs / feature tables, and clarify routing is client-only (WARP is Settings YAML, not server exit). docs: document Cloudflare WARP (v1.3.6) across READMEs and routing Add docs/warp.md, link from all language READMEs / feature tables, and clarify routing is client-only (WARP is Settings YAML, not server exit). docs: document Cloudflare WARP (v1.3.6) across READMEs and routing Add docs/warp.md, link from all language READMEs / feature tables, and clarify routing is client-only (WARP is Settings YAML, not server exit). docs: document Cloudflare WARP (v1.3.6) across READMEs and routing Add docs/warp.md, link from all language READMEs / feature tables, and clarify routing is client-only (WARP is Settings YAML, not server exit). docs: document Cloudflare WARP (v1.3.6) across READMEs and routing Add docs/warp.md, link from all language READMEs / feature tables, and clarify routing is client-only (WARP is Settings YAML, not server exit). |
||
|
kazeyukiro
|
52bb97c083 |
chore: remove Cloudflare WARP feature (panel, API, docs)
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP path, and documentation. Client routing and inbound panel unchanged; server remains MATCH,DIRECT. chore: remove Cloudflare WARP feature (panel, API, docs) Drop register/inject endpoints, Settings/Routing UI, server-exit WARP path, and documentation. Client routing and inbound panel unchanged; server remains MATCH,DIRECT. chore: remove Cloudflare WARP feature (panel, API, docs) Drop register/inject endpoints, Settings/Routing UI, server-exit WARP path, and documentation. Client routing and inbound panel unchanged; server remains MATCH,DIRECT. chore: remove Cloudflare WARP feature (panel, API, docs) Drop register/inject endpoints, Settings/Routing UI, server-exit WARP path, and documentation. Client routing and inbound panel unchanged; server remains MATCH,DIRECT. chore: remove Cloudflare WARP feature (panel, API, docs) Drop register/inject endpoints, Settings/Routing UI, server-exit WARP path, and documentation. Client routing and inbound panel unchanged; server remains MATCH,DIRECT. chore: remove Cloudflare WARP feature (panel, API, docs) Drop register/inject endpoints, Settings/Routing UI, server-exit WARP path, and documentation. Client routing and inbound panel unchanged; server remains MATCH,DIRECT. chore: remove Cloudflare WARP feature (panel, API, docs) Drop register/inject endpoints, Settings/Routing UI, server-exit WARP path, and documentation. Client routing and inbound panel unchanged; server remains MATCH,DIRECT. chore: remove Cloudflare WARP feature (panel, API, docs) Drop register/inject endpoints, Settings/Routing UI, server-exit WARP path, and documentation. Client routing and inbound panel unchanged; server remains MATCH,DIRECT. chore: remove Cloudflare WARP feature (panel, API, docs) Drop register/inject endpoints, Settings/Routing UI, server-exit WARP path, and documentation. Client routing and inbound panel unchanged; server remains MATCH,DIRECT. chore: remove Cloudflare WARP feature (panel, API, docs) Drop register/inject endpoints, Settings/Routing UI, server-exit WARP path, and documentation. Client routing and inbound panel unchanged; server remains MATCH,DIRECT. chore: remove Cloudflare WARP feature (panel, API, docs) Drop register/inject endpoints, Settings/Routing UI, server-exit WARP path, and documentation. Client routing and inbound panel unchanged; server remains MATCH,DIRECT. chore: remove Cloudflare WARP feature (panel, API, docs) Drop register/inject endpoints, Settings/Routing UI, server-exit WARP path, and documentation. Client routing and inbound panel unchanged; server remains MATCH,DIRECT. |
||
|
kazeyukiro
|
a0ceb3a815 |
feat: server WARP exit for listener traffic (user → node → WARP IP)
When visual-config contains wireguard/WARP outbounds, GenerateFinalConfig merges them into the serving Mihomo process and sets MATCH to that exit (optional CN DIRECT). Client community rules remain client-subscription only. feat: server WARP exit for listener traffic (user → node → WARP IP) When visual-config contains wireguard/WARP outbounds, GenerateFinalConfig merges them into the serving Mihomo process and sets MATCH to that exit (optional CN DIRECT). Client community rules remain client-subscription only. feat: server WARP exit for listener traffic (user → node → WARP IP) When visual-config contains wireguard/WARP outbounds, GenerateFinalConfig merges them into the serving Mihomo process and sets MATCH to that exit (optional CN DIRECT). Client community rules remain client-subscription only. feat: server WARP exit for listener traffic (user → node → WARP IP) When visual-config contains wireguard/WARP outbounds, GenerateFinalConfig merges them into the serving Mihomo process and sets MATCH to that exit (optional CN DIRECT). Client community rules remain client-subscription only. feat: server WARP exit for listener traffic (user → node → WARP IP) When visual-config contains wireguard/WARP outbounds, GenerateFinalConfig merges them into the serving Mihomo process and sets MATCH to that exit (optional CN DIRECT). Client community rules remain client-subscription only. feat: server WARP exit for listener traffic (user → node → WARP IP) When visual-config contains wireguard/WARP outbounds, GenerateFinalConfig merges them into the serving Mihomo process and sets MATCH to that exit (optional CN DIRECT). Client community rules remain client-subscription only. feat: server WARP exit for listener traffic (user → node → WARP IP) When visual-config contains wireguard/WARP outbounds, GenerateFinalConfig merges them into the serving Mihomo process and sets MATCH to that exit (optional CN DIRECT). Client community rules remain client-subscription only. feat: server WARP exit for listener traffic (user → node → WARP IP) When visual-config contains wireguard/WARP outbounds, GenerateFinalConfig merges them into the serving Mihomo process and sets MATCH to that exit (optional CN DIRECT). Client community rules remain client-subscription only. feat: server WARP exit for listener traffic (user → node → WARP IP) When visual-config contains wireguard/WARP outbounds, GenerateFinalConfig merges them into the serving Mihomo process and sets MATCH to that exit (optional CN DIRECT). Client community rules remain client-subscription only. feat: server WARP exit for listener traffic (user → node → WARP IP) When visual-config contains wireguard/WARP outbounds, GenerateFinalConfig merges them into the serving Mihomo process and sets MATCH to that exit (optional CN DIRECT). Client community rules remain client-subscription only. feat: server WARP exit for listener traffic (user → node → WARP IP) When visual-config contains wireguard/WARP outbounds, GenerateFinalConfig merges them into the serving Mihomo process and sets MATCH to that exit (optional CN DIRECT). Client community rules remain client-subscription only. feat: server WARP exit for listener traffic (user → node → WARP IP) When visual-config contains wireguard/WARP outbounds, GenerateFinalConfig merges them into the serving Mihomo process and sets MATCH to that exit (optional CN DIRECT). Client community rules remain client-subscription only. |
||
|
kazeyukiro
|
ad35987e21 |
refactor: drop server-side split; visual routing is client-only
GenerateFinalConfig strips rules/proxy-groups/proxies from visual-config and forces MATCH,DIRECT on the serving Mihomo process. Panel Routing page remains the editor for client subscription YAML only. refactor: drop server-side split; visual routing is client-only GenerateFinalConfig strips rules/proxy-groups/proxies from visual-config and forces MATCH,DIRECT on the serving Mihomo process. Panel Routing page remains the editor for client subscription YAML only. refactor: drop server-side split; visual routing is client-only GenerateFinalConfig strips rules/proxy-groups/proxies from visual-config and forces MATCH,DIRECT on the serving Mihomo process. Panel Routing page remains the editor for client subscription YAML only. refactor: drop server-side split; visual routing is client-only GenerateFinalConfig strips rules/proxy-groups/proxies from visual-config and forces MATCH,DIRECT on the serving Mihomo process. Panel Routing page remains the editor for client subscription YAML only. refactor: drop server-side split; visual routing is client-only GenerateFinalConfig strips rules/proxy-groups/proxies from visual-config and forces MATCH,DIRECT on the serving Mihomo process. Panel Routing page remains the editor for client subscription YAML only. refactor: drop server-side split; visual routing is client-only GenerateFinalConfig strips rules/proxy-groups/proxies from visual-config and forces MATCH,DIRECT on the serving Mihomo process. Panel Routing page remains the editor for client subscription YAML only. refactor: drop server-side split; visual routing is client-only GenerateFinalConfig strips rules/proxy-groups/proxies from visual-config and forces MATCH,DIRECT on the serving Mihomo process. Panel Routing page remains the editor for client subscription YAML only. refactor: drop server-side split; visual routing is client-only GenerateFinalConfig strips rules/proxy-groups/proxies from visual-config and forces MATCH,DIRECT on the serving Mihomo process. Panel Routing page remains the editor for client subscription YAML only. refactor: drop server-side split; visual routing is client-only GenerateFinalConfig strips rules/proxy-groups/proxies from visual-config and forces MATCH,DIRECT on the serving Mihomo process. Panel Routing page remains the editor for client subscription YAML only. refactor: drop server-side split; visual routing is client-only GenerateFinalConfig strips rules/proxy-groups/proxies from visual-config and forces MATCH,DIRECT on the serving Mihomo process. Panel Routing page remains the editor for client subscription YAML only. refactor: drop server-side split; visual routing is client-only GenerateFinalConfig strips rules/proxy-groups/proxies from visual-config and forces MATCH,DIRECT on the serving Mihomo process. Panel Routing page remains the editor for client subscription YAML only. refactor: drop server-side split; visual routing is client-only GenerateFinalConfig strips rules/proxy-groups/proxies from visual-config and forces MATCH,DIRECT on the serving Mihomo process. Panel Routing page remains the editor for client subscription YAML only. |
||
|
kazeyukiro
|
3b65c03d6c |
feat(sub): export panel routing groups/rules into client Mihomo YAML
Client subscriptions now use visual-config proxy-groups and rules. Leaf groups that only listed DIRECT get subscription node names injected. Default remains PROXY+AUTO when routing was never customized. feat(sub): export panel routing groups/rules into client Mihomo YAML Client subscriptions now use visual-config proxy-groups and rules. Leaf groups that only listed DIRECT get subscription node names injected. Default remains PROXY+AUTO when routing was never customized. feat(sub): export panel routing groups/rules into client Mihomo YAML Client subscriptions now use visual-config proxy-groups and rules. Leaf groups that only listed DIRECT get subscription node names injected. Default remains PROXY+AUTO when routing was never customized. feat(sub): export panel routing groups/rules into client Mihomo YAML Client subscriptions now use visual-config proxy-groups and rules. Leaf groups that only listed DIRECT get subscription node names injected. Default remains PROXY+AUTO when routing was never customized. feat(sub): export panel routing groups/rules into client Mihomo YAML Client subscriptions now use visual-config proxy-groups and rules. Leaf groups that only listed DIRECT get subscription node names injected. Default remains PROXY+AUTO when routing was never customized. feat(sub): export panel routing groups/rules into client Mihomo YAML Client subscriptions now use visual-config proxy-groups and rules. Leaf groups that only listed DIRECT get subscription node names injected. Default remains PROXY+AUTO when routing was never customized. feat(sub): export panel routing groups/rules into client Mihomo YAML Client subscriptions now use visual-config proxy-groups and rules. Leaf groups that only listed DIRECT get subscription node names injected. Default remains PROXY+AUTO when routing was never customized. feat(sub): export panel routing groups/rules into client Mihomo YAML Client subscriptions now use visual-config proxy-groups and rules. Leaf groups that only listed DIRECT get subscription node names injected. Default remains PROXY+AUTO when routing was never customized. feat(sub): export panel routing groups/rules into client Mihomo YAML Client subscriptions now use visual-config proxy-groups and rules. Leaf groups that only listed DIRECT get subscription node names injected. Default remains PROXY+AUTO when routing was never customized. feat(sub): export panel routing groups/rules into client Mihomo YAML Client subscriptions now use visual-config proxy-groups and rules. Leaf groups that only listed DIRECT get subscription node names injected. Default remains PROXY+AUTO when routing was never customized. feat(sub): export panel routing groups/rules into client Mihomo YAML Client subscriptions now use visual-config proxy-groups and rules. Leaf groups that only listed DIRECT get subscription node names injected. Default remains PROXY+AUTO when routing was never customized. feat(sub): export panel routing groups/rules into client Mihomo YAML Client subscriptions now use visual-config proxy-groups and rules. Leaf groups that only listed DIRECT get subscription node names injected. Default remains PROXY+AUTO when routing was never customized. |
||
|
kazeyukiro
|
f11b686a5e |
fix(routing): community templates restore proxy-groups
YiXuan/echs/MyClash presets now write matching select groups (地区/代理/AI/TG 等) plus rules, not rules-only with a single PROXY. fix(routing): community templates restore proxy-groups YiXuan/echs/MyClash presets now write matching select groups (地区/代理/AI/TG 等) plus rules, not rules-only with a single PROXY. fix(routing): community templates restore proxy-groups YiXuan/echs/MyClash presets now write matching select groups (地区/代理/AI/TG 等) plus rules, not rules-only with a single PROXY. fix(routing): community templates restore proxy-groups YiXuan/echs/MyClash presets now write matching select groups (地区/代理/AI/TG 等) plus rules, not rules-only with a single PROXY. fix(routing): community templates restore proxy-groups YiXuan/echs/MyClash presets now write matching select groups (地区/代理/AI/TG 等) plus rules, not rules-only with a single PROXY. fix(routing): community templates restore proxy-groups YiXuan/echs/MyClash presets now write matching select groups (地区/代理/AI/TG 等) plus rules, not rules-only with a single PROXY. fix(routing): community templates restore proxy-groups YiXuan/echs/MyClash presets now write matching select groups (地区/代理/AI/TG 等) plus rules, not rules-only with a single PROXY. fix(routing): community templates restore proxy-groups YiXuan/echs/MyClash presets now write matching select groups (地区/代理/AI/TG 等) plus rules, not rules-only with a single PROXY. fix(routing): community templates restore proxy-groups YiXuan/echs/MyClash presets now write matching select groups (地区/代理/AI/TG 等) plus rules, not rules-only with a single PROXY. fix(routing): community templates restore proxy-groups YiXuan/echs/MyClash presets now write matching select groups (地区/代理/AI/TG 等) plus rules, not rules-only with a single PROXY. fix(routing): community templates restore proxy-groups YiXuan/echs/MyClash presets now write matching select groups (地区/代理/AI/TG 等) plus rules, not rules-only with a single PROXY. fix(routing): community templates restore proxy-groups YiXuan/echs/MyClash presets now write matching select groups (地区/代理/AI/TG 等) plus rules, not rules-only with a single PROXY. |
||
|
kazeyukiro
|
1a7cff051c |
feat(routing): community rule templates (MyClash, echs-top, YiXuanZX)
- Templates adapted for GEOSITE/GEOIP + PROXY group (server visual-config) - Auto-create PROXY select group when applying community presets - README acknowledgements; docs/routing.md notes feat(routing): community rule templates (MyClash, echs-top, YiXuanZX) - Templates adapted for GEOSITE/GEOIP + PROXY group (server visual-config) - Auto-create PROXY select group when applying community presets - README acknowledgements; docs/routing.md notes feat(routing): community rule templates (MyClash, echs-top, YiXuanZX) - Templates adapted for GEOSITE/GEOIP + PROXY group (server visual-config) - Auto-create PROXY select group when applying community presets - README acknowledgements; docs/routing.md notes feat(routing): community rule templates (MyClash, echs-top, YiXuanZX) - Templates adapted for GEOSITE/GEOIP + PROXY group (server visual-config) - Auto-create PROXY select group when applying community presets - README acknowledgements; docs/routing.md notes feat(routing): community rule templates (MyClash, echs-top, YiXuanZX) - Templates adapted for GEOSITE/GEOIP + PROXY group (server visual-config) - Auto-create PROXY select group when applying community presets - README acknowledgements; docs/routing.md notes feat(routing): community rule templates (MyClash, echs-top, YiXuanZX) - Templates adapted for GEOSITE/GEOIP + PROXY group (server visual-config) - Auto-create PROXY select group when applying community presets - README acknowledgements; docs/routing.md notes feat(routing): community rule templates (MyClash, echs-top, YiXuanZX) - Templates adapted for GEOSITE/GEOIP + PROXY group (server visual-config) - Auto-create PROXY select group when applying community presets - README acknowledgements; docs/routing.md notes feat(routing): community rule templates (MyClash, echs-top, YiXuanZX) - Templates adapted for GEOSITE/GEOIP + PROXY group (server visual-config) - Auto-create PROXY select group when applying community presets - README acknowledgements; docs/routing.md notes feat(routing): community rule templates (MyClash, echs-top, YiXuanZX) - Templates adapted for GEOSITE/GEOIP + PROXY group (server visual-config) - Auto-create PROXY select group when applying community presets - README acknowledgements; docs/routing.md notes feat(routing): community rule templates (MyClash, echs-top, YiXuanZX) - Templates adapted for GEOSITE/GEOIP + PROXY group (server visual-config) - Auto-create PROXY select group when applying community presets - README acknowledgements; docs/routing.md notes feat(routing): community rule templates (MyClash, echs-top, YiXuanZX) - Templates adapted for GEOSITE/GEOIP + PROXY group (server visual-config) - Auto-create PROXY select group when applying community presets - README acknowledgements; docs/routing.md notes feat(routing): community rule templates (MyClash, echs-top, YiXuanZX) - Templates adapted for GEOSITE/GEOIP + PROXY group (server visual-config) - Auto-create PROXY select group when applying community presets - README acknowledgements; docs/routing.md notes |
||
|
kazeyukiro
|
c6ac347866 |
docs: align routing (structured rules, WARP inject) and API notes
Add docs/routing.md; README feature links; OpenAPI paths for rules/groups/inject-warp. docs: align routing (structured rules, WARP inject) and API notes Add docs/routing.md; README feature links; OpenAPI paths for rules/groups/inject-warp. docs: align routing (structured rules, WARP inject) and API notes Add docs/routing.md; README feature links; OpenAPI paths for rules/groups/inject-warp. docs: align routing (structured rules, WARP inject) and API notes Add docs/routing.md; README feature links; OpenAPI paths for rules/groups/inject-warp. docs: align routing (structured rules, WARP inject) and API notes Add docs/routing.md; README feature links; OpenAPI paths for rules/groups/inject-warp. docs: align routing (structured rules, WARP inject) and API notes Add docs/routing.md; README feature links; OpenAPI paths for rules/groups/inject-warp. docs: align routing (structured rules, WARP inject) and API notes Add docs/routing.md; README feature links; OpenAPI paths for rules/groups/inject-warp. docs: align routing (structured rules, WARP inject) and API notes Add docs/routing.md; README feature links; OpenAPI paths for rules/groups/inject-warp. docs: align routing (structured rules, WARP inject) and API notes Add docs/routing.md; README feature links; OpenAPI paths for rules/groups/inject-warp. docs: align routing (structured rules, WARP inject) and API notes Add docs/routing.md; README feature links; OpenAPI paths for rules/groups/inject-warp. docs: align routing (structured rules, WARP inject) and API notes Add docs/routing.md; README feature links; OpenAPI paths for rules/groups/inject-warp. docs: align routing (structured rules, WARP inject) and API notes Add docs/routing.md; README feature links; OpenAPI paths for rules/groups/inject-warp. |