docs: rules split into config.json (effective state) + config.upstream.json (upstream backup) since v0.7.0
docs: layered rules (upstream/user) since core v0.6.0 Document the two rule layers from snishaper-core v0.6.0: rules/config.json is the upstream layer replaced wholesale by rule updates; rules/config.user.json is the user layer holding local edits/additions/deletions that updates never touch. - Code-Structure (zh/en): file tree gains config.user.json; core dep bump v0.4.0 -> v0.6.0 - GUI-Configuration (zh/en): new section on layer badges and revert-to-upstream - FAQ (zh/en): new entry on update safety for custom rules
docs: update code structure for core v0.4.0 packages
docs: update code-structure wiki for core v0.3.1 branding
docs: update code-structure wiki for snishaper-core migration The engine packages (proxy, certmanager, cfpool, dohresolver, netiface, singtun, subscription, tlsfrag, gfwlist) are no longer local directories; they are consumed from github.com/SnishaperTeam/snishaper-core. Reflect the new layout, import paths and the per-instance netiface Selector API, and add the Go test/vet commands. zh and EN kept structurally identical.
docs: document mihomo-library node dialing and URL tests in code structure
docs: document fragment config API, Iconify icons and configurable TLS fragmentation Adds app_fragment.go to the layout, notes the latency probe APIs in
docs: initial wiki with Home, Usage Guide, CLI Reference and Code Structure (zh/en)