copilotz 1.0.0-rc.34 → 1.0.0-rc.36

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.
package/CHANGELOG.md CHANGED
@@ -1,3 +1,41 @@
1
+ ## 1.0.0-rc.36 — 2026-11-10
2
+
3
+ **Upgrading.** Chat has two tools of its own, `list_conversations` and `read_conversation`, for the
4
+ agents that list them in their `tools`. An app that made its own tools under those names drops them
5
+ and lists chat's, which do the same and take a space. A Personal space's agents now write elsewhere
6
+ for their person without labels from there (below): an app that relied on that refusal says so in
7
+ its own rules.
8
+
9
+ - **Agents work under the authority of whoever asked** ([design](design/work.md), "Authority"). In a
10
+ person's own Personal space, where only they read the answers, their agents reach every space they
11
+ do, and now act there too. That makes the Personal chat a chief of staff:
12
+ - **Tools take a space** (`in`, its id, which the `elsewhere` context lists): `list_conversations`
13
+ and `read_conversation` (new, chat's own), boards (`list_boards`, `read_board`, `create_board`,
14
+ `create_card`, `update_card`, `move_card`), documents (`list_documents`, `read_document`,
15
+ `write_document`, `append_document`, `edit_document`), routines (`schedule_routine`,
16
+ `list_routines`, `cancel_routine`: a routine kept elsewhere starts a new conversation there each
17
+ run) and `recall`, as before. From a shared space they work only there and in what it draws on,
18
+ and say so (`workIn`, in the agents' contract, for apps' tools).
19
+ - **`send_message` takes `thread`:** a conversation that's there already, in this space or any
20
+ other the person can write in. Who answers there gets it (`to`, or the conversation's own
21
+ agent), it says where it came from, and the answer comes back, as a hand-over's does.
22
+ - **What they write elsewhere is the person's:** work for someone from their own Personal space
23
+ takes no labels from there (`labels.write`, `ownPersonal`). Before, everything an agent wrote
24
+ from Personal into a space others see was refused (`needs_share`), even a card the person asked
25
+ for. What's written in the Personal space itself keeps its marks (its conversation may move),
26
+ and labels guard shared spaces and contacts' chats as before.
27
+
28
+ ## 1.0.0-rc.35 — 2026-11-09
29
+
30
+ **Fixed: a retried call's nested calls.** A call run again under its id (a retry after a failure or
31
+ a stop) looked up its own nested recorded calls without its actor. In a person's or contact's job
32
+ the runtime then refused the lookup ("This job can't act as that"), and the retry failed. It now
33
+ asks as whom the call works for. This affected any person or contact Action retried after it made a
34
+ nested recorded call, and retried Processor deliveries; it has been so since the authority checks.
35
+
36
+ The MCP line's tests now wait for what they assert rather than for fixed times (they flaked on macOS
37
+ runners). Nothing to do when upgrading from rc.34.
38
+
1
39
  ## 1.0.0-rc.34 — 2026-11-09
2
40
 
3
41
  rc.33, released whole. rc.33's publish stopped before npm: packing its tarballs, npm took `dist/npm`