Optimize assistant context by requested themes

docs/CODEX_EXECUTION_LOG.md

@@ -10,6 +10,12 @@ Changed:
   fail-closed rejection of `done_reason=length` unchanged.
 - Added the output limit to the editable Unraid template and aligned all
   deployment defaults and documentation.
+- Browser QA in the central 28-municipality workbench exposed that an explicit
+  six-theme question still summarized every current vector theme. Agricultural
+  subclass intersections pushed context construction past 110 seconds.
+- Added deterministic Dutch theme selection before GIS calculation. Explicit
+  questions now calculate only named themes; general summaries and source
+  inventory questions deliberately retain full context.
 
 Validation evidence:
 - A read-only live production-chain probe with the 1,200-token setting
@@ -18,7 +24,16 @@ Validation evidence:
 - The complete readiness gate passed 713 backend tests, backend compilation,
   105 documented API routes with three explicit binary/non-envelope routes,
   one Alembic head and the frontend TypeScript and production build.
-- Tower deployment and browser verification follow in this pass.
+- After deterministic theme filtering was added, the complete readiness gate
+  passed 720 backend tests plus all compile, contract, Alembic, frontend and
+  shell gates.
+- The regional thematic operator dry-run resolved exactly 28 official
+  municipality Areas. The live Mol run in `Kempen Regional Workbench` imported
+  all five products with complete source coverage; the DOV operator imported
+  1,159 exact Mol soil polygons into the same project.
+- Browser validation then showed all six new themes as available and returned
+  3,638.41 ha space occupation, 31.76% share and the full 15-theme Mol summary
+  from persisted data.
 
 Next:
 - Deploy, rerun the exact six-theme Dutch question and verify the end-user