docs: reflect the LIBRARY/registry.py + bucket-backed state architecture

README.md

@@ -23,13 +23,20 @@ Generic command-routing compute node.
   to read.
 
 Adding a capability means adding a module under `/LIBRARY` and registering
-it in `LIBRARY/__init__.py`. `app.py` and `system.py` never need to change.
+it in `LIBRARY/registry.py`. `app.py` and `system.py` never need to change.
 
-`LIBRARY/data.py` bridges to the attached bucket (`1990two/PROJECT92-v2-storage`
-by default, override with `BUCKET_ID`) -- `save`/`load`/`list`/`delete`.
+`system.py` bridges to the attached bucket (`1990two/PROJECT92-v2-storage`
+by default, override with `BUCKET_ID`) -- `bucket_save`/`bucket_load`/
+`bucket_list`/`bucket_delete` (+ `_json` variants). Data retrieval is
+cross-cutting infrastructure, so it lives here rather than in a routed
+LIBRARY module. `LIBRARY/AGENTS/task_lock.py` and `LIBRARY/SYS/validate.py`
+persist their state through these bucket functions as small JSON files,
+specifically because the Space's own container disk resets on every
+restart/redeploy and the bucket doesn't.
 
-`LIBRARY/agents.py` bridges to model providers via `provider_keys` in
-`gate` -- `chat` command, OpenAI-compatible providers only.
+`LIBRARY/AGENTS/providers.py` bridges to model providers via `provider_keys`
+in `gate` -- target `agents`, `chat` command, OpenAI-compatible providers
+only.
 
 ## Required Space secrets
 - `SUPABASE_URL`