agl 43.3.2 → 43.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (76) hide show
  1. package/changelog.md +12 -0
  2. package/dist_serve/bundle.js +1377 -1375
  3. package/dist_serve/bundle.js.map +2 -2
  4. package/dist_ts/00_commitinfo_data.js +1 -1
  5. package/dist_ts/aglapi/interfaces.d.ts +5 -0
  6. package/dist_ts/aglapi/interfaces.js +2 -1
  7. package/dist_ts/classes.authstore.js +5 -2
  8. package/dist_ts/classes.claudeharness.js +4 -3
  9. package/dist_ts/classes.codexclientadapter.d.ts +5 -0
  10. package/dist_ts/classes.codexclientadapter.js +12 -6
  11. package/dist_ts/classes.controller.d.ts +22 -5
  12. package/dist_ts/classes.controller.js +149 -61
  13. package/dist_ts/classes.mcpclient.d.ts +2 -2
  14. package/dist_ts/classes.mcpclient.js +14 -9
  15. package/dist_ts/classes.mcptools.d.ts +1 -1
  16. package/dist_ts/classes.mcptools.js +2 -1
  17. package/dist_ts/classes.opencodeclient.js +20 -4
  18. package/dist_ts/driver/functions.driverinstructions.d.ts +1 -1
  19. package/dist_ts/driver/functions.driverinstructions.js +2 -1
  20. package/dist_ts/fleet/classes.deploymodels.d.ts +58 -1
  21. package/dist_ts/fleet/classes.deploymodels.js +121 -2
  22. package/dist_ts/fleet/classes.deploymonitor.d.ts +193 -47
  23. package/dist_ts/fleet/classes.deploymonitor.js +548 -180
  24. package/dist_ts/fleet/classes.gitfacts.d.ts +4 -1
  25. package/dist_ts/fleet/classes.gitfacts.js +13 -10
  26. package/dist_ts/fleet/classes.service.d.ts +2 -0
  27. package/dist_ts/fleet/classes.service.js +6 -3
  28. package/dist_ts/fleet/functions.deployprobes.js +21 -2
  29. package/dist_ts/fleet/functions.deploystatus.d.ts +26 -0
  30. package/dist_ts/fleet/functions.deploystatus.js +33 -0
  31. package/dist_ts/fleet/functions.deployvalidation.d.ts +1 -0
  32. package/dist_ts/fleet/functions.deployvalidation.js +5 -2
  33. package/dist_ts/functions.deploycli.js +3 -2
  34. package/dist_ts/functions.deviceapi.d.ts +7 -6
  35. package/dist_ts/functions.deviceapi.js +13 -5
  36. package/dist_ts/functions.mcpdeploytools.js +3 -1
  37. package/dist_ts/functions.promptreply.d.ts +13 -0
  38. package/dist_ts/functions.promptreply.js +17 -0
  39. package/dist_ts_interfaces/deployments.d.ts +38 -6
  40. package/dist_ts_interfaces/deployments.js +7 -3
  41. package/dist_ts_interfaces/devices.d.ts +2 -1
  42. package/dist_ts_interfaces/devices.js +1 -1
  43. package/dist_ts_interfaces/inbox.d.ts +10 -1
  44. package/dist_ts_interfaces/inbox.js +1 -1
  45. package/dist_ts_interfaces/mcprequests.d.ts +1 -1
  46. package/package.json +1 -1
  47. package/readme.md +29 -11
  48. package/ts/00_commitinfo_data.ts +1 -1
  49. package/ts/aglapi/interfaces.ts +1 -0
  50. package/ts/classes.authstore.ts +4 -1
  51. package/ts/classes.claudeharness.ts +3 -2
  52. package/ts/classes.codexclientadapter.ts +11 -5
  53. package/ts/classes.controller.ts +161 -72
  54. package/ts/classes.mcpclient.ts +14 -5
  55. package/ts/classes.mcptools.ts +1 -0
  56. package/ts/classes.opencodeclient.ts +23 -3
  57. package/ts/driver/functions.driverinstructions.ts +1 -0
  58. package/ts/fleet/classes.deploymodels.ts +113 -1
  59. package/ts/fleet/classes.deploymonitor.ts +565 -179
  60. package/ts/fleet/classes.gitfacts.ts +10 -8
  61. package/ts/fleet/classes.service.ts +7 -1
  62. package/ts/fleet/functions.deployprobes.ts +16 -1
  63. package/ts/fleet/functions.deploystatus.ts +56 -0
  64. package/ts/fleet/functions.deployvalidation.ts +4 -1
  65. package/ts/functions.deploycli.ts +2 -1
  66. package/ts/functions.deviceapi.ts +19 -9
  67. package/ts/functions.mcpdeploytools.ts +2 -0
  68. package/ts/functions.promptreply.ts +20 -0
  69. package/ts_interfaces/deployments.ts +39 -6
  70. package/ts_interfaces/devices.schema.json +1 -1
  71. package/ts_interfaces/devices.ts +2 -1
  72. package/ts_interfaces/inbox.ts +8 -1
  73. package/ts_web/00_commitinfo_data.ts +1 -1
  74. package/ts_web/elements.deployments.ts +20 -4
  75. package/ts_web/elements.harnesscontrollerapp.ts +43 -13
  76. package/ts_web/elements.inbox.ts +3 -3
package/changelog.md CHANGED
@@ -1,5 +1,17 @@
1
1
  # Changelog
2
2
 
3
+ ## 2026-11-12 - 43.4.0
4
+
5
+ ### Features
6
+
7
+ - The Deployments status is stored and refreshed in the background (AGL-1704): the Deployments view, `agl deploy status`, `agl release status` without a repository, the driver's `deploy_status`, a device's host view and the Inbox's deploy go's answer at once from the status the controller last computed, instead of walking the workspace roots and reading the board and git for every target on each read. The controller computes it after every pass (at start, every five minutes, after a fleet release and after a saved configuration) and once board changes settle, one run at a time; a request during a run shares the one run after it. The status is kept in the controller's database (`agl_fleet_deploy_status`, one document per controller), so after a restart it is shown at once with the time it was checked, and the `undeployed` AutoLabel shows from the first board read. Where a maintenance window stands, whether a target may deploy now and the busy sessions are applied when the status is read. A read before the first computation waits up to 20 s and is then refused as still being computed (`deploy_unavailable` with its own message), which a device reads as `failed` with a reference instead of `not_running`. A remote whose fetched tags cannot be read now fails the computation, naming the repository, and the last status stands with the failure recorded beside it (before, the repository read as one without releases); a status over 4 MiB fails its computation instead of being cut. A probe's error text no longer repeats a token in the probe URL's query or fragment. `agl release status REPO`, `agl deploy history` and a ticket's "Where it runs" are still read when asked. Board changes are computed 2 s after the last one and at most 10 s after the first, so a steady stream of changes no longer holds the status off; a fleet landing asks for a pass as a release does, so what the next release ships shows at once; a maintenance window opening or ending reaches the views at that moment, no longer with the next pass; and saving the standard directories, adding a project or removing one makes the next computation walk the workspace again. The browser no longer reads the Deployments view again on every board change: the controller tells it when the status changed. While the newest computation failed, the status says so beside the last one computed: the Deployments view and `agl deploy status` show "The last check failed at …" with its reference, `agl deploy status --json` and the driver's `deploy_status` carry `failure`, and an open view hears when a failure appears and when the next check clears it. A device reading the host before the first computation stored a status no longer leaves a failure journal entry per read: it reads `failed`, with the reference the failed computation was recorded under, or without one while it still runs. The owner (in the browser or through the owner's MCP tools) and the driver can now ask for a full check at once ("update deployments"): `controller.deploy.refresh`, `agl.mcp.deploy.refresh` with the local owner capability and the MCP and driver tool `deploy_refresh` fetch, probe and compute now, sharing the pass in progress' follow-up with every other request, wait up to 60 s and answer `refreshed` or `refreshing` with when the status was checked; its end reaches open views also when nothing changed. Opening the Deployments view asks for one in the background while it shows the stored status, and **Probe all** is now one full check instead of a probe per target. The driver's instructions say when to call it. `agl deploy` has no `refresh` verb. An earlier release starts with the new collection in place and ignores it.
8
+
9
+ ### Fixes
10
+
11
+ - The device contract's `child` answer names only the replies a child takes (AGL-1701): `TDeviceInboxAnswer` said a `child` item is answered with "the same replies" as a session's, `device.elicitation.reply` included, but a direct child (an OpenCode subagent) asks only permissions and questions, since OpenCode hands AGL no MCP forms. A `child` item is answered with `device.permission.reply` or `device.question.reply` and the child's `childSessionId`, as since device protocol 1.2; the Inbox's MCP form item can no longer live in or be answered as a child (`IControllerInboxElicitationItem`'s `where` and `answer`), and the web Inbox drops its unreachable child checks for one. No wire change; the device protocol stays 1.3.
12
+ - An answer to a permission or question the session no longer holds is refused as a concurrent change, not as a malformed request (AGL-1687): when another client answered it first, or its turn moved on, a conversation's and a direct child's reply refused it `invalid_request` (OpenCode), a Codex or Claude Code conversation's as a controller fault with a failure journal reference, a Flex conversation's as `flex_operation_failed`, a native session's `not_found`, and one answered between AGL's read and its answer as a controller fault (OpenCode, Codex) or `flex_operation_failed` (Flex). Every reply path now refuses one the session does not hold with `concurrent_change` ("answered or changed meanwhile, so nothing was sent"), whether AGL's read finds it gone or the harness refuses it at the send, which the browser and devices receive alike; a malformed answer (an unsupported reply, an id of another harness, an answer of the wrong shape) stays `invalid_request`. In the browser a conversation says so at the composer, drops the answer its card showed and reads the conversation again, with no error journal entry, and the Inbox shows the sentence on the card and lists again. MCP elicitations keep their own refusals (`not_found`).
13
+ - The session, terminal and resource lists appear as soon as the projects load (AGL-1704), no longer after the Deployments, driver, direct report, session feed and Inbox reads: the page load waited for all of them before it listed the conversations, terminals and resources, so one slow read held the whole workspace back.
14
+
3
15
  ## 2026-11-12 - 43.3.2
4
16
 
5
17
  ### Fixes