Extract scene camera adapters

docs/prompt-architecture-improvement-plan.md

@@ -86,9 +86,14 @@ Move or isolate later:
 
 - role graph generation for hardcore interaction categories into a dedicated
   module, for example `hardcore_role_graphs.py`;
-- camera-scene adapters into `scene_camera_adapters.py`;
 - category-library loading and inheritance helpers into `category_library.py`.
 
+Already isolated:
+
+- camera-scene prose and coworking composition adaptation live in
+  `scene_camera_adapters.py`; `prompt_builder.py` still owns camera config
+  parsing and row mutation.
+
 ### Pair / Adapter Layer
 
 Owner today: `build_insta_of_pair`.
@@ -285,10 +290,11 @@ Near-term:
 - Keep scene-camera adapters scoped by location family.
 - Use the memory note in
   `/home/ethanfel/.codex/memories/scene-camera-system.md` when editing POV.
+- Keep `scene_camera_adapters.py` as the owner for location-aware camera prose;
+  add new location families there one at a time.
 
 Medium-term:
 
-- Move coworking adapter into a scene-camera adapter module.
 - Build new adapters one location family at a time.
 
 ## Invariants To Preserve
@@ -307,6 +313,5 @@ Medium-term:
 1. Expand `tools/prompt_smoke.py` with close foreplay and POV penetration
    fixtures.
 2. Split Krea action/POV/clothing helpers into separate modules.
-3. Extract scene-camera adapters from `prompt_builder.py`.
-4. Split `__init__.py` node classes by family after behavior is covered by smoke
+3. Split `__init__.py` node classes by family after behavior is covered by smoke
    checks.

docs/prompt-pool-routing-map.md

@@ -776,7 +776,7 @@ Use these traces to narrow a problem in one pass.
 2. If scene is good and composition is bad, edit composition pools, not
    location pools.
 3. If a scene-camera adapter rewrote composition, inspect
-   `_coworking_composition_prompt` or the future adapter for that scene family.
+   `scene_camera_adapters.py`.
 4. If the issue comes from `Location Theme`, edit `THEMATIC_LOCATION_PRESETS`.
 
 ### Trigger missing after formatting