Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

worker: persist known-worker control grants

Browse Source
This commit is contained in:
Hare
2026-08-16 23:08:32 +09:00
parent 46a44b232b
commit f41ab0e277
7 changed files with 1082 additions and 212 deletions
Download Patch File Download Diff File Expand all files Collapse all files
resources/profiles/base.dcdl
+1 -1
View File
@@ -27,7 +27,7 @@ feature = {
web = { enabled = true; };
image = { enabled = true; };
sub_worker = { enabled = true; };
worker = { enabled = false; };
worker = { enabled = true; };
objective = { enabled = true; };
ticket = { enabled = true; authoring = true; thread = true; };
};
resources/prompts/common/worker-observation.md
+1 -1
View File
@@ -2,7 +2,7 @@
Worker-session tools are a read-only exploration surface over host-granted active Worker sessions.
- Use `ListWorkerSessions` to discover only the sessions already granted to you. Reuse the returned structured `subject` exactly: Runtime peers use `{ kind: "runtime_worker", runtime_id, worker_id }`, while parent-owned children use `{ kind: "sub_worker", name }`. Do not guess subject identifiers.
- Use `WorkerList` to discover known Workers and reuse its returned structured `subject` exactly. Runtime Workers use `{ kind: "runtime_worker", runtime_id, worker_id }`, while parent-owned children use `{ kind: "sub_worker", name }`. Do not guess subject identifiers.
- Use `ViewSessionOverview` for sparse orientation, `SearchSessionEntries` for bounded range/filter queries, and `ReadSessionEntry` for one bounded entry.
- `SessionEntryRef` is the common entry identity across overview, search, reads, and evidence conversion. Reuse returned `E...` values; never invent them.
- Every operation rereads the latest committed capture. Existing references remain stable when entries append.