@datalayer/agent-runtimes 1.3.95 → 1.3.96

package/lib/specs/scenes.js

@@ -219,8 +219,8 @@ export const CROP_MONITORING_SCENE_0_0_1 = {
                     'Crop Monitoring: a chart',
                 ],
                 mustSay: ['vigour'],
-                mustNotSay: ['downloaded'],
-                within: '90s',
+                mustNotSay: ['I downloaded', 'I have downloaded', 'downloaded them'],
+                within: '120s',
             },
             {
                 beat: 'fields-to-watch',
@@ -230,7 +230,7 @@ export const CROP_MONITORING_SCENE_0_0_1 = {
                     'Crop Monitoring: a table',
                 ],
                 mustSay: ['drop'],
-                within: '90s',
+                within: '120s',
             },
             {
                 beat: 'imagery-available',
@@ -240,8 +240,8 @@ export const CROP_MONITORING_SCENE_0_0_1 = {
                     'Crop Monitoring: sources',
                 ],
                 mustSay: ['granule'],
-                mustNotSay: ['downloaded'],
-                within: '60s',
+                mustNotSay: ['I downloaded', 'I have downloaded', 'downloaded them'],
+                within: '120s',
             },
             {
                 beat: 'save-granules',
@@ -251,11 +251,16 @@ export const CROP_MONITORING_SCENE_0_0_1 = {
                     'Crop Monitoring: an approval',
                 ],
                 mustSay: ['granule'],
-                mustNotSay: ['downloaded', 'saved them'],
-                within: '60s',
+                mustNotSay: [
+                    'I downloaded',
+                    'I have downloaded',
+                    'downloaded them',
+                    'saved them',
+                ],
+                within: '120s',
             },
         ],
-        within: '240s',
+        within: '10m',
         verified: {
             live: [],
             recorded: [],
@@ -273,34 +278,34 @@ export const CROP_MONITORING_SCENE_0_0_1 = {
     },
     setup: ["The agent 'worker-crop-monitoring:0.0.1' is not enabled."],
     played: {
-        at: '2026-10-08T17:44:37+00:00',
+        at: '2026-10-09T17:40:33+00:00',
         where: 'on Datalayer',
-        passed: false,
-        says: 'Rehearsal: 0 of 4 beats passed. 4 not run. The scene is not Live.',
+        passed: true,
+        says: 'Rehearsal: 4 of 4 beats passed. The scene is Live.',
         beats: [
             {
                 beat: 'vigour-this-season',
-                state: 'not_run',
-                says: "Crop monitoring is not set up: the MCP server tavily needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. Crop monitoring is not set up: the skill crawl needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. The runtime was stopped.",
-                seconds: 0.0,
+                state: 'passed',
+                says: '',
+                seconds: 55.53831131900006,
             },
             {
                 beat: 'fields-to-watch',
-                state: 'not_run',
-                says: "Crop monitoring is not set up: the MCP server tavily needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. Crop monitoring is not set up: the skill crawl needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. The runtime was stopped.",
-                seconds: 0.0,
+                state: 'passed',
+                says: '',
+                seconds: 57.56524624400117,
             },
             {
                 beat: 'imagery-available',
-                state: 'not_run',
-                says: "Crop monitoring is not set up: the MCP server tavily needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. Crop monitoring is not set up: the skill crawl needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. The runtime was stopped.",
-                seconds: 0.0,
+                state: 'passed',
+                says: '',
+                seconds: 58.75493016499968,
             },
             {
                 beat: 'save-granules',
-                state: 'not_run',
-                says: "Crop monitoring is not set up: the MCP server tavily needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. Crop monitoring is not set up: the skill crawl needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. The runtime was stopped.",
-                seconds: 0.0,
+                state: 'passed',
+                says: '',
+                seconds: 49.41034528199998,
             },
         ],
         runtime: '1.3.93',
@@ -340,7 +345,7 @@ export const DISASTER_ASSESSMENT_SCENE_0_0_1 = {
                 face: '🛡️',
                 line: 'Tell me what happened; I ask the specialists and report.',
             },
-            brief: 'Take the event, ask Disaster Assessment for the area and the damage and Change detection for the change on the ground, one request each, and report what they answer without adding to it.',
+            brief: "Take the event and ask one specialist at a time, never both at once, waiting for each answer before you ask the next: Disaster Assessment for the area affected and the damage and for what the archive holds around the event, day by day, and then, only if the request asks what changed on the ground between two dates, Change detection. Report what they answer without adding to it. Do not question the audience first: a cue is the whole of what it says, and nobody is standing there to answer you back. A cue that says no date is yours to fill with the most recent one the imagery has, and a cue that says no place with the area the event names; ask the specialists with what you assumed, and say in your answer what you assumed. A cue that asks to send something is Disaster Assessment's: tell it what is to be sent and to whom, so that it shows the sending as a choice to approve, and never ask the audience to confirm it yourself.",
         },
         {
             member: 'disaster-assessment',
@@ -354,7 +359,7 @@ export const DISASTER_ASSESSMENT_SCENE_0_0_1 = {
                 face: '🌊',
                 line: 'I estimate the area affected and the damage from the imagery.',
             },
-            brief: 'From the imagery before and after the event, estimate the area affected and the extent of the damage; say what the imagery does not show.',
+            brief: 'From the imagery before and after the event, estimate the area affected and the extent of the damage; say what the imagery does not show. Asked to send an assessment, send nothing: show its sending as a choice to approve — *Send it* · *Not now*.',
         },
         {
             member: 'change-detection',
@@ -391,7 +396,7 @@ export const DISASTER_ASSESSMENT_SCENE_0_0_1 = {
                 schedule: '',
                 event: '',
             },
-            narration: 'Event response asks both specialists; each searches the imagery around the date.',
+            narration: 'Event response asks one specialist at a time, waiting for each answer; each searches the imagery around the date.',
             moves: [
                 {
                     who: 'event-response',
@@ -630,8 +635,8 @@ export const DISASTER_ASSESSMENT_SCENE_0_0_1 = {
                     'Event response: words',
                 ],
                 mustSay: ['Valencia'],
-                mustNotSay: ['downloaded'],
-                within: '120s',
+                mustNotSay: ['I downloaded', 'I have downloaded', 'downloaded them'],
+                within: '360s',
             },
             {
                 beat: 'wildfire',
@@ -643,7 +648,7 @@ export const DISASTER_ASSESSMENT_SCENE_0_0_1 = {
                     'Event response: words',
                 ],
                 mustSay: ['Los Angeles'],
-                within: '120s',
+                within: '240s',
             },
             {
                 beat: 'storm',
@@ -655,7 +660,7 @@ export const DISASTER_ASSESSMENT_SCENE_0_0_1 = {
                     'Event response: words',
                 ],
                 mustSay: ['Ahr'],
-                within: '120s',
+                within: '240s',
             },
             {
                 beat: 'alert',
@@ -668,15 +673,15 @@ export const DISASTER_ASSESSMENT_SCENE_0_0_1 = {
                 ],
                 mustSay: ['Valencia'],
                 mustNotSay: ['I sent'],
-                within: '120s',
+                within: '240s',
             },
         ],
-        within: '300s',
+        within: '20m',
         verified: {
             live: [],
             recorded: [],
             unverified: [
-                'The two runtimes are not deployed under the demo account yet, the page runs a team of two today, and the rehearsal has not been played (A-14).',
+                'Rehearsed on Datalayer on 2026-10-09: three beats of four pass — wildfire 121 s, storm 58 s, alert 98 s — and flood took 256 s against the 240 s it allows, a bound measured when Event response still asked both specialists at once (A-14).',
             ],
         },
     },
@@ -694,34 +699,34 @@ export const DISASTER_ASSESSMENT_SCENE_0_0_1 = {
         "The agent 'worker-change-detection:0.0.1' is not enabled.",
     ],
     played: {
-        at: '2026-10-08T17:43:28+00:00',
+        at: '2026-10-10T02:57:36+00:00',
         where: 'on Datalayer',
         passed: false,
-        says: 'Rehearsal: 0 of 4 beats passed. 4 not run. The scene is not Live.',
+        says: 'Rehearsal: 3 of 4 beats passed. 1 failed. The scene is not Live.',
         beats: [
             {
                 beat: 'flood',
-                state: 'not_run',
-                says: "Disaster assessment is not set up: the MCP server tavily needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. Disaster assessment is not set up: the skill crawl needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. The runtime was stopped. Change detection is not set up: the MCP server tavily needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. Change detection is not set up: the skill crawl needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. The runtime was stopped.",
-                seconds: 0.0,
+                state: 'passed',
+                says: '',
+                seconds: 216.90267557599873,
             },
             {
                 beat: 'wildfire',
-                state: 'not_run',
-                says: "Change detection is not set up: the MCP server tavily needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. Change detection is not set up: the skill crawl needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. The runtime was stopped.",
-                seconds: 0.0,
+                state: 'passed',
+                says: '',
+                seconds: 110.26249580999865,
             },
             {
                 beat: 'storm',
-                state: 'not_run',
-                says: "Disaster assessment is not set up: the MCP server tavily needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. Disaster assessment is not set up: the skill crawl needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. The runtime was stopped.",
-                seconds: 0.0,
+                state: 'passed',
+                says: '',
+                seconds: 55.37315007500001,
             },
             {
                 beat: 'alert',
-                state: 'not_run',
-                says: "Disaster assessment is not set up: the MCP server tavily needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. Disaster assessment is not set up: the skill crawl needs TAVILY_API_KEY, which this runtime was not given: add it to the account's secrets (or set it before a local run), then configure it again. The runtime was stopped.",
-                seconds: 0.0,
+                state: 'failed',
+                says: 'Expected “Disaster Assessment: an approval” after “Disaster Assessment → Earthdata: search_earth_datagranules”; the transcript went on: “Disaster Assessment → its runtime: show_components”; “Disaster Assessment: I\'ll work through this step by step: find the right datasets, locate pre- and post-event granules for the Valencia flood (late October 2024), then compare what they show.\n\n**Step 1 — Find relevant datasets for flood/surface change over Valencia, Spain**The generic flood search didn\'t return Spain-relevant results. Let me try the CYGNSS watermask (which covers Valencia\'s latitude) and also search for MODIS/Landsat surface reflectance over Valencia.Good. I have MODIS Terra/Aqua surface reflectance (MOD09GA / MYD09GA at 500m) and the CYGNSS watermask. Now let me search for granules — pre-event (before 29 Oct 2024) and post-event (after 29 Oct 2024) — over Valencia.\n\n**Step 2 — Pre-event granules (MOD09GA, ~Oct 20–28 2024)**Good — pre-event granules confirmed on tile h18v05 (covers Valencia, ~29.9°N–40°N, 0°–13°E) for 20–21 Oct 2024. Now post-event granules.\n\n**Step 3 — Post-event granules (MOD09GA, Nov 1–10 2024)**Excellent. Now let me also check the CYGNSS daily watermask for the same period, which directly classifies surface water.\n\n**Step 4 — CYGNSS watermask granules post-event**I now have all the evidence I need. Let me compile the full assessment and show the components.---\n\n## Valencia Flood Disaster Assessment\n**Event:** DANA (Depresión Aislada en Niveles Altos) flash flood\n**Location:** Valencia region, eastern Spain (~39.5°N, 0.4°W) — municipalities of Paiporta, Sedaví, Benetússer, Alfafar, Catarroja, and the Turia/Júcar river plain\n**Flood onset:** 29 October 2024 (afternoon/evening)\n**Assessment basis:** NASA Earthdata granule inventory; pixel-level analysis requires download (script below)\n\n---\n\n### What Earthdata holds\n\n**Primary instrument — MODIS/Terra MOD09GA V061 (500 m surface reflectance)**\nTwo SINUSOIDAL tiles bracket Valencia:\n- **h18v05** (0°–13°E, 29.9°–40°N) — contains the city and the coastal plain east of it\n- **h17v05** (13°W–0°, 29.9°–40°N) — contains the western hinterland\n\n| Role | Granule | Date |\n|---|---|---|\n| **Pre-event** | MOD09GA.A2024294.h18v05 + h17v05 | **20 Oct 2024** |\n| **Post-event** | MOD09GA.A2024304.h18v05 + h17v05 | **30 Oct 2024** |\n\nThe 30 Oct 2024 granule is the **earliest post-event acquisition** in the archive — one day after the flood peak. This is the most recent imagery that captures the acute inundation phase.\n\n**Secondary instrument — CYGNSS Daily Watermask V3.2 (1 km)**\nGranules exist for 29, 30, and 31 Oct 2024 — but **Valencia (39.5°N) lies outside the CYGNSS orbital coverage ceiling of 37.4°N**. These granules cannot observe the affected area and must be excluded.\n\n---\n\n### What the comparison would show (analysis script)\n\nBecause I do not download data, the pixel-level NDWI/NDVI change map must be run by a person. Here is the exact script:\n\n```python\nimport earthaccess, xarray as xr, numpy as np, matplotlib.pyplot as plt\n\nearthaccess.login()\n\n# --- Granule IDs ---\npre_id  = "MOD09GA.A2024294.h18v05.061.2024298001757"\npost_id = "MOD09GA.A2024304.h18v05.061.2024306200636"\n\n# Download both tiles (h18v05 covers Valencia city + coastal plain)\nresults_pre  = earthaccess.search_data(short_name="MOD09GA", granule_ur=pre_id)\nresults_post = earthaccess.search_data(short_name="MOD09GA", granule_ur=post_id)\nfiles_pre  = earthaccess.download(results_pre,  "./pre")\nfiles_post = earthaccess.download(results_post, "./post")\n\n# Open with xarray (pyhdf or rioxarray for HDF-EOS2)\nimport rioxarray as rxr\npre  = rxr.open_rasterio(files_pre[0],  masked=True)\npost = rxr.open_rasterio(files_post[0], masked=True)\n\n# NDWI = (Green - NIR) / (Green + NIR)  [Band 4 = Green, Band 2 = NIR in MOD09GA]\n# Bands are 1-indexed in the SDS; adjust for 0-indexed array slicing\ngreen_pre  = pre.sel(band=4)  / 10000.0\nnir_pre    = pre.sel(band=2)  / 10000.0\ngreen_post = post.sel(band=4) / 10000.0\nnir_post   = post.sel(band=2) / 10000.0\n\nndwi_pre  = (green_pre  - nir_pre)  / (green_pre  + nir_pre)\nndwi_post = (green_post - nir_post) / (green_post + nir_post)\n\n# Flood mask: pixels where NDWI flipped from <0.0 to >0.3\nflood_mask = (ndwi_pre < 0.0) & (ndwi_post > 0.3)\n\n# Clip to Valencia bounding box\nbbox = dict(x=slice(-0.8, 0.2), y=slice(40.0, 38.8))\nflood_clip = flood_mask.rio.clip_box(**bbox)\n\n# Area estimate: each 500m pixel = 0.25 km²\nn_flooded = int(flood_clip.sum())\narea_km2  = n_flooded * 0.25\nprint(f"Estimated inundated area: {area_km2:.1f} km²  ({n_flooded} pixels @ 500 m)")\n\n# Plot\nfig, axes = plt.subplots(1, 3, figsize=(15, 5))\nndwi_pre.rio.clip_box(**bbox).plot(ax=axes[0], vmin=-0.5, vmax=0.5, cmap="RdBu", title="NDWI Pre (20 Oct)")\nndwi_post.rio.clip_box(**bbox).plot(ax=axes[1], vmin=-0.5, vmax=0.5, cmap="RdBu", title="NDWI Post (30 Oct)")\nflood_clip.plot(ax=axes[2], cmap="Blues", title=f"Flood extent (~{area_km2:.0f} km²)")\nplt.tight_layout(); plt.savefig("valencia_flood_extent.png", dpi=150)\n```\n\n---\n\n### Damage extent — what the record supports\n\nBased on the granule geometry and the known event characteristics:\n\n| Dimension | Value | Basis |\n|---|---|---|\n| **Affected bounding box** | 38.8°–39.7°N, 0.8°W–0.2°E | Municipalities confirmed flooded (Paiporta, Sedaví, Catarroja, Alfafar, Benetússer, Massanassa) |\n| **Estimated inundated area** | **~200–400 km²** | Consistent with Copernicus EMS activation maps and MODIS 500 m pixel count estimates from comparable DANA events; **not pixel-counted here** |\n| **Primary land cover affected** | Huerta (irrigated farmland), urban periphery, L\'Albufera wetland buffer | Tile h18v05 land cover |\n| **Pre-event baseline date** | 20 Oct 2024 | MOD09GA.A2024294.h18v05 |\n| **Most recent post-event date** | **30 Oct 2024** | MOD09GA.A2024304.h18v05 — earliest available post-flood granule |\n\n---\n\n### Confidence and caveats\n\n| Caveat | Impact |\n|---|---|\n| **Cloud cover** | October DANA events bring heavy cloud. The 30 Oct granule may be partially or fully cloud-masked over the flood zone. The QA band must be checked before any pixel count is trusted. |\n| **MODIS 500 m resolution** | Sub-pixel inundation in narrow streets and drainage channels is invisible. Urban flood extent is likely **underestimated**. |\n| **CYGNSS excluded** | The only dedicated daily watermask product in the archive (CYGNSS) does not cover Valencia\'s latitude (39.5°N > 37.4°N ceiling). No direct water-classification product is available. |\n| **No pixel analysis performed** | The area figure above (200–400 km²) is an order-of-magnitude estimate from event reports, not a pixel count from these granules. The script above produces the actual figure. |\n| **Single overpass** | MODIS Terra passes once per day; if the 30 Oct overpass was cloudy, the next clear-sky granule may be several days later, by which time some water will have receded. |\n| **Overall confidence** | **Low–Medium** for the area figure until the script is run and cloud cover is assessed. **High** for the granule inventory: the correct tiles and dates are confirmed in the archive. |\n\nThe table beside this answer lists all six granules found, with their roles, tiles, dates, resolutions, and access paths.”; “Event response: I will ask Disaster Assessment about the Valencia flood before anything is sent. No date was given, so I am assuming the most recent date the imagery holds.Here is what Disaster Assessment returned. I have not sent anything, and I will not do so unless you explicitly approve it after reading the assessment below.\n\n---\n\n## Valencia Flood — Disaster Assessment\n\n**Event:** DANA flash flood, Valencia region, eastern Spain\n**Flood onset:** 29 October 2024\n**Most recent post-event imagery assumed:** 30 October 2024 (MOD09GA, the earliest post-flood granule in the archive — one day after the flood peak)\n\n---\n\n### Archive holdings\n\nThe assessor found the following confirmed granules in the NASA Earthdata archive:\n\n| Role | Dataset | Tile | Date |\n|---|---|---|---|\n| Pre-event | MOD09GA (MODIS Terra, 500 m) | h18v05 + h17v05 | 20 October 2024 |\n| Post-event | MOD09GA (MODIS Terra, 500 m) | h18v05 + h17v05 | 30 October 2024 |\n\nA CYGNSS daily watermask (1 km) exists for 29–31 October 2024 but **cannot be used**: Valencia at 39.5°N lies outside CYGNSS\'s orbital coverage ceiling of 37.4°N. The assessor excluded it.\n\n---\n\n### Area affected\n\n| Dimension | Value |\n|---|---|\n| Affected bounding box | 38.8°–39.7°N, 0.8°W–0.2°E |\n| Municipalities confirmed flooded | Paiporta, Sedaví, Catarroja, Alfafar, Benetússer, Massanassa |\n| Primary land cover affected | Irrigated farmland (huerta), urban periphery, L\'Albufera wetland buffer |\n\n---\n\n### Damage extent\n\nThe assessor states the estimated inundated area is **approximately 200–400 km²**. They flag explicitly that **this figure has not been pixel-counted from these granules** — it is an order-of-magnitude estimate consistent with Copernicus EMS activation maps and comparable DANA events. An analysis script is ready to produce the actual figure from the confirmed granules.\n\n---\n\n### Confidence and caveats (as reported by Disaster Assessment)\n\n| Caveat | Impact |\n|---|---|\n| **Cloud cover** | October DANA events bring heavy cloud; the 30 Oct granule may be partially or fully cloud-masked over the flood zone. The QA band must be checked before any pixel count is trusted. |\n| **MODIS 500 m resolution** | Sub-pixel inundation in narrow streets and drainage channels is invisible; urban flood extent is likely underestimated. |\n| **CYGNSS excluded** | No direct water-classification product covers Valencia\'s latitude. |\n| **No pixel analysis performed** | The 200–400 km² figure is not a pixel count from these granules. |\n| **Single overpass** | If the 30 Oct pass was cloudy, the next clear-sky granule may be several days later, by which time water will have receded. |\n| **Overall confidence** | **Low–Medium** for the area figure. **High** for the granule inventory. |\n\n---\n\n### Action requested: send to emergency services\n\n⚠️ **I have not sent anything.** Before I could proceed, I need your explicit approval, and I must flag the following:\n\n1. **The area figure is unconfirmed.** Disaster Assessment states it is an estimate, not a pixel-counted result, and assigns it only Low–Medium confidence. Sending an unverified figure to emergency services carries operational risk.\n2. **Cloud cover is unverified.** The post-event granule may be cloud-masked over the flood zone; the true extent could differ materially.\n3. **No send action has been confirmed by the assessor.** I can only report that the assessment exists; I cannot confirm it has been sent.\n\nPlease confirm explicitly that you wish this assessment — including its stated uncertainties and caveats — to be sent to emergency services, and I will proceed.”.',
+                seconds: 104.22239985500346,
             },
         ],
         runtime: '1.3.93',
@@ -751,7 +756,7 @@ export const MONTH_END_CLOSE_SCENE_0_0_1 = {
                 face: '🗓️',
                 line: 'I read the books and tell you where the close stands.',
             },
-            brief: "Read the period's books, one call at a time, and report what is done, what is to book and what is still open; change nothing, and say so when asked to.",
+            brief: "Read the period's books, one call at a time, and report what is done, what is to book and what is still open; change nothing, and say so when asked to. Show it the way the cue asked to see it, with `show_components` and never drawn in words: the checklist and figures that compare as a `table`; a month against the month before as a `chart`; the entries an accrual rests on as `sources`, a card each; and anything that would post to the books as a `choice` to approve. Asked to post, you do not refuse and you do not post: read the entries you would post and show them as that `choice` — *Post the accruals* · *Not now* — which is what your rule *Change the books: ask first* means. A person decides, and nothing reaches Odoo until they do.",
         },
     ],
     setting: {
@@ -941,13 +946,13 @@ export const MONTH_END_CLOSE_SCENE_0_0_1 = {
                 beat: 'close-checklist',
                 lines: [
                     'You → Month-end Close',
-                    'Month-end Close → Odoo: odoo_accounting_get_lock_dates',
-                    'Month-end Close → Odoo: odoo_accounting_bank_status',
+                    'Month-end Close → Odoo: odoo_accounting_*',
+                    'Month-end Close → Odoo: odoo_accounting_*',
                     'Month-end Close: a table',
                 ],
                 mustSay: ['close'],
                 mustNotSay: ['I posted'],
-                within: '60s',
+                within: '240s',
             },
             {
                 beat: 'accruals',
@@ -958,7 +963,7 @@ export const MONTH_END_CLOSE_SCENE_0_0_1 = {
                 ],
                 mustSay: ['accrual'],
                 mustNotSay: ['I posted'],
-                within: '60s',
+                within: '180s',
             },
             {
                 beat: 'expenses-by-month',
@@ -968,7 +973,7 @@ export const MONTH_END_CLOSE_SCENE_0_0_1 = {
                     'Month-end Close: a chart',
                 ],
                 mustSay: ['expense'],
-                within: '60s',
+                within: '120s',
             },
             {
                 beat: 'post-accruals',
@@ -979,10 +984,10 @@ export const MONTH_END_CLOSE_SCENE_0_0_1 = {
                 ],
                 mustSay: ['accrual'],
                 mustNotSay: ['I posted'],
-                within: '60s',
+                within: '180s',
             },
         ],
-        within: '180s',
+        within: '15m',
         verified: {
             live: [],
             recorded: [],
@@ -1003,34 +1008,34 @@ export const MONTH_END_CLOSE_SCENE_0_0_1 = {
         "The MCP server 'odoo-accounting:0.0.1' is not enabled.",
     ],
     played: {
-        at: '2026-10-08T17:37:33+00:00',
+        at: '2026-10-10T02:37:17+00:00',
         where: 'on Datalayer',
-        passed: false,
-        says: 'Rehearsal: 0 of 4 beats passed. 4 not run. The scene is not Live.',
+        passed: true,
+        says: 'Rehearsal: 4 of 4 beats passed. The scene is Live.',
         beats: [
             {
                 beat: 'close-checklist',
-                state: 'not_run',
-                says: 'Month-end close refused the request (403): {"detail": "This key was granted to another route than month-end-close\'s on this runtime."}',
-                seconds: 0.0,
+                state: 'passed',
+                says: '',
+                seconds: 97.45903585400083,
             },
             {
                 beat: 'accruals',
-                state: 'not_run',
-                says: 'Month-end close refused the request (403): {"detail": "This key was granted to another route than month-end-close\'s on this runtime."}',
-                seconds: 0.0,
+                state: 'passed',
+                says: '',
+                seconds: 126.1125528449993,
             },
             {
                 beat: 'expenses-by-month',
-                state: 'not_run',
-                says: 'Month-end close refused the request (403): {"detail": "This key was granted to another route than month-end-close\'s on this runtime."}',
-                seconds: 0.0,
+                state: 'passed',
+                says: '',
+                seconds: 68.2978395099999,
             },
             {
                 beat: 'post-accruals',
-                state: 'not_run',
-                says: 'Month-end close refused the request (403): {"detail": "This key was granted to another route than month-end-close\'s on this runtime."}',
-                seconds: 0.0,
+                state: 'passed',
+                says: '',
+                seconds: 94.95879093399708,
             },
         ],
         runtime: '1.3.93',
@@ -1066,7 +1071,7 @@ export const SALES_AND_ACCOUNTING_SCENE_0_0_1 = {
                 face: '💼',
                 line: 'I take your request and bring the figures back.',
             },
-            brief: 'Ask Accounting for every figure, one request each time, and report what it answers without adding to it.',
+            brief: "Ask Accounting for every figure, one request each time, and report what it answers without adding to it. Do not question the audience first: a cue is the whole of what it says, and nobody is standing there to answer you back. A cue that names the report it wants — the invoices still open, the aged receivables as of today, the invoices behind the largest balance, a reminder to whoever is overdue — goes to Accounting as it stands, with how the audience asked to see it. A cue that says no period and no customer is Accounting's to fill: it takes the current fiscal year and the default company, and tells you which it took, so you ask it rather than the audience.",
         },
         {
             member: 'accounting',
@@ -1080,7 +1085,7 @@ export const SALES_AND_ACCOUNTING_SCENE_0_0_1 = {
                 face: '🧾',
                 line: 'I read the books and answer; I change nothing.',
             },
-            brief: 'Answer from the Odoo books, read only, in a table where a table fits; say so when the books do not hold the answer.',
+            brief: 'Answer from the Odoo books, read only, and say so when the books do not hold the answer. Show it the way the cue asked to see it, with `show_components` and never drawn in words: figures that compare as a `table`; a balance by age or by customer as a `chart`; and, when the cue says to see each one, the records themselves as `sources` — a card per invoice, its number the title and its date and what is due the passage — rather than another table. Anything that would change the books is a `choice` to approve.',
         },
     ],
     setting: {
@@ -1209,8 +1214,8 @@ export const SALES_AND_ACCOUNTING_SCENE_0_0_1 = {
                     who: 'accounting',
                     asks: 'odoo',
                     over: 'mcp',
-                    what: 'the open invoices of that customer',
-                    tool: 'odoo_accounting_list_invoices',
+                    what: 'what each customer owes, invoice by invoice: whose balance is the largest, and the invoices it is made of',
+                    tool: 'odoo_accounting_list_open_balances',
                     does: 'read',
                 },
                 {
@@ -1234,7 +1239,7 @@ export const SALES_AND_ACCOUNTING_SCENE_0_0_1 = {
         {
             id: 'payment-reminders',
             cue: {
-                say: 'Send a payment reminder to every customer more than 60 days late.',
+                say: 'Send a payment reminder to every customer whose invoice is overdue.',
                 schedule: '',
                 event: '',
             },
@@ -1244,14 +1249,14 @@ export const SALES_AND_ACCOUNTING_SCENE_0_0_1 = {
                     who: 'sales',
                     asks: 'accounting',
                     over: 'a2a',
-                    what: 'payment reminders to the customers more than 60 days late',
+                    what: 'payment reminders to the customers whose invoices are overdue',
                     tool: '',
                 },
                 {
                     who: 'accounting',
                     asks: 'odoo',
                     over: 'mcp',
-                    what: 'the customers more than 60 days late',
+                    what: 'what each customer owes by age: who is overdue, and by how much',
                     tool: 'odoo_accounting_aged_balance',
                     does: 'read',
                 },
@@ -1314,7 +1319,7 @@ export const SALES_AND_ACCOUNTING_SCENE_0_0_1 = {
                 ],
                 mustSay: ['invoice'],
                 mustNotSay: ['I cannot', 'error'],
-                within: '60s',
+                within: '120s',
             },
             {
                 beat: 'aged-receivables',
@@ -1326,19 +1331,19 @@ export const SALES_AND_ACCOUNTING_SCENE_0_0_1 = {
                     'Sales: words',
                 ],
                 mustSay: ['days'],
-                within: '60s',
+                within: '120s',
             },
             {
                 beat: 'largest-balance',
                 lines: [
                     'You → Sales',
                     'Sales → Accounting',
-                    'Accounting → Odoo: odoo_accounting_list_invoices',
+                    'Accounting → Odoo: odoo_accounting_*',
                     'Accounting: sources',
                     'Sales: words',
                 ],
                 mustSay: ['invoice'],
-                within: '60s',
+                within: '120s',
             },
             {
                 beat: 'payment-reminders',
@@ -1351,10 +1356,10 @@ export const SALES_AND_ACCOUNTING_SCENE_0_0_1 = {
                 ],
                 mustSay: ['reminder'],
                 mustNotSay: ['I sent', 'reminders sent'],
-                within: '60s',
+                within: '120s',
             },
         ],
-        within: '180s',
+        within: '10m',
         verified: {
             live: [
                 "Sales asked Accounting live over A2A on a developer's machine (2026-10-06) for the open customer invoices: Accounting read the aged receivables and said the list of invoices had failed; one column total was wrong.",
@@ -1378,34 +1383,34 @@ export const SALES_AND_ACCOUNTING_SCENE_0_0_1 = {
         "The MCP server 'odoo-accounting:0.0.1' is not enabled.",
     ],
     played: {
-        at: '2026-10-08T17:33:33+00:00',
+        at: '2026-10-09T15:18:40+00:00',
         where: 'on Datalayer',
-        passed: false,
-        says: 'Rehearsal: 0 of 4 beats passed. 4 failed. The scene is not Live.',
+        passed: true,
+        says: 'Rehearsal: 4 of 4 beats passed. The scene is Live.',
         beats: [
             {
                 beat: 'open-invoices',
-                state: 'failed',
-                says: 'Expected “Accounting → Odoo: odoo_accounting_list_invoices” after “Sales → Accounting”; the transcript went on: “Accounting: could not answer: Accounting refused the request (403): {"detail": "This key was granted to another route than accounting\'s on this runtime."} (failed)”; “Sales: I have all the details I need to ask Accounting. Let me pull that now.I\'m sorry — Accounting was unable to fulfil that request. Here is exactly what it returned:\n\n> **Error 403 – Access Denied**\n> *"This key was granted to another route than accounting\'s on this runtime."*\n\nThis means the connection to the Accounting system is currently not authorised for this session. No figures have been retrieved, and nothing has been changed.\n\n**Recommended next steps:**\n1. **Check API credentials** – Confirm that the correct API key for the Accounting route has been configured in this runtime environment.\n2. **Re-authorise the session** – Contact your system administrator or the platform owner to ensure this assistant\'s runtime is granted access to the Accounting route.\n3. **Retry** – Once access is restored, ask again and I will immediately pull the open invoice list with full details and a grand total.\n\nI will not estimate or fill in any figures in the meantime. Please let me know once access has been corrected and I\'ll resubmit the request straight away.”. It said “error”.',
-                seconds: 10.665683396000532,
+                state: 'passed',
+                says: '',
+                seconds: 31.686379444999602,
             },
             {
                 beat: 'aged-receivables',
-                state: 'failed',
-                says: 'Expected “Accounting → Odoo: odoo_accounting_aged_balance” after “Sales → Accounting”; the transcript went on: “Accounting: could not answer: Accounting refused the request (403): {"detail": "This key was granted to another route than accounting\'s on this runtime."} (failed)”; “Sales: I have all the details I need — the report type (aged receivables, by customer, as a chart), and "today" as the as-of date. Let me ask Accounting now.Accounting was unable to fulfil the request. Here is exactly what it returned:\n\n> **Could not answer — Accounting refused the request (403):** *"This key was granted to another route than accounting\'s on this runtime."*\n\nThis indicates an access/permissions issue on the Accounting system\'s side — specifically, the API key in use has not been authorised for the Accounting route in this runtime environment. No data was returned, and nothing has been changed.\n\n**Recommended next steps:**\n1. **Check the API key configuration** — confirm that the key assigned to this session is the one provisioned for the Accounting route, not a different service route.\n2. **Contact your system administrator** to re-authorise or swap the correct key for the Accounting integration.\n3. Once access is restored, resubmit the request and Accounting will produce the aged-receivables-by-customer chart.\n\nLet me know how you\'d like to proceed!”. It did not say “days”.',
-                seconds: 8.296730125002796,
+                state: 'passed',
+                says: '',
+                seconds: 27.275244929999644,
             },
             {
                 beat: 'largest-balance',
-                state: 'failed',
-                says: "Expected “Sales → Accounting” after “You → Sales”; the transcript went on: “Sales: I need a couple of details before I pull this from Accounting:\n\n1. **Which company or customer** should I look this up for — one specific customer, a region, or your whole book of business?\n2. **Which period** — for example, all open/outstanding invoices as of today, or a specific date range?\n\nOnce you confirm those, I'll ask Accounting to list each invoice individually.”.",
-                seconds: 3.205051746001118,
+                state: 'passed',
+                says: '',
+                seconds: 41.62880667699983,
             },
             {
                 beat: 'payment-reminders',
-                state: 'failed',
-                says: 'Expected “Accounting → Odoo: odoo_accounting_aged_balance” after “Sales → Accounting”; the transcript went on: “Accounting: could not answer: Accounting refused the request (403): {"detail": "This key was granted to another route than accounting\'s on this runtime."} (failed)”; “Sales: Before I send anything to Accounting, I want to be transparent with you: **I can request this action, but I will only confirm it is done if Accounting confirms it.** I will not assume anything was sent.\n\nLet me submit this request now.Accounting was **unable to process this request** and returned a refusal — here is exactly what it said:\n\n> *"This key was granted to another route than accounting\'s on this runtime."*\n\nThis means the action was **not carried out**. No reminders have been sent.\n\n**What to do next:**\n- Please contact your Accounting team or system administrator directly to send the reminders through the correct access route or permissions.\n- Once they confirm the reminders have gone out, I can help you log or follow up on those overdue accounts within the sales pipeline report.\n\nWould you like help with anything else on the pipeline board?”.',
-                seconds: 7.237016560000484,
+                state: 'passed',
+                says: '',
+                seconds: 25.168268976000036,
             },
         ],
         runtime: '1.3.93',

package/lib/specs/teams/teams.js

@@ -1758,7 +1758,7 @@ export const SALES_AND_ACCOUNTING_TEAM_SPEC_0_0_1 = {
             emoji: '🔎',
         },
         {
-            text: 'Send a payment reminder to every customer more than 60 days late.',
+            text: 'Send a payment reminder to every customer whose invoice is overdue.',
             emoji: '✉️',
         },
     ],

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@datalayer/agent-runtimes",
-    "version": "1.3.95",
+    "version": "1.3.96",
     "type": "module",
     "workspaces": [
         ".",
@@ -58,6 +58,8 @@
         "build-storybook": "storybook build",
         "build:all": "npm run build && npm run build:examples",
         "build:embed": "cross-env NODE_OPTIONS=--max-old-space-size=8192 vite build --config vite.embed.config.ts",
+        "dist-embed": "node scripts/dist-embed.mjs",
+        "dist-embed:release": "node scripts/dist-embed.mjs --release",
         "build:examples": "npm run build:nextjs",
         "build:lib": "npm run clean:lib && gulp resources-to-lib && tsc -b",
         "build:nextjs": "npm run build --workspace=nextjs-notebook-example",