From f7e39a47c66d37be4d83c3ba5563f0a4c6c791c6 Mon Sep 17 00:00:00 2001 From: jxxghp Date: Sat, 15 Aug 2026 23:05:01 +0800 Subject: [PATCH] =?UTF-8?q?docs(agents):=20=E7=A7=BB=E9=99=A4=E5=B7=B2?= =?UTF-8?q?=E5=BA=9F=E5=BC=83=E7=9A=84=20app/helper=20=E8=B5=84=E6=BA=90?= =?UTF-8?q?=E5=9B=9E=E9=80=80=E6=8F=8F=E8=BF=B0?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- AGENTS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 36e8c356d..5743d4932 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -54,7 +54,7 @@ For work that changes or reviews repository behavior, identify the domains actua The historical `app/core`, `app/helper`, and `app/utils` directories are compatibility-only virtual import roots. Never add physical Python source there and never use those imports from host code. Choose an owner by responsibility, not by whether a function is "shared" or has historically been called a helper. -`app/helper/` may contain only the non-Python `.resource-compat` marker so source archives retain a write target for old Docker images whose updater is fixed to that path. If such an updater writes the compiled site resources there, `app/application/site/__init__.py` exposes that directory only as a fallback when the canonical extension is absent. New images and current update flows must continue writing exclusively to `app/application/site/`. +The legacy roots have no physical directories in the source tree. Current images and update flows write site resources only to `app/application/site/`; plugin imports under `app.helper.*` are resolved exclusively by the exact runtime compatibility manifest. | Package | Owns | Must Not Own | Representative Files | |---|---|---|---| @@ -156,4 +156,4 @@ For the full documentation map and cross-references, refer to: **[Documentation Hub Index](./docs/rules/README.md)** -*Last Updated: 2026-08-14* +*Last Updated: 2026-08-15*