@ai-ecoverse/slicc-spectrum 1.85.1 → 1.86.1

package/README.md

@@ -147,6 +147,8 @@ The stylesheet (wterm's plus the theme) is constructed once per document and ado
 The bundle loads the WASM with `new URL('./wterm.wasm', import.meta.url)`, so `dist/` works from any path, including from OPFS through the slicc-bios service worker. wterm's base64-inlined copy of the WASM is left out of the bundle.
 TypeScript declarations go to `dist/types/`, and the package's `types` export points at them.
 Set `SliccTerminal.wasmUrl` before the first element connects to load it from elsewhere.
+`dist/swc.css` (exported as `@ai-ecoverse/slicc-spectrum/swc.css`) is the pinned `@adobe/spectrum-wc` stylesheet with its tokens inlined, one file with no `@import`.
+A page that puts a UI element straight into the document, such as a guest's page, links it and wraps the element in `<div class="swc-theme swc-theme--sizeM swc-theme--light">` and `<sp-theme system="spectrum-two">`, as `test/integration/page/guest/` does.
 
 ## wterm notes
 
@@ -859,7 +861,7 @@ Guest seats on a cone.
 Emit `seats` when it changes.
 `mint(agentId, { label, expiresAt, gates })` resolves with the `seat` and its `url`, which the panel shows once and never keeps, and `revoke(id)` ends a seat; both reject with an `Error` whose message is a sentence to show.
 The hub caps `expiresAt` at 30 days.
-`gates` (`{ messages, tools }`) are fixed at mint, so changing them means revoking and minting again; each is a `GuestGate`: `user` (a person with Control approves each one), `cone` (the shared cone itself decides, messages only unless `gates()` offers it for tools), `agent` (the automatic check decides by the owner's intent and asks a person when unsure), `scoop:<name>` (that scoop decides) or `off` (no review: messages go straight in as follow-ups, and tool calls run without review; messages only unless `gates()` offers it for tools).
+`gates` (`{ messages, tools }`) are fixed at mint, so changing them means revoking and minting again; each is a `GuestGate`: `user` (the owner approves each one, from any of their devices, with or without Control; the invite reads "You approve each one" with "Any of your devices can approve, with or without Control."), `cone` (the shared cone itself decides, messages only unless `gates()` offers it for tools), `agent` (the automatic check decides by the owner's intent and asks a person when unsure), `scoop:<name>` (that scoop decides) or `off` (no review: messages go straight in as follow-ups, and tool calls run without review; messages only unless `gates()` offers it for tools).
 The optional `unavailable()` returns a sentence when seats can't be minted here (no tray hub), or `null`; emit `unavailable` with it when it changes.
 The optional `gates()` returns the policy's allowed choices, `{ messages, tools }`, each a list of `GuestGate`s in display order, where `scoop:*` means each of the cone's scoops; the owner can change them, and without it the invite offers the lists above.
 `mint` always gets a concrete gate, never `scoop:*`.

package/dist/slicc-ui.js

@@ -12339,7 +12339,7 @@ var guestExpiries = [
   ["30d", "30 days", 30 * day]
 ];
 var guestNameLimit = 40;
-var approve = "A person with Control approves each one.";
+var approve = "Any of your devices can approve, with or without Control.";
 var defaultGates = {
   messages: ["user", "agent", "cone", "scoop:*", "off"],
   tools: ["user", "agent", "scoop:*"]