@toa.io/extensions.exposition 1.0.0-alpha.284 → 1.0.0-alpha.286

package/features/etag.feature

@@ -24,7 +24,6 @@ Feature: Optimistic concurrency control
     Then the following reply is sent:
       """
       201 Created
-      etag: "1"
 
       id: ${{ id }}
       """
@@ -74,88 +73,6 @@ Feature: Optimistic concurrency control
     Then the following reply is sent:
       """
       200 OK
-      etag: "2"
-      """
-
-  Scenario: Using etag with enumeration
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          io:output: true
-          GET: enumerate
-      """
-    # sorted and bounded, or the collection does not enumerate the same way twice
-    When the following request is received:
-      """
-      GET /pots/?sort=id:asc&limit=2 HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      etag: "${{ etag }}"
-      """
-    # the same representation must be asked for, the tag identifies it
-    When the following request is received:
-      """
-      GET /pots/?sort=id:asc&limit=2 HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      if-none-match: "${{ etag }}"
-      """
-    Then the following reply is sent:
-      """
-      304 Not Modified
-      etag: "${{ etag }}"
-      """
-
-  Scenario: `etag` of a reply that carries no version
-    Given the `echo` is running with the following manifest:
-      """yaml
-      exposition:
-        /:name:
-          io:output: true
-          GET: compute
-      """
-    When the following request is received:
-      """
-      GET /echo/Bob/ HTTP/1.1
-      host: nex.toa.io
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      etag: "2d6a12ffc0a952fbd09f8909de4e0e4b20ba2b906cd12ac22bbef4ee5bd9003e"
-
-      Hello Bob
-      """
-    When the following request is received:
-      """
-      GET /echo/Bob/ HTTP/1.1
-      host: nex.toa.io
-      accept: text/plain
-      if-none-match: "2d6a12ffc0a952fbd09f8909de4e0e4b20ba2b906cd12ac22bbef4ee5bd9003e"
-      """
-    Then the following reply is sent:
-      """
-      304 Not Modified
-      etag: "2d6a12ffc0a952fbd09f8909de4e0e4b20ba2b906cd12ac22bbef4ee5bd9003e"
-      """
-    # the tag identifies the representation, which is what `vary: accept` says
-    When the following request is received:
-      """
-      GET /echo/Bob/ HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      if-none-match: "2d6a12ffc0a952fbd09f8909de4e0e4b20ba2b906cd12ac22bbef4ee5bd9003e"
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      etag: "360c52c694c418b4a793a4815e611206ab17fe04836351a65638a15d1491810b"
       """
 
   Scenario: Weak `etag`
@@ -182,7 +99,6 @@ Feature: Optimistic concurrency control
     Then the following reply is sent:
       """
       201 Created
-      etag: "1"
 
       id: ${{ id }}
       """
@@ -232,7 +148,6 @@ Feature: Optimistic concurrency control
     Then the following reply is sent:
       """
       200 OK
-      etag: "2"
       """
 
   Scenario: Hash `if-none-match` on versioned resource
@@ -258,7 +173,6 @@ Feature: Optimistic concurrency control
     Then the following reply is sent:
       """
       201 Created
-      etag: "1"
 
       id: ${{ id }}
       """

package/features/identity.bans.feature

@@ -5,9 +5,9 @@ Feature: Bans
     Given the `identity.basic` database contains:
     # developer:secret
     # user:12345
-      | _id                              | authority | username  | password                                                     | _deleted |
-      | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O | null     |
-      | e8e4f9c2a68d419b861403d71fabc915 | nex       | user      | $2b$10$Frszmrmsz9iwSXzBbRRMKeDVKsNxozkrLNSsN.SnVC.KPxLtQr/bK | null     |
+      | _id                              | authority | username  | password                                                     | DELETED |
+      | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O | null    |
+      | e8e4f9c2a68d419b861403d71fabc915 | nex       | user      | $2b$10$Frszmrmsz9iwSXzBbRRMKeDVKsNxozkrLNSsN.SnVC.KPxLtQr/bK | null    |
     And the `identity.bans` database is empty
 
   Scenario: Banning an Identity

package/features/identity.basic.feature

@@ -132,8 +132,8 @@ Feature: Basic authentication
               access: granted!
       """
     And the `identity.basic` database contains:
-      | _id                              | _version | authority | username  | password                                                     |
-      | efe3a65ebbee47ed95a73edd911ea328 | 1        | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
+      | _id                              | VERSION | authority | username  | password                                                     |
+      | efe3a65ebbee47ed95a73edd911ea328 | 1       | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
     When the following request is received:
       """
       PATCH /identity/basic/efe3a65ebbee47ed95a73edd911ea328/ HTTP/1.1
@@ -173,9 +173,9 @@ Feature: Basic authentication
 
   Scenario: Changing other identity's password
     Given the `identity.basic` database contains:
-      | _id                              | authority | username  | password                                                     | _version |
-      | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O | 1        |
-      | 6c0be50cbfb043acafe69cc7d3895f84 | nex       | attacker  | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O | 1        |
+      | _id                              | authority | username  | password                                                     | VERSION |
+      | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O | 1       |
+      | 6c0be50cbfb043acafe69cc7d3895f84 | nex       | attacker  | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O | 1       |
     When the following request is received:
       """
       PATCH /identity/basic/efe3a65ebbee47ed95a73edd911ea328/ HTTP/1.1
@@ -222,8 +222,8 @@ Feature: Basic authentication
         - ^[^A]{1,16}$  # should not contain 'A'
       """
     And the `identity.basic` database contains:
-      | _id                              | _version | authority | username  | password                                                     |
-      | efe3a65ebbee47ed95a73edd911ea328 | 1        | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
+      | _id                              | VERSION | authority | username  | password                                                     |
+      | efe3a65ebbee47ed95a73edd911ea328 | 1       | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
     When the following request is received:
       """
       PATCH /identity/basic/efe3a65ebbee47ed95a73edd911ea328/ HTTP/1.1
@@ -508,8 +508,8 @@ Feature: Basic authentication
 
   Scenario: Check if username is available
     Given the `identity.basic` database contains:
-      | _id                              | authority | username  | password                                                     | _version |
-      | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O | 1        |
+      | _id                              | authority | username  | password                                                     | VERSION |
+      | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O | 1       |
     When the following request is received:
       """
       GET /identity/basic/usernames/ZGV2ZWxvcGVy/ HTTP/1.1

package/features/identity.federation.feature

@@ -9,7 +9,7 @@ Feature: Identity Federation
     Given the `identity.federation` configuration:
       """yaml
       trust:
-        - iss: http://localhost:44444
+        - iss: http://localhost:31005
           aud: test
       """
     And the IDP token for User is issued
@@ -68,14 +68,14 @@ Feature: Identity Federation
       200 OK
 
       - id: ${{ User.credential }}
-        iss: http://localhost:44444
+        iss: http://localhost:31005
       """
 
   Scenario: Creating an Identity using inception
     Given the `identity.federation` configuration:
       """yaml
       trust:
-        - iss: http://localhost:44444
+        - iss: http://localhost:31005
           aud: test
       assert: false
       """
@@ -150,7 +150,7 @@ Feature: Identity Federation
       200 OK
 
       - id: ${{ Bill.credential }}
-        iss: http://localhost:44444
+        iss: http://localhost:31005
       """
     And the following request is received:
       # same credentials
@@ -171,11 +171,11 @@ Feature: Identity Federation
     Given the `identity.federation` configuration:
       """yaml
       trust:
-        - iss: http://localhost:44444
+        - iss: http://localhost:31005
           aud: test
       principal:
         authority: nex
-        iss: http://localhost:44444
+        iss: http://localhost:31005
         sub: root
       """
     And the IDP token for root is issued
@@ -218,7 +218,7 @@ Feature: Identity Federation
     Given the `identity.federation` configuration:
       """yaml
       trust:
-        - iss: http://localhost:44444
+        - iss: http://localhost:31005
           aud: test
       """
     And the `identity.basic` database is empty
@@ -260,7 +260,7 @@ Feature: Identity Federation
       201 Created
 
       id: ${{ Bob.credential }}
-      iss: http://localhost:44444
+      iss: http://localhost:31005
       """
     # the created credential is listed as is
     When the following request is received:
@@ -275,7 +275,7 @@ Feature: Identity Federation
       200 OK
 
       - id: ${{ Bob.credential }}
-        iss: http://localhost:44444
+        iss: http://localhost:31005
       """
     And the following request is received:
       """
@@ -335,7 +335,7 @@ Feature: Identity Federation
     Given the `identity.federation` configuration:
       """yaml
       trust:
-        - iss: http://localhost:44444
+        - iss: http://localhost:31005
           aud: nex
           secret: $IDP_SECRET
       """
@@ -363,7 +363,7 @@ Feature: Identity Federation
     Given the `identity.federation` configuration:
       """yaml
       trust:
-        - iss: http://localhost:44444
+        - iss: http://localhost:31005
           aud: nex
           signature:
             iss: io.toa.nex.id

package/features/identity.tokens.custom.feature

@@ -82,8 +82,8 @@ Feature: Custom tokens
       | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
       | e8e4f9c2a68d419b861403d71fabc915 | nex       | user      | $2b$10$Frszmrmsz9iwSXzBbRRMKeDVKsNxozkrLNSsN.SnVC.KPxLtQr/bK |
     And the `identity.roles` database contains:
-      | _id                              | identity                         | role                      |
-      | 9c4702490ff84f2a9e1b1da2ab64bdd4 | efe3a65ebbee47ed95a73edd911ea328 | system:identity:tokens    |
+      | _id                              | identity                         | role                   |
+      | 9c4702490ff84f2a9e1b1da2ab64bdd4 | efe3a65ebbee47ed95a73edd911ea328 | system:identity:tokens |
     When the following request is received:
       """
       POST /identity/tokens/e8e4f9c2a68d419b861403d71fabc915/ HTTP/1.1
@@ -258,7 +258,7 @@ Feature: Custom tokens
       200 OK
 
       - id: ${{ kid }}
-        _created: ${{ created }}
+        CREATED: ${{ created }}
         label: One-time token
         expires: ${{ expires }}
       """
@@ -369,8 +369,8 @@ Feature: Custom tokens
 
   Scenario: Changing the password revokes custom tokens
     Given the `identity.basic` database contains:
-      | _id                              | _version | authority | username  | password                                                     |
-      | efe3a65ebbee47ed95a73edd911ea328 | 1        | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
+      | _id                              | VERSION | authority | username  | password                                                     |
+      | efe3a65ebbee47ed95a73edd911ea328 | 1       | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
     And the `identity.tokens` configuration:
       """yaml
       cache:

package/features/identity.tokens.feature

@@ -92,8 +92,8 @@ Feature: Tokens lifecycle
       refresh: 1
       """
     And the `identity.basic` database contains:
-      | _id                              | _version | authority | username  | password                                                     |
-      | efe3a65ebbee47ed95a73edd911ea328 | 1        | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
+      | _id                              | VERSION | authority | username  | password                                                     |
+      | efe3a65ebbee47ed95a73edd911ea328 | 1       | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
     When the following request is received:
       """
       GET /efe3a65ebbee47ed95a73edd911ea328/ HTTP/1.1

package/features/interruptions.feature

@@ -1,3 +1,4 @@
+@timing
 Feature: Request interruptions
 
   Scenario: Connection reset while processing a request

package/features/introspection.map.feature

@@ -20,8 +20,8 @@ Feature: Reading the introspection map
 
   Scenario: Reading the nodes
     Given the `introspection.nodes` database contains:
-      | _id                              | namespace | component | version  | _version | _deleted |
-      | 70e1a6551346c6932657cdb2526df0fa | pots      | tea       | 7bb04bba | 1        | null     |
+      | _id                              | namespace | component | version  | VERSION | DELETED |
+      | 70e1a6551346c6932657cdb2526df0fa | pots      | tea       | 7bb04bba | 1       | null    |
     When the following request is received:
       """
       GET /introspection/nodes/ HTTP/1.1
@@ -42,8 +42,8 @@ Feature: Reading the introspection map
 
   Scenario: Reading one node
     Given the `introspection.nodes` database contains:
-      | _id                              | namespace | component | version  | _version | _deleted |
-      | 70e1a6551346c6932657cdb2526df0fa | pots      | tea       | 7bb04bba | 1        | null     |
+      | _id                              | namespace | component | version  | VERSION | DELETED |
+      | 70e1a6551346c6932657cdb2526df0fa | pots      | tea       | 7bb04bba | 1       | null    |
     When the following request is received:
       """
       GET /introspection/nodes/70e1a6551346c6932657cdb2526df0fa/ HTTP/1.1

package/features/io.throttle.feature

@@ -1,3 +1,4 @@
+@timing
 Feature: Request throttling
 
   Scenario: Throttle requests to a path

package/features/map.feature

@@ -234,7 +234,7 @@ Feature: HTTP context mapping
     And the `identity.federation` configuration:
       """yaml
       trust:
-        - iss: http://localhost:44444
+        - iss: http://localhost:31005
           aud: test
       """
     And the `echo` is running with the following manifest:
@@ -269,7 +269,7 @@ Feature: HTTP context mapping
     And the `identity.federation` configuration:
       """yaml
       trust:
-        - iss: http://localhost:44444
+        - iss: http://localhost:31005
           aud: test
       assert: false
       """

package/features/mcp.feature

@@ -8,7 +8,8 @@ Feature: Model Context Protocol
   says.
 
   What a tool is, is stated on the route and nowhere else. The operation states what it is
-  too, and that is not this: one operation mounted on two routes is two tools.
+  too, and that is not this: one operation mounted on two routes is two tools. A `title`
+  beside the description is what a person is shown where a client lists what it may call.
 
   Two revisions are answered from one endpoint that remembers nothing between requests: the
   modern one, where every request carries its own version and capabilities, and the one
@@ -42,7 +43,9 @@ Feature: Model Context Protocol
             GET:
               query:
                 criteria: volume>=100
-              mcp:tool: The pots that hold a hundred or more, newest first.
+              mcp:tool:
+                title: Large pots
+                description: The pots that hold a hundred or more, newest first.
               endpoint: enumerate
           /unpublished:
             GET: enumerate
@@ -160,7 +163,7 @@ Feature: Model Context Protocol
       id: 2
       result:
         tools:
-          - name: pots/GET
+          - name: pots.GET
             description: All the pots, newest first.
             inputSchema:
               type: object
@@ -178,7 +181,7 @@ Feature: Model Context Protocol
               additionalProperties: false
             annotations:
               readOnlyHint: true
-          - name: pots/POST
+          - name: pots.POST
             description: Start a new pot brewing.
             inputSchema:
               type: object
@@ -192,7 +195,7 @@ Feature: Model Context Protocol
                 - title
                 - volume
               additionalProperties: false
-          - name: pots/_id/GET
+          - name: pots._id.GET
             description: One pot, by its id.
             inputSchema:
               type: object
@@ -202,7 +205,8 @@ Feature: Model Context Protocol
               required:
                 - id
               additionalProperties: false
-          - name: pots/large/GET
+          - name: pots.large.GET
+            title: Large pots
             description: The pots that hold a hundred or more, newest first.
             annotations:
               readOnlyHint: true
@@ -212,11 +216,11 @@ Feature: Model Context Protocol
       """
     And the reply does not contain:
       """
-      pots/guarded/GET
+      pots.guarded.GET
       """
     And the reply does not contain:
       """
-      pots/unpublished/GET
+      pots.unpublished.GET
       """
     And the reply does not contain:
       """
@@ -235,10 +239,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: pots/unpublished/GET
+      mcp-name: pots.unpublished.GET
 
       {"jsonrpc": "2.0", "id": 30, "method": "tools/call",
-       "params": {"name": "pots/unpublished/GET", "arguments": {},
+       "params": {"name": "pots.unpublished.GET", "arguments": {},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """
@@ -283,7 +287,7 @@ Feature: Model Context Protocol
       id: 20
       result:
         tools:
-          - name: pots/GET
+          - name: pots.GET
       """
 
   Scenario: A tool takes what the procedure takes
@@ -295,10 +299,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: pots/_id/GET
+      mcp-name: pots._id.GET
 
       {"jsonrpc": "2.0", "id": 3, "method": "tools/call",
-       "params": {"name": "pots/_id/GET",
+       "params": {"name": "pots._id.GET",
                   "arguments": {"id": "4c4759e6f9c74da989d64511df42d6f4"},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
@@ -326,10 +330,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: pots/POST
+      mcp-name: pots.POST
 
       {"jsonrpc": "2.0", "id": 4, "method": "tools/call",
-       "params": {"name": "pots/POST", "arguments": {"title": "Kettle", "volume": 1.7},
+       "params": {"name": "pots.POST", "arguments": {"title": "Kettle", "volume": 1.7},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """
@@ -354,10 +358,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: kettles/GET
+      mcp-name: kettles.GET
 
       {"jsonrpc": "2.0", "id": 5, "method": "tools/call",
-       "params": {"name": "kettles/GET", "arguments": {},
+       "params": {"name": "kettles.GET", "arguments": {},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """
@@ -403,10 +407,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: pots/GET
+      mcp-name: pots.GET
 
       {"jsonrpc": "2.0", "id": 7, "method": "tools/call",
-       "params": {"name": "pots/POST", "arguments": {},
+       "params": {"name": "pots.POST", "arguments": {},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """
@@ -484,7 +488,7 @@ Feature: Model Context Protocol
     named a record that is not the caller's, which it may correct itself by naming another.
     A challenge here would send the client to ask for a scope that would not help.
 
-    # developer:secret, who is not an `admin` and so may not reach `pots/guarded/GET`
+    # developer:secret, who is not an `admin` and so may not reach `pots.guarded.GET`
     Given the `identity.basic` database contains:
       | _id                              | authority | username  | password                                                     |
       | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
@@ -498,10 +502,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: pots/guarded/GET
+      mcp-name: pots.guarded.GET
 
       {"jsonrpc": "2.0", "id": 31, "method": "tools/call",
-       "params": {"name": "pots/guarded/GET", "arguments": {},
+       "params": {"name": "pots.guarded.GET", "arguments": {},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """
@@ -531,10 +535,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: pots/_id/GET
+      mcp-name: pots._id.GET
 
       {"jsonrpc": "2.0", "id": 32, "method": "tools/call",
-       "params": {"name": "pots/_id/GET",
+       "params": {"name": "pots._id.GET",
                   "arguments": {"id": "not-an-id"},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
@@ -570,10 +574,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: echo/GET
+      mcp-name: echo.GET
 
       {"jsonrpc": "2.0", "id": 10, "method": "tools/call",
-       "params": {"name": "echo/GET", "arguments": {},
+       "params": {"name": "echo.GET", "arguments": {},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """
@@ -612,10 +616,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: echo/GET
+      mcp-name: echo.GET
 
       {"jsonrpc": "2.0", "id": 11, "method": "tools/call",
-       "params": {"name": "echo/GET", "arguments": {"greeting": "hello"},
+       "params": {"name": "echo.GET", "arguments": {"greeting": "hello"},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """

package/features/oauth.grants.feature

@@ -119,7 +119,7 @@ Feature: Authorization code flow
       id: 1
       result:
         tools:
-          - name: pots/GET
+          - name: pots.GET
       """
 
   Scenario: A code is spent once

package/features/octets.cloudinary.feature

@@ -1,4 +1,4 @@
-@cloudinary
+@manual @cloudinary
 Feature: Octets with Cloudinary storage
 
   Background:

package/features/octets.download.feature

@@ -1,3 +1,4 @@
+@network
 Feature: Download external resources
 
   Scenario Outline: Download from trusted location defined as <type>

package/features/require.feature

@@ -27,7 +27,6 @@ Feature: Request requirements
     Then the following reply is sent:
       """
       201 Created
-      etag: "${{ etag }}"
 
       id: ${{ id }}
       """
@@ -53,7 +52,7 @@ Feature: Request requirements
       host: nex.toa.io
       content-type: application/yaml
       accept: text/plain
-      if-match: "${{ etag }}"
+      if-match: "1"
 
       title: Bye
       """