@toa.io/extensions.exposition 1.0.0-alpha.272 → 1.0.0-alpha.274

package/CHANGELOG.md

@@ -3,6 +3,217 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [1.0.0-alpha.274](https://github.com/toa-io/toa/compare/v1.0.0-alpha.273...v1.0.0-alpha.274) (2026-09-02)
+
+
+* Configuration is served by a component, followed live, and kept per epoch (#1017) ([b05997d](https://github.com/toa-io/toa/commit/b05997d3adb784f238a222cb46878b23859339a2)), closes [#1017](https://github.com/toa-io/toa/issues/1017)
+
+
+### BREAKING CHANGES
+
+* a secret configuration value is an object, not a string;
+read it with `unwrap()`.
+
+Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
+
+* test(configuration): wait for the second round rather than assume it
+
+Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
+
+* refactor(configuration)!: read a secret with its own unwrap
+
+Component code depends on no Toa package, so a secret is read as
+`context.configuration.apiKey.unwrap()` and the helper in `@toa.io/generic`
+goes. A value a component reads as a secret is therefore given as a reference:
+`identity.basic` no longer defaults `pepper` to `''`, the development context
+and the feature harness give the token keys, the federation client secret and
+the signing key as references, and the harness has a step for the secrets a
+scenario refers to. CONTRIBUTING states the rule.
+* `identity.basic` `pepper` has no default; a value read as a
+secret must be given as a `$NAME` reference.
+
+Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
+
+* feat(configuration): list the configurations
+
+`configuration.values.list` returns every component's configuration for its
+deployed epoch, by component name, and `GET /configuration/values/` serves it
+behind `system:configuration:get`.
+
+Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
+
+* fix(exposition): write a value in YAML the way its toJSON says
+
+A redacted secret in a reply was dumped as an empty object; it is written as
+`<REDACTED>`, as JSON and msgpack already write it.
+
+Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
+
+* test(configuration): a secret is an object, and stays redacted in a reply
+
+A component with `{ a: 1, b: $SECRET_B }` returns its configuration as
+`{ a: 1, b: '<REDACTED>' }` and the secret itself through `unwrap()`. The reply
+step also accepts a reply as a caller across a process boundary receives it,
+since a call within the process hands the object over as it is.
+
+Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
+
+* chore(schemas): bump the dependencies
+
+ajv 8.18.0 to 8.20.0, ajv-formats 2.1.1 to 3.0.1, better-ajv-errors 1.2.0
+to 2.0.3, fast-glob 3.2.12 to 3.3.3 and js-yaml 4.3.1 to 5.4.1 — the version
+exposition already uses. The three majors keep the CommonJS entry points this
+library calls: ajv-formats as a function, better-ajv-errors as .default, and
+js-yaml's load.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+* feat(configuration)!: serve the schema with the value
+
+GET /configuration/values/:component/ answers { configuration, schema, epoch }
+where it answered with the configuration alone, and list carries the schema of
+every component. Nothing reads a configuration without needing to know what it
+is checked against, and the schema was only ever on the values service.
+
+An epoch the deployment does not know has no schema; the value stored for it
+is still returned.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+* feat(configuration): publish a configuration UI
+
+The values service serves a page at /.configuration on port 8003, out of the
+directory ui builds: the configured components, a screen per component showing
+what it holds now, and a dialog creating the next one. Reading needs
+system:configuration:get and creating needs system:configuration:create.
+
+A configuration is immutable, so the dialog opens on the current value and what
+is left out of it is left out of the component. The editor takes YAML, the
+schema is applied before anything is sent, and a secret is a reference the page
+never shows.
+
+The page is always published: the annotation is the per-component values map
+and has nowhere to carry a switch.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+* feat(introspection): link a component to its configuration
+
+A card carrying @toa.io/extensions.configuration reads that extension as a link
+to the configuration UI rather than as a name, and configuration joins the
+namespaces the runtime provides, so its components band under System.
+
+Deployed, both pages sit behind the same ingress and the path alone is right;
+locally each console has its own port.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+* feat(introspection): scroll the map, zoom with a modifier
+
+The map was grabbed to move and zoomed with a bare wheel, which is neither what
+a page does nor what the wheel does anywhere else. A plain scroll now pans on
+both axes and the wheel scales only with the modifier held — a trackpad pinch
+arrives as one of those on every platform.
+
+A card's own scrollable box keeps its wheel, in both paths.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+* refactor(introspection): centre the filter in the header
+
+The sides take equal space, which is what leaves the filter between them.
+Neither side may shrink under what it holds, or the tabs run out from under
+their side and across the filter, and the filter across the sign-out button;
+the title gives way instead.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+* fix(configuration): connect the UI to the values service
+
+The page was declared as a dependency from inside `open`, and a connector connects
+what it depends on before `open` runs — so the server was constructed and never
+listened. Nothing caught it: the UI feature builds the server itself.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+* feat(configuration)!: reserve resources in the annotation
+
+The values service deploys like any other and must state what it may take, but the
+annotation is a map of component ids and had nowhere to put it — so `toa env` failed
+for every context using configuration unless it declared a context-wide `resources`.
+
+`resources` is now the service's own, read the way `introspection` and `realtime` read
+theirs. A component actually named `resources` is written `default.resources`, which is
+what its id is anyway.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+* feat(configuration): follow the system colour scheme
+
+The dark tokens were behind a `.dark` class nothing sets, and the `dark:` variant was
+pointed at that class too — so a component's own dark styling never applied either.
+Both now key off `prefers-color-scheme`, and `color-scheme` hands the native chrome
+the same answer.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+* feat(introspection): follow the system colour scheme
+
+The dark tokens were behind a `.dark` class nothing sets, and the `dark:` variant was
+pointed at that class too — so a component's own dark styling never applied either.
+Both now key off `prefers-color-scheme`, and `color-scheme` hands the native chrome
+the same answer.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+* feat(configuration): present a change as an edit of what is there
+
+A configuration is immutable and creating one replaces the whole of it, but the dialog
+opens on the current value and the page never shows an older one — so what the reader
+does is edit. The words follow: Edit rather than New, Update rather than Create, and
+the paragraph explaining the model goes, along with the field's label, which the title
+above it already said.
+
+The editor also stayed as wide as its longest line — `field-sizing: content` sizes to
+content, and no `max-width` clamps that — so a long value painted outside the dialog.
+It is fixed now, the dialog takes the width the screen has rather than a fixed step,
+and the band held for errors no longer leaves a gap when there are none.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+* feat(configuration): mark a component that keeps a secret
+
+A key after the name on the row, wherever the configuration holds a reference, however
+deep. The predicate reads the same lines the value screen renders, so the two cannot
+disagree about what counts as a secret.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+* feat(configuration): lead back to the list from the title
+
+Every address ends in a slash, so the way up is the address itself on the list and one
+level above it on a component's screen — which holds wherever the page is mounted.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+
+
+
+
+# [1.0.0-alpha.273](https://github.com/toa-io/toa/compare/v1.0.0-alpha.272...v1.0.0-alpha.273) (2026-09-02)
+
+
+### Bug Fixes
+
+* **exposition:** green the feature suite ([67c25ad](https://github.com/toa-io/toa/commit/67c25ad627db3b3779b09405c5a3c319ecd47722))
+* **exposition:** keep a departing tenant from taking a branch back ([64a4eaf](https://github.com/toa-io/toa/commit/64a4eafc9122fabba7b59bf7d559a9d4ef36f773))
+* **exposition:** remove redundant inputs ([34763e4](https://github.com/toa-io/toa/commit/34763e417c93c4eecc5f96879a68c2b68bd6b8a8))
+* **exposition:** report a refreshed branch at trace ([4f170ef](https://github.com/toa-io/toa/commit/4f170ef529a04755b22494789407305f11ce395e))
+
+
+
+
+
 # [1.0.0-alpha.272](https://github.com/toa-io/toa/compare/v1.0.0-alpha.271...v1.0.0-alpha.272) (2026-09-01)
 
 

package/components/exposition.atom/manifest.toa.yaml

@@ -15,5 +15,7 @@ operations:
           type: array
           items:
             type: number
-      required: [keys, deltas]
+      required:
+        - keys
+        - deltas
       additionalProperties: false

package/components/exposition.octets/manifest.toa.yaml

@@ -7,12 +7,21 @@ operations:
   put:
     bindings: ~
     input:
-      storage*: string
-      request*: ~
-      location: string
-      accept: string
-      limit: number
-      trust: ~ # array of strings or regular expressions
+      properties:
+        location:
+          type: string
+        accept:
+          type: string
+        limit:
+          type: number
+        trust: {}
+        storage:
+          type: string
+        request: {}
+      type: object
+      required:
+        - storage
+        - request
     errors:
       - LOCATION_UNTRUSTED
       - LOCATION_LENGTH
@@ -21,9 +30,18 @@ operations:
   get: &simple
     bindings: ~
     input:
-      storage*: string
-      path*: string
-      range: string
-      agent: string
+      properties:
+        range:
+          type: string
+        agent:
+          type: string
+        storage:
+          type: string
+        path:
+          type: string
+      type: object
+      required:
+        - storage
+        - path
   head: *simple
   delete: *simple

package/components/exposition.octets/operations/put.js

@@ -2,7 +2,6 @@
 
 const { Readable } = require('node:stream')
 const { posix } = require('node:path')
-const { Err } = require('error-value')
 const { match } = require('matchacho')
 
 async function put (input, context) {
@@ -122,10 +121,26 @@ function toURL (location) {
   }
 }
 
-const ERR_UNTRUSTED = new Err('LOCATION_UNTRUSTED', 'Location is not trusted')
-const ERR_LENGTH = new Err('LOCATION_LENGTH', 'Content-Length must be 0 when Content-Location is used')
-const ERR_UNAVAILABLE = new Err('LOCATION_UNAVAILABLE', 'Location is not available')
-const ERR_INVALID_ID = new Err('INVALID_ID', 'Invalid Content-ID')
+const ERR_UNTRUSTED = new (class LocationUntrustedError extends Error {
+  code = 'LOCATION_UNTRUSTED'
+  message = 'Location is not trusted'
+})()
+
+const ERR_LENGTH = new (class LocationLengthError extends Error {
+  code = 'LOCATION_LENGTH'
+  message = 'Content-Length must be 0 when Content-Location is used'
+})()
+
+const ERR_UNAVAILABLE = new (class LocationUnavailableError extends Error {
+  code = 'LOCATION_UNAVAILABLE'
+  message = 'Location is not available'
+})()
+
+const ERR_INVALID_ID = new (class InvalidIdError extends Error {
+  code = 'INVALID_ID'
+  message = 'Invalid Content-ID'
+})()
+
 
 const ID_RX = /^[a-zA-Z0-9-_]{1,32}$/
 

package/components/identity.bans/manifest.toa.yaml

@@ -3,19 +3,38 @@ name: bans
 
 entity:
   schema:
-    banned*: false
-    originator*: string
-    comment: string
+    properties:
+      comment:
+        type: string
+      banned:
+        type: boolean
+        default: false
+      originator:
+        type: string
+    type: object
+    required:
+      - banned
+      - originator
   associated: true
 
 operations:
   transit:
     concurrency: retry
     input:
-      banned*: boolean
-      originator*:
-        id: string
-      comment: string
+      properties:
+        comment:
+          type: string
+        banned:
+          type: boolean
+        originator:
+          properties:
+            id:
+              type: string
+          type: object
+      type: object
+      required:
+        - banned
+        - originator
 
 exposition:
   isolated: true