katalyst-plugin-context 0.2.1a5__tar.gz → 0.2.1a7__tar.gz

{katalyst_plugin_context-0.2.1a5 → katalyst_plugin_context-0.2.1a7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: katalyst-plugin-context
-Version: 0.2.1a5
+Version: 0.2.1a7
 Summary: Katalyst context plugin — the right context from the taxonomy for an agent working on a node
 Author: eSimplicity
 License: Proprietary

{katalyst_plugin_context-0.2.1a5 → katalyst_plugin_context-0.2.1a7}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "katalyst-plugin-context"
-version = "0.2.1a5"
+version = "0.2.1a7"
 description = "Katalyst context plugin — the right context from the taxonomy for an agent working on a node"
 license = { text = "Proprietary" }
 requires-python = ">=3.12"

katalyst_plugin_context-0.2.1a7/xspec/.gitignore

@@ -0,0 +1,8 @@
+node_modules
+.features-gen
+playwright-report
+test-results
+cucumber-report
+storage
+.env
+blob-report

katalyst_plugin_context-0.2.1a7/xspec/features/cli/52_kata_context.feature

@@ -0,0 +1,274 @@
+@cli @area-context
+Feature: Kata CLI - Context: what an agent working on a node gets
+  As an agent about to change a node
+  I want one call that returns the decisions and rules around it
+  So that I meet a rule the node inherits from a parent, not only the ones in its own file
+
+  # docs/plugins/context/index.md, against the neutral service catalogue of examples/catalogue
+  # (installed as docs/user-guide/getting-started.md installs it) with a small payments model:
+  #
+  #   area payments            governed by use-postgres, follows the mandatory rule encrypt-card-data
+  #   service payments.checkout   governed by async-events
+  #   component payments.checkout.web-api   follows the recommended rule log-correlation-id,
+  #                                          uses the package httpx (governed by pin-httpx)
+  #   check scan-for-card-numbers, under encrypt-card-data
+  #
+  # The catalogue declares one view, `governance`, that every `component` always includes, and
+  # a second, `package-decisions`, that the caller must ask for. `severity: mandatory` blocks.
+
+  Background:
+    Given the payments catalogue is installed
+
+  # ─────────────────────────────────────────────────────────────
+  # The map
+  # ─────────────────────────────────────────────────────────────
+
+  @smoke
+  Scenario: The map shows the ancestors, the relationships, the views and what can be asked next
+    When I run "kata tax context filesystem:payments.checkout.web-api --map"
+    Then the command should succeed
+    And the output should contain "# Context: component `filesystem:payments.checkout.web-api`"
+    And the output should contain "Ancestors: service `filesystem:payments.checkout` ← area `filesystem:payments`"
+    And the output should contain "- `USES_PACKAGE:out` → package ×1"
+    And the output should contain "- `GOVERNED_BY:out` → decision ×1 — inherited from `filesystem:payments.checkout`"
+    And the output should contain "- `FOLLOWS_RULE:out` → rule ×1 — inherited from `filesystem:payments`"
+    And the output should contain "- **governance** (always included): Governing decisions and rules — 5 item(s)"
+    And the output should contain "- **package-decisions**: Decisions on the packages it uses — 1 item(s)"
+    And the output should contain "## Always included"
+
+  Scenario: The map in JSON marks the always-included view and says what policy allows
+    When I run "kata tax context filesystem:payments.checkout.web-api --map --format json"
+    Then the command should succeed
+    And the JSON output at "$.node.qualifiedName" should equal "filesystem:payments.checkout.web-api"
+    And the JSON output at "$.ancestors[*].qualifiedName" should contain "filesystem:payments.checkout"
+    And the JSON output at "$.ancestors[*].qualifiedName" should contain "filesystem:payments"
+    And the JSON output at "$.views[?(@.name=='governance')].always" should equal "true"
+    And the JSON output at "$.views[?(@.name=='package-decisions')].always" should equal "false"
+    And the JSON output at "$.always.items[*]" should have 5 items
+    And the JSON output at "$.options.steps" should contain "USES_PACKAGE:out"
+    And the JSON output at "$.options.detail" should contain "full"
+    And the JSON output at "$.options.maxDepth" should equal "4"
+
+  # ─────────────────────────────────────────────────────────────
+  # A default call: the always-included view, blocking items first
+  # ─────────────────────────────────────────────────────────────
+
+  @smoke
+  Scenario: A call with no path and no view returns the always-included view, the mandatory rule first
+    When I run "kata tax context filesystem:payments.checkout.web-api"
+    Then the command should succeed
+    And the output should contain "## Governing decisions and rules"
+    And the output should contain "⛔ blocking · **Encrypt card data** `filesystem:encrypt-card-data` · severity: mandatory"
+    And the output should contain "_advisory_ · **Log a correlation id** `filesystem:log-correlation-id` · severity: recommended"
+    And the output should contain "why: area filesystem:payments ─FOLLOWS_RULE→ (inherited)"
+    And the output should list "Encrypt card data" before "Log a correlation id"
+    And the output should list "Encrypt card data" before "Publish events, do not call"
+    And the output should not contain "Pin httpx"
+    And the output should contain "nothing narrowed"
+
+  Scenario: The same call in JSON marks the blocking item and where it was inherited from
+    When I run "kata tax context filesystem:payments.checkout.web-api --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[*]" should have 5 items
+    And the JSON output at "$.items[0].qualifiedName" should equal "filesystem:encrypt-card-data"
+    And the JSON output at "$.items[0].blocking.blocking" should equal "true"
+    And the JSON output at "$.items[0].inheritedFrom" should equal "filesystem:payments"
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:log-correlation-id')].blocking.blocking" should equal "false"
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:log-correlation-id')].inheritedFrom" should be null
+    And the JSON output at "$.items[*].view" should not contain "package-decisions"
+    And the JSON output at "$.effective.always" should contain "governance"
+    And the JSON output at "$.truncated" should be null
+
+  # ─────────────────────────────────────────────────────────────
+  # #290: naming a view or a path still holds the always-included views
+  # ─────────────────────────────────────────────────────────────
+
+  Scenario: Asking for one view still returns the always-included view first
+    When I run "kata tax context filesystem:payments.checkout.web-api --view package-decisions"
+    Then the command should succeed
+    And the output should contain "## Governing decisions and rules  _(view: governance)_"
+    And the output should contain "## Decisions on the packages it uses  _(view: package-decisions)_"
+    And the output should contain "⛔ blocking · **Encrypt card data**"
+    And the output should contain "`filesystem:pin-httpx`"
+    And the output should list "view: governance" before "view: package-decisions"
+
+  Scenario: Asking for one view in JSON returns the mandatory rule and the view's own item
+    When I run "kata tax context filesystem:payments.checkout.web-api --view package-decisions --format json"
+    Then the command should succeed
+    And the JSON output at "$.effective.views" should contain "governance"
+    And the JSON output at "$.effective.views" should contain "package-decisions"
+    And the JSON output at "$.effective.always" should contain "governance"
+    And the JSON output at "$.items[*].qualifiedName" should contain "filesystem:encrypt-card-data"
+    And the JSON output at "$.items[?(@.view=='package-decisions')]" should have 1 item
+    And the JSON output at "$.items[?(@.view=='package-decisions')].qualifiedName" should contain "filesystem:pin-httpx"
+
+  Scenario: Asking for a path still returns the always-included view
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[*].qualifiedName" should contain "filesystem:encrypt-card-data"
+    And the JSON output at "$.items[*].qualifiedName" should contain "filesystem:httpx"
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:httpx')].path" should equal "USES_PACKAGE:out"
+
+  # ─────────────────────────────────────────────────────────────
+  # Detail and depth
+  # ─────────────────────────────────────────────────────────────
+
+  Scenario: The detail level decides how much of an item is shown
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out --detail refs --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:httpx')].detail" should equal "refs"
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out --detail summary"
+    Then the command should succeed
+    And the output should contain "- **httpx** `filesystem:httpx` · version: 0.27"
+    And the output should contain "HTTP client"
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out --detail full --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:httpx')].detail" should equal "full"
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:httpx')].spec.version" should equal "0.27"
+
+  Scenario: The always-included view keeps its own detail when the request asks for more
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out --detail full --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:encrypt-card-data')].detail" should equal "summary"
+
+  Scenario: The depth is how many times a single-step path is followed
+    When I run "kata tax context filesystem:payments.checkout.web-api --path CHILD_OF:out --no-inherit --depth 1 --detail refs --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[?(@.path=='CHILD_OF:out')].qualifiedName" should contain "filesystem:payments.checkout"
+    And the JSON output at "$.items[?(@.path=='CHILD_OF:out')].qualifiedName" should not contain "filesystem:payments"
+    When I run "kata tax context filesystem:payments.checkout.web-api --path CHILD_OF:out --no-inherit --depth 2 --detail refs --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[?(@.path=='CHILD_OF:out')].qualifiedName" should contain "filesystem:payments.checkout"
+    And the JSON output at "$.items[?(@.path=='CHILD_OF:out')].qualifiedName" should contain "filesystem:payments"
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:payments' && @.path=='CHILD_OF:out')].depth" should equal "2"
+
+  # katalyst-taxonomy#303: a path that names CHILD_OF returns the ancestors with the default
+  # inheritance too; the map's `CHILD_OF:out → service ×1` row is no dead path.
+  Scenario: A path that names the parent relationship returns the ancestors with inheritance on
+    When I run "kata tax context filesystem:payments.checkout.web-api --path CHILD_OF:out --depth 2 --detail refs --format json"
+    Then the command should succeed
+    And the JSON output at "$.effective.inherit" should equal "true"
+    And the JSON output at "$.items[?(@.path=='CHILD_OF:out')].qualifiedName" should contain "filesystem:payments.checkout"
+    And the JSON output at "$.items[?(@.path=='CHILD_OF:out')].qualifiedName" should contain "filesystem:payments"
+    When I run "kata tax context filesystem:payments.checkout.web-api --path '*:out' --detail refs --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[?(@.path=='*:out')].qualifiedName" should not contain "filesystem:payments.checkout"
+
+  Scenario: A depth above the built-in limit is lowered, and the answer says so
+    When I run "kata tax context filesystem:payments.checkout.web-api --path CHILD_OF:out --no-inherit --depth 9 --format json"
+    Then the command should succeed
+    And the JSON output at "$.effective.depth" should equal "4"
+    And the JSON output at "$.policy.clamped[?(@.control=='depth')].requested" should equal "9"
+    And the JSON output at "$.policy.clamped[?(@.control=='depth')].limitedBy" should equal "builtin"
+    When I run "kata tax context filesystem:payments.checkout.web-api --path CHILD_OF:out --no-inherit --depth 9"
+    Then the command should succeed
+    And the output should contain "- depth: asked 9, got 4 (builtin)"
+
+  Scenario: A detail level or step that is not allowed is refused before any reading
+    When I run "kata tax context filesystem:payments.checkout.web-api --detail huge"
+    Then the command should fail
+    And the exit code should be 2
+
+  # ─────────────────────────────────────────────────────────────
+  # Naming the node: FQTN ambiguity
+  # ─────────────────────────────────────────────────────────────
+
+  Scenario: An FQTN that two kinds share is refused, with the names that disambiguate it
+    When I run "kata tax create rule payments --set title=Payments --set severity=recommended -d 'A rule that is also called payments.'"
+    Then the command should succeed
+    When I run "kata tax context filesystem:payments"
+    Then the command should fail
+    And the output should contain "'filesystem:payments' names more than one node; use one of: filesystem:payments#area, filesystem:payments#rule"
+    When I run "kata tax context filesystem:payments#rule"
+    Then the command should succeed
+    And the output should contain "# Context: rule `filesystem:payments#rule`"
+    When I run "kata tax context filesystem:payments#area --map"
+    Then the command should succeed
+    And the output should contain "# Context: area `filesystem:payments#area`"
+
+  Scenario: A node that shares its name with another kind walks its own relationships
+    When I run "kata tax create rule payments --set title=Payments --set severity=recommended -d 'A rule that is also called payments.'"
+    Then the command should succeed
+    When I run "kata tax context 'filesystem:payments#area' --format json"
+    Then the command should succeed
+    And the JSON output at "$.node.qualifiedName" should equal "filesystem:payments#area"
+    And the JSON output at "$.items[*].qualifiedName" should contain "filesystem:encrypt-card-data"
+    And the JSON output at "$.items[*].qualifiedName" should contain "filesystem:use-postgres"
+    And the JSON output at "$.items[*].qualifiedName" should contain "filesystem:encrypt-card-data.scan-for-card-numbers"
+    And the JSON output at "$.dropped.unresolved" should equal "0"
+    When I run "kata tax context 'filesystem:payments#rule' --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[*]" should have 0 items
+
+  Scenario: The children of a node that shares its name still find their parent
+    When I run "kata tax create rule payments --set title=Payments --set severity=recommended -d 'A rule that is also called payments.'"
+    Then the command should succeed
+    When I run "kata tax context filesystem:payments.checkout --path CHILD_OF:out --no-inherit --detail refs --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[?(@.path=='CHILD_OF:out')].qualifiedName" should contain "filesystem:payments#area"
+
+  Scenario: A bare name of a nested node is refused with the name that works
+    When I run "kata tax context web-api"
+    Then the command should fail
+    And the output should contain "a node is named by its qualified name: use 'filesystem:payments.checkout.web-api'"
+
+  Scenario: An FQTN that one backend holds works without the backend
+    When I run "kata tax context payments.checkout.web-api --format json"
+    Then the command should succeed
+    And the JSON output at "$.node.qualifiedName" should equal "filesystem:payments.checkout.web-api"
+
+  # ─────────────────────────────────────────────────────────────
+  # #306: the markdown answer shows a node's fields
+  # ─────────────────────────────────────────────────────────────
+
+  Scenario: At full detail the markdown renders a list field as bullets
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out --detail full"
+    Then the command should succeed
+    And the output should contain "- **httpx** `filesystem:httpx` · version: 0.27"
+    And the output should contain "  - decisions:"
+    And the output should contain "    - pin-httpx"
+    And the output should not contain "['pin-httpx']"
+
+  Scenario: At summary detail the markdown shows only the declared summary fields
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out --detail summary"
+    Then the command should succeed
+    And the output should contain "- **httpx** `filesystem:httpx` · version: 0.27"
+    And the output should not contain "- decisions:"
+
+  Scenario: The markdown and the JSON hold the same items for the same budget
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out --detail full --budget 120"
+    Then the command should succeed
+    When I record the item names of the context output
+    And I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out --detail full --budget 120 --format json"
+    Then the command should succeed
+    And the context output should show the recorded item names
+
+  # ─────────────────────────────────────────────────────────────
+  # #307: one item reached by several routes
+  # ─────────────────────────────────────────────────────────────
+
+  Scenario: An item reached by two routes prints its shortest route and counts the other
+    When I run "kata tax relate filesystem:payments.checkout.web-api GOVERNED_BY filesystem:pin-httpx"
+    Then the command should succeed
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out/GOVERNED_BY:out --detail summary"
+    Then the command should succeed
+    And the output should contain "why: ─GOVERNED_BY→ (+1 more route)"
+    And the output should not contain "package filesystem:httpx ─GOVERNED_BY→"
+
+  Scenario: At full detail the markdown lists every route
+    When I run "kata tax relate filesystem:payments.checkout.web-api GOVERNED_BY filesystem:pin-httpx"
+    Then the command should succeed
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out/GOVERNED_BY:out --detail full"
+    Then the command should succeed
+    And the output should contain "why: ─GOVERNED_BY→"
+    And the output should contain "why: ─USES_PACKAGE→ package filesystem:httpx ─GOVERNED_BY→"
+    And the output should not contain "more route"
+
+  Scenario: The JSON keeps every route, the shortest first
+    When I run "kata tax relate filesystem:payments.checkout.web-api GOVERNED_BY filesystem:pin-httpx"
+    Then the command should succeed
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out/GOVERNED_BY:out --detail summary --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:pin-httpx')].why[*]" should have 2 items
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:pin-httpx')].why[0].path" should equal "GOVERNED_BY:out"
+

katalyst_plugin_context-0.2.1a7/xspec/features/cli/53_kata_context_budget_policy.feature

@@ -0,0 +1,265 @@
+@cli @area-context
+Feature: Kata CLI - Context: the budget, profile policy, and lint of the policy
+  As an operator deciding what each agent role may pull into its context
+  I want a size budget that cuts the least important items first, and policy per profile that only narrows
+  So that a small answer still holds the rule that blocks, and a profile never widens what the schema allows
+
+  # docs/plugins/context/index.md ("The budget", "Policy", "What kata tax lint checks"), against the
+  # same payments catalogue as 52_kata_context.feature.
+  #
+  # katalyst-taxonomy#291: the budget measures the content of the items, not the serialisation, so
+  # JSON and markdown return the same items for the same budget.
+  # katalyst-taxonomy#292: lint warns when a profile's policy makes an always-included view
+  # unreachable.
+  #
+  # The plugin's config.yaml section holds policy for every profile and for one profile. A
+  # profile is a role: `reviewer` reads decisions and rules in summary and follows no incoming
+  # step and no package; `ci-bot` reads names only, in a small answer.
+
+  Background:
+    Given the payments catalogue is installed
+
+  # ─────────────────────────────────────────────────────────────
+  # The budget
+  # ─────────────────────────────────────────────────────────────
+
+  @smoke
+  Scenario: A small budget cuts the items that do not block first, and says what it cut
+    When I run "kata tax context filesystem:payments.checkout.web-api --budget 100 --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[*].qualifiedName" should contain "filesystem:encrypt-card-data"
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:encrypt-card-data')].blocking.blocking" should equal "true"
+    And the JSON output at "$.truncated.cutBlocking" should equal "0"
+    And the JSON output at "$.truncated.cut[*].qualifiedNames[*]" should contain "filesystem:log-correlation-id"
+    And the JSON output at "$.truncated.cut[*].qualifiedNames[*]" should contain "filesystem:encrypt-card-data.scan-for-card-numbers"
+    And the JSON output at "$.truncated.cut[*].qualifiedNames[*]" should not contain "filesystem:encrypt-card-data"
+    And the JSON output at "$.truncated.hint.budget" should equal "270"
+
+  Scenario: The markdown names what the budget cut, and how to get it
+    When I run "kata tax context filesystem:payments.checkout.web-api --budget 100"
+    Then the command should succeed
+    And the output should contain "⛔ blocking · **Encrypt card data** `filesystem:encrypt-card-data`"
+    And the output should contain "## Cut by the budget (100 tokens;"
+    And the output should contain "view governance, `FOLLOWS_RULE:out`: 1 cut — `filesystem:log-correlation-id`"
+    And the output should contain "More: ask again with budget 270."
+
+  Scenario: The budget returns the same items over JSON and over markdown
+    When I run "kata tax context filesystem:payments.checkout.web-api --budget 100 --format json"
+    And I record the item names of the context output
+    And I run "kata tax context filesystem:payments.checkout.web-api --budget 100 --format markdown"
+    Then the command should succeed
+    And the context output should show the recorded item names
+
+  Scenario: Asking again with the hinted budget returns everything
+    When I run "kata tax context filesystem:payments.checkout.web-api --budget 270 --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[*]" should have 5 items
+    And the JSON output at "$.truncated" should be null
+
+  # ─────────────────────────────────────────────────────────────
+  # A profile narrows a view
+  # ─────────────────────────────────────────────────────────────
+
+  @smoke
+  Scenario: A profile's policy narrows the answer, and the notes say what it hid
+    Given I run "kata config profile create reviewer --copy-from local"
+    And the context plugin is configured with:
+      """
+      policy:
+        budget: { max: 8000 }
+      profiles:
+        reviewer:
+          policy:
+            detail: [refs, summary]
+            paths: { deny: ["*:in", "USES_PACKAGE"] }
+      """
+    When I run "kata --profile reviewer tax context filesystem:payments.checkout.web-api --view package-decisions --detail full --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[*].qualifiedName" should contain "filesystem:encrypt-card-data"
+    And the JSON output at "$.items[*].qualifiedName" should not contain "filesystem:encrypt-card-data.scan-for-card-numbers"
+    And the JSON output at "$.items[*].qualifiedName" should not contain "filesystem:pin-httpx"
+    And the JSON output at "$.policy.layers" should contain "profile:reviewer"
+    And the JSON output at "$.policy.notes[*].text" should contain "view 'governance' path 'FOLLOWS_RULE:out/CHILD_OF:in:check' is hidden by profile:reviewer"
+    And the JSON output at "$.policy.notes[*].text" should contain "view 'package-decisions' path 'USES_PACKAGE:out/GOVERNED_BY:out' is hidden by profile:reviewer"
+    And the JSON output at "$.policy.clamped[?(@.control=='detail')].requested" should equal "full"
+    And the JSON output at "$.policy.clamped[?(@.control=='detail')].effective" should equal "summary"
+    And the JSON output at "$.policy.clamped[?(@.control=='detail')].limitedBy" should equal "profile:reviewer"
+
+  Scenario: The same request under the default profile is not narrowed
+    Given I run "kata config profile create reviewer --copy-from local"
+    And the context plugin is configured with:
+      """
+      profiles:
+        reviewer:
+          policy:
+            paths: { deny: ["*:in", "USES_PACKAGE"] }
+      """
+    When I run "kata tax context filesystem:payments.checkout.web-api --view package-decisions --detail full --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[*].qualifiedName" should contain "filesystem:encrypt-card-data.scan-for-card-numbers"
+    And the JSON output at "$.items[*].qualifiedName" should contain "filesystem:pin-httpx"
+    And the JSON output at "$.policy.layers" should not contain "profile:reviewer"
+    And the JSON output at "$.policy.notes[*]" should have 0 items
+
+  Scenario: The markdown ends with the policy layers and the notes
+    Given I run "kata config profile create reviewer --copy-from local"
+    And the context plugin is configured with:
+      """
+      profiles:
+        reviewer:
+          policy:
+            detail: [refs, summary]
+            paths: { deny: ["*:in", "USES_PACKAGE"] }
+      """
+    When I run "kata --profile reviewer tax context filesystem:payments.checkout.web-api --view package-decisions --detail full"
+    Then the command should succeed
+    And the output should contain "_Policy: builtin → kind:component → profile:reviewer_"
+    And the output should contain "- view 'governance' path 'FOLLOWS_RULE:out/CHILD_OF:in:check' is hidden by profile:reviewer"
+    And the output should contain "- detail: asked full, got summary (profile:reviewer)"
+    And the output should not contain "Scan for card numbers"
+
+  Scenario: A profile cannot widen a limit: a request above its budget is lowered
+    Given I run "kata config profile create ci-bot --copy-from local"
+    And the context plugin is configured with:
+      """
+      profiles:
+        ci-bot:
+          policy:
+            detail: [refs]
+            budget: { max: 100 }
+          defaults: { budget: 100 }
+      """
+    When I run "kata --profile ci-bot tax context filesystem:payments.checkout.web-api --budget 1000 --format json"
+    Then the command should succeed
+    And the JSON output at "$.effective.budget" should equal "100"
+    And the JSON output at "$.policy.clamped[?(@.control=='budget')].requested" should equal "1000"
+    And the JSON output at "$.policy.clamped[?(@.control=='budget')].effective" should equal "100"
+    And the JSON output at "$.policy.clamped[?(@.control=='budget')].limitedBy" should equal "profile:ci-bot"
+    And the JSON output at "$.truncated.hint.budget" should equal "100"
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:encrypt-card-data')].blocking.blocking" should equal "true"
+
+  Scenario: A profile can take a view out of the always-included views, and the answer says so
+    Given I run "kata config profile create ci-bot --copy-from local"
+    And the context plugin is configured with:
+      """
+      profiles:
+        ci-bot:
+          policy:
+            always_include: []
+      """
+    When I run "kata --profile ci-bot tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out --format json"
+    Then the command should succeed
+    And the JSON output at "$.items[*].qualifiedName" should contain "filesystem:httpx"
+    And the JSON output at "$.items[*].qualifiedName" should not contain "filesystem:encrypt-card-data"
+    And the JSON output at "$.dropped.always[0].view" should equal "governance"
+    And the JSON output at "$.dropped.always[0].limitedBy" should equal "profile:ci-bot"
+    When I run "kata --profile ci-bot tax context filesystem:payments.checkout.web-api --map --format json"
+    Then the command should succeed
+    And the JSON output at "$.views[?(@.name=='governance')].always" should equal "false"
+    And the JSON output at "$.views[?(@.name=='governance')].droppedBy" should equal "profile:ci-bot"
+
+  Scenario: The effective policy of a node can be printed
+    Given I run "kata config profile create reviewer --copy-from local"
+    And the context plugin is configured with:
+      """
+      profiles:
+        reviewer:
+          policy:
+            detail: [refs, summary]
+      """
+    When I run "kata --profile reviewer tax context filesystem:payments.checkout.web-api --policy"
+    Then the command should succeed
+    And the output should be valid JSON
+    And the JSON output at "$.effective.layers" should contain "kind:component"
+    And the JSON output at "$.effective.layers" should contain "profile:reviewer"
+    And the JSON output at "$.effective.detail" should not contain "full"
+
+  # ─────────────────────────────────────────────────────────────
+  # #292: kata tax lint warns when a profile hides an always-included view
+  # ─────────────────────────────────────────────────────────────
+
+  Scenario: Lint warns when a profile hides a path of an always-included view
+    Given I run "kata config profile create reviewer --copy-from local"
+    And the context plugin is configured with:
+      """
+      profiles:
+        reviewer:
+          policy:
+            paths: { deny: ["*:in", "USES_PACKAGE"] }
+      """
+    When I run "kata tax lint"
+    Then the command should succeed
+    And the output should contain "Rule warnings"
+    And the output should contain "[context-policy] kind 'component': profile:reviewer hides always-included view 'governance' path 'FOLLOWS_RULE:out/CHILD_OF:in:check'"
+    And the output should contain "[context-policy] kind 'service': profile:reviewer hides always-included view 'governance' path 'FOLLOWS_RULE:out/CHILD_OF:in:check'"
+    And the output should contain "[context-policy] kind 'area': profile:reviewer hides always-included view 'governance' path 'FOLLOWS_RULE:out/CHILD_OF:in:check'"
+
+  Scenario: Lint says when the hidden path can reach a blocking item
+    Given I run "kata config profile create triage --copy-from local"
+    And the context plugin is configured with:
+      """
+      profiles:
+        triage:
+          policy:
+            paths: { deny: ["FOLLOWS_RULE"] }
+            inheritance: false
+      """
+    When I run "kata tax lint"
+    Then the command should succeed
+    And the output should contain "[context-policy] kind 'component': profile:triage turns inheritance off, so always-included view 'governance' loses what its ancestors carry, which can include blocking items (rule)"
+    And the output should contain "[context-policy] kind 'component': profile:triage hides always-included view 'governance' path 'FOLLOWS_RULE:out'; it can reach blocking items (rule)"
+
+  Scenario: Lint warns when a profile takes the view out of the always-included views
+    Given I run "kata config profile create ci-bot --copy-from local"
+    And the context plugin is configured with:
+      """
+      profiles:
+        ci-bot:
+          policy:
+            always_include: []
+      """
+    When I run "kata tax lint"
+    Then the command should succeed
+    And the output should contain "[context-policy] kind 'component': profile:ci-bot"
+    And the output should contain "always-included view 'governance'"
+
+  Scenario: Lint warns when a max_depth is shorter than a path of the always-included view
+    Given I run "kata config profile create shallow --copy-from local"
+    And the context plugin is configured with:
+      """
+      profiles:
+        shallow:
+          policy:
+            max_depth: 1
+      """
+    When I run "kata tax lint"
+    Then the command should succeed
+    And the output should contain "[context-policy] kind 'component': profile:shallow sets max_depth 1, shorter than always-included view 'governance' path 'FOLLOWS_RULE:out/CHILD_OF:in:check'"
+
+  Scenario: Lint is silent when no profile narrows the always-included view
+    Given I run "kata config profile create reviewer --copy-from local"
+    And the context plugin is configured with:
+      """
+      profiles:
+        reviewer:
+          policy:
+            detail: [refs, summary]
+            budget: { max: 2000 }
+      """
+    When I run "kata tax lint"
+    Then the command should succeed
+    And the output should not contain "context-policy"
+
+  Scenario: A policy that breaks the plugin's schema fails closed
+    Given I run "kata config profile create reviewer --copy-from local"
+    And the context plugin is configured with:
+      """
+      profiles:
+        reviewer:
+          policy:
+            budget: { max: lots }
+      """
+    When I run "kata --profile reviewer tax context filesystem:payments.checkout.web-api"
+    Then the command should fail
+    And the output should contain "budget.max"
+    And the output should contain "is not of type 'integer'"

katalyst_plugin_context-0.2.1a7/xspec/features/mcp/09_mcp_context.feature

@@ -0,0 +1,190 @@
+@mcp @area-context
+Feature: MCP Server - Context: taxonomy_context_map and taxonomy_context
+  As an AI agent about to change a node
+  I want the map of what surrounds it and one call that returns the decisions and rules that apply
+  So that I read a rule the node inherits, and a blocking item, before I act
+
+  # docs/plugins/context/index.md ("The surfaces"), against the service catalogue of
+  # examples/catalogue with the payments model of plugins/context/xspec/fixtures/context-catalogue. Over MCP
+  # the format defaults to json and the answer is an envelope: {ok, data}. With
+  # format=markdown, data is {markdown, result}. The same service answers the CLI, so the
+  # details are in 52_kata_context.feature and 53_kata_context_budget_policy.feature; these
+  # scenarios hold the essentials of the tools.
+
+  Background:
+    Given the MCP server is connected
+    And the payments catalogue is installed in the MCP workspace
+
+  Scenario: The server exposes the context tools
+    Then the MCP server should expose a tool named "taxonomy_context_map"
+    And the MCP server should expose a tool named "taxonomy_context"
+
+  @smoke
+  Scenario: The map lists the ancestors, the views and what can be asked next
+    When I call MCP tool "taxonomy_context_map" with:
+      | key  | value                                  |
+      | node | filesystem:payments.checkout.web-api   |
+    Then the result should succeed
+    And the JSON result at "$.ok" should equal "true"
+    And the JSON result at "$.data.node.qualifiedName" should equal "filesystem:payments.checkout.web-api"
+    And the JSON result at "$.data.ancestors[*].qualifiedName" should contain "filesystem:payments.checkout"
+    And the JSON result at "$.data.ancestors[*].qualifiedName" should contain "filesystem:payments"
+    And the JSON result at "$.data.views[?(@.name=='governance')].always" should equal "true"
+    And the JSON result at "$.data.views[?(@.name=='package-decisions')].always" should equal "false"
+    And the JSON result at "$.data.relationships[*].path" should contain "USES_PACKAGE:out"
+    And the JSON result at "$.data.options.steps" should contain "GOVERNED_BY:out"
+    And the JSON result at "$.data.always.items[*].qualifiedName" should contain "filesystem:encrypt-card-data"
+
+  @smoke
+  Scenario: A call with no path and no view returns the always-included view, the mandatory rule first
+    When I call MCP tool "taxonomy_context" with:
+      | key  | value                                  |
+      | node | filesystem:payments.checkout.web-api   |
+    Then the result should succeed
+    And the JSON result at "$.data.items[0].qualifiedName" should equal "filesystem:encrypt-card-data"
+    And the JSON result at "$.data.items[0].blocking.blocking" should equal "true"
+    And the JSON result at "$.data.items[0].inheritedFrom" should equal "filesystem:payments"
+    And the JSON result at "$.data.items[?(@.qualifiedName=='filesystem:log-correlation-id')].blocking.blocking" should equal "false"
+    And the JSON result at "$.data.effective.always" should contain "governance"
+    And the JSON result at "$.data.truncated" should be null
+
+  Scenario: A named view still holds the always-included view
+    When I call MCP tool "taxonomy_context" with:
+      | key   | value                                 |
+      | node  | filesystem:payments.checkout.web-api  |
+      | views | ["package-decisions"]                 |
+    Then the result should succeed
+    And the JSON result at "$.data.items[*].qualifiedName" should contain "filesystem:encrypt-card-data"
+    And the JSON result at "$.data.items[?(@.view=='package-decisions')].qualifiedName" should contain "filesystem:pin-httpx"
+
+  Scenario: A path still holds the always-included view
+    When I call MCP tool "taxonomy_context" with:
+      | key   | value                                 |
+      | node  | filesystem:payments.checkout.web-api  |
+      | paths | ["USES_PACKAGE:out"]                  |
+    Then the result should succeed
+    And the JSON result at "$.data.items[*].qualifiedName" should contain "filesystem:encrypt-card-data"
+    And the JSON result at "$.data.items[*].qualifiedName" should contain "filesystem:httpx"
+
+  Scenario: The detail and the depth decide how much is returned
+    When I call MCP tool "taxonomy_context" with:
+      | key     | value                                 |
+      | node    | filesystem:payments.checkout.web-api  |
+      | paths   | ["USES_PACKAGE:out"]                  |
+      | detail  | full                                  |
+    Then the result should succeed
+    And the JSON result at "$.data.items[?(@.qualifiedName=='filesystem:httpx')].detail" should equal "full"
+    And the JSON result at "$.data.items[?(@.qualifiedName=='filesystem:httpx')].spec.version" should equal "0.27"
+    When I call MCP tool "taxonomy_context" with:
+      | key     | value                                 |
+      | node    | filesystem:payments.checkout.web-api  |
+      | paths   | ["CHILD_OF:out"]                      |
+      | depth   | 2                                     |
+      | inherit | false                                 |
+      | detail  | refs                                  |
+    Then the result should succeed
+    And the JSON result at "$.data.items[?(@.path=='CHILD_OF:out')].qualifiedName" should contain "filesystem:payments"
+
+  Scenario: A small budget cuts the items that do not block first, over the default JSON format
+    When I call MCP tool "taxonomy_context" with:
+      | key    | value                                 |
+      | node   | filesystem:payments.checkout.web-api  |
+      | budget | 100                                   |
+    Then the result should succeed
+    And the JSON result at "$.data.items[*].qualifiedName" should contain "filesystem:encrypt-card-data"
+    And the JSON result at "$.data.items[?(@.qualifiedName=='filesystem:encrypt-card-data')].blocking.blocking" should equal "true"
+    And the JSON result at "$.data.truncated.cutBlocking" should equal "0"
+    And the JSON result at "$.data.truncated.cut[*].qualifiedNames[*]" should contain "filesystem:log-correlation-id"
+
+  Scenario: The budget returns the same items in JSON and in markdown
+    When I call MCP tool "taxonomy_context" with:
+      | key    | value                                 |
+      | node   | filesystem:payments.checkout.web-api  |
+      | budget | 100                                   |
+    And I record the item names of the MCP context result
+    And I call MCP tool "taxonomy_context" with:
+      | key    | value                                 |
+      | node   | filesystem:payments.checkout.web-api  |
+      | budget | 100                                   |
+      | format | markdown                              |
+    Then the result should succeed
+    And the MCP context result should show the recorded item names
+    And the markdown of the MCP context result should show the recorded item names
+    And the JSON result at "$.data.markdown" should contain "Cut by the budget (100 tokens;"
+
+  Scenario: A profile's policy narrows the answer, and the notes say what it hid
+    Given the MCP workspace has a profile "reviewer" that is active
+    And the context plugin is configured in the MCP workspace with:
+      """
+      profiles:
+        reviewer:
+          policy:
+            detail: [refs, summary]
+            paths: { deny: ["*:in", "USES_PACKAGE"] }
+      """
+    When I call MCP tool "taxonomy_context" with:
+      | key    | value                                 |
+      | node   | filesystem:payments.checkout.web-api  |
+      | views  | ["package-decisions"]                 |
+      | detail | full                                  |
+    Then the result should succeed
+    And the JSON result at "$.data.items[*].qualifiedName" should contain "filesystem:encrypt-card-data"
+    And the JSON result at "$.data.items[*].qualifiedName" should not include the value "filesystem:pin-httpx"
+    And the JSON result at "$.data.items[*].qualifiedName" should not include the value "filesystem:encrypt-card-data.scan-for-card-numbers"
+    And the JSON result at "$.data.policy.layers" should contain "profile:reviewer"
+    And the JSON result at "$.data.policy.notes[*].text" should contain "view 'package-decisions' path 'USES_PACKAGE:out/GOVERNED_BY:out' is hidden by profile:reviewer"
+    And the JSON result at "$.data.policy.clamped[?(@.control=='detail')].effective" should equal "summary"
+
+  Scenario: An FQTN that two kinds share is refused, with the names that disambiguate it
+    Given a config file ".global/taxonomy/catalogue/rules/payments.yaml" in the MCP workspace with:
+      """
+      apiVersion: katalyst.taxonomy/v2alpha
+      kind: rule
+      metadata:
+        name: payments
+      spec:
+        title: Payments
+        severity: recommended
+        description: A rule that is also called payments.
+        owners: [team@example.com]
+      """
+    When I call MCP tool "taxonomy_context" with:
+      | key  | value               |
+      | node | filesystem:payments |
+    Then the JSON result at "$.ok" should equal "false"
+    And the JSON result at "$.error.code" should equal "INVALID_INPUT"
+    And the result should contain "filesystem:payments#area"
+    And the result should contain "filesystem:payments#rule"
+    When I call MCP tool "taxonomy_context_map" with:
+      | key  | value                    |
+      | node | filesystem:payments#rule |
+    Then the result should succeed
+    And the JSON result at "$.data.node.qualifiedName" should equal "filesystem:payments#rule"
+
+  Scenario: A node that shares its name with another kind walks its own relationships
+    Given a config file ".global/taxonomy/catalogue/rules/payments.yaml" in the MCP workspace with:
+      """
+      apiVersion: katalyst.taxonomy/v2alpha
+      kind: rule
+      metadata:
+        name: payments
+      spec:
+        title: Payments
+        severity: recommended
+        description: A rule that is also called payments.
+        owners: [team@example.com]
+      """
+    When I call MCP tool "taxonomy_context" with:
+      | key  | value                    |
+      | node | filesystem:payments#area |
+    Then the result should succeed
+    And the JSON result at "$.data.items[*].qualifiedName" should contain "filesystem:use-postgres"
+    And the JSON result at "$.data.dropped.unresolved" should equal "0"
+
+  Scenario: A bare name of a nested node is refused with the name that works
+    When I call MCP tool "taxonomy_context" with:
+      | key  | value   |
+      | node | web-api |
+    Then the JSON result at "$.ok" should equal "false"
+    And the JSON result at "$.error.code" should equal "NOT_FOUND"
+    And the JSON result at "$.error.message" should contain "filesystem:payments.checkout.web-api"

katalyst_plugin_context-0.2.1a7/xspec/fixtures/context-catalogue/catalogue/areas/payments.yaml

@@ -0,0 +1,13 @@
+apiVersion: katalyst.taxonomy/v2alpha
+kind: area
+metadata:
+  name: payments
+spec:
+  owner: payments-team
+  description: Everything that moves money
+  owners:
+  - team@example.com
+  decisions:
+  - use-postgres
+  rules:
+  - encrypt-card-data

katalyst_plugin_context-0.2.1a7/xspec/fixtures/context-catalogue/catalogue/checks/encrypt-card-data.scan-for-card-numbers.yaml

@@ -0,0 +1,12 @@
+apiVersion: katalyst.taxonomy/v2alpha
+kind: check
+metadata:
+  name: "scan-for-card-numbers"
+spec:
+  title: "Scan for card numbers"
+  command: "make scan-pan"
+  description: "Scans the code and the log samples for card numbers."
+  owners:
+    - "team@example.com"
+  parents:
+    node: "encrypt-card-data"

katalyst_plugin_context-0.2.1a7/xspec/fixtures/context-catalogue/catalogue/components/payments.checkout.web-api.yaml

@@ -0,0 +1,15 @@
+apiVersion: katalyst.taxonomy/v2alpha
+kind: component
+metadata:
+  name: web-api
+spec:
+  language: python
+  description: The HTTP API that the checkout flow exposes to the storefront.
+  owners:
+  - team@example.com
+  parents:
+    node: payments.checkout
+  rules:
+  - log-correlation-id
+  packages:
+  - httpx

katalyst_plugin_context-0.2.1a7/xspec/fixtures/context-catalogue/catalogue/decisions/async-events.yaml

@@ -0,0 +1,10 @@
+apiVersion: katalyst.taxonomy/v2alpha
+kind: decision
+metadata:
+  name: "async-events"
+spec:
+  title: "Publish events, do not call"
+  status: "accepted"
+  description: "The checkout service tells other services about an order by publishing an event."
+  owners:
+    - "team@example.com"

katalyst_plugin_context-0.2.1a7/xspec/fixtures/context-catalogue/catalogue/decisions/pin-httpx.yaml

@@ -0,0 +1,10 @@
+apiVersion: katalyst.taxonomy/v2alpha
+kind: decision
+metadata:
+  name: "pin-httpx"
+spec:
+  title: "Pin httpx to 0.27"
+  status: "accepted"
+  description: "The web-api component pins httpx to the 0.27 series."
+  owners:
+    - "team@example.com"

katalyst_plugin_context-0.2.1a7/xspec/fixtures/context-catalogue/catalogue/decisions/use-postgres.yaml

@@ -0,0 +1,10 @@
+apiVersion: katalyst.taxonomy/v2alpha
+kind: decision
+metadata:
+  name: "use-postgres"
+spec:
+  title: "Use PostgreSQL"
+  status: "accepted"
+  description: "Every service in the payments area stores its data in PostgreSQL."
+  owners:
+    - "team@example.com"

katalyst_plugin_context-0.2.1a7/xspec/fixtures/context-catalogue/catalogue/packages/httpx.yaml

@@ -0,0 +1,11 @@
+apiVersion: katalyst.taxonomy/v2alpha
+kind: package
+metadata:
+  name: httpx
+spec:
+  version: '0.27'
+  description: HTTP client
+  owners:
+  - team@example.com
+  decisions:
+  - pin-httpx

katalyst_plugin_context-0.2.1a7/xspec/fixtures/context-catalogue/catalogue/rules/encrypt-card-data.yaml

@@ -0,0 +1,10 @@
+apiVersion: katalyst.taxonomy/v2alpha
+kind: rule
+metadata:
+  name: "encrypt-card-data"
+spec:
+  title: "Encrypt card data"
+  severity: "mandatory"
+  description: "Card numbers are encrypted at rest and in transit. No log line contains a card number."
+  owners:
+    - "team@example.com"

katalyst_plugin_context-0.2.1a7/xspec/fixtures/context-catalogue/catalogue/rules/log-correlation-id.yaml

@@ -0,0 +1,10 @@
+apiVersion: katalyst.taxonomy/v2alpha
+kind: rule
+metadata:
+  name: "log-correlation-id"
+spec:
+  title: "Log a correlation id"
+  severity: "recommended"
+  description: "Every log line of a request carries the correlation id of the request."
+  owners:
+    - "team@example.com"

katalyst_plugin_context-0.2.1a7/xspec/fixtures/context-catalogue/catalogue/services/payments.checkout.yaml

@@ -0,0 +1,13 @@
+apiVersion: katalyst.taxonomy/v2alpha
+kind: service
+metadata:
+  name: checkout
+spec:
+  tier: 1
+  description: The checkout flow
+  owners:
+  - team@example.com
+  parents:
+    node: payments
+  decisions:
+  - async-events

katalyst_plugin_context-0.2.1a7/xspec/package.json

@@ -0,0 +1,15 @@
+{
+  "name": "katalyst-plugin-context-xspec",
+  "private": true,
+  "version": "0.1.0",
+  "type": "module",
+  "description": "The context plugin's xspec suite. Its dependencies and the shared step library are xspec/'s (npm workspace at the repository root).",
+  "scripts": {
+    "gen": "bddgen",
+    "test": "bddgen && playwright test",
+    "typecheck": "tsc --noEmit",
+    "smoke": "../../../xspec/scripts/run-tags.sh '@smoke'",
+    "tags": "../../../xspec/scripts/run-tags.sh",
+    "clean": "rm -rf .features-gen test-results cucumber-report blob-report playwright-report"
+  }
+}

katalyst_plugin_context-0.2.1a7/xspec/playwright.config.ts

@@ -0,0 +1,5 @@
+// The context plugin's suite: its features (features/<surface>/), fixtures and steps (steps/).
+// The shared step library (xspec/support/) and config (xspec/playwright.base.ts) are the root's.
+import { xspecConfig } from '../../../xspec/playwright.base.js';
+
+export default xspecConfig(import.meta.url);

katalyst_plugin_context-0.2.1a7/xspec/steps/context.ts

@@ -0,0 +1,216 @@
+/**
+ * Step definitions for the context plugin features (kata tax context, taxonomy_context_map,
+ * taxonomy_context).
+ *
+ * The fixture is the neutral service catalogue of `examples/catalogue`, installed the way
+ * docs/user-guide/getting-started.md installs it (`kata tax bundle add`), with the payments
+ * nodes of `plugins/context/xspec/fixtures/context-catalogue` copied in beside it. The nodes are written
+ * as files rather than through ~20 `kata tax create` calls, which would be most of every
+ * scenario's time.
+ */
+import fs from 'node:fs';
+import path from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { expect } from '@playwright/test';
+import { createBdd } from 'playwright-bdd';
+import { buildEnv, createTempDir, dedent, runCommand } from '../../../../xspec/support/cli/steps.js';
+import { runKata } from '../../../../xspec/support/mcp/steps.js';
+import { repoCommand } from '../../../../xspec/support/runner.js';
+import type { CliWorld, test as sharedTest } from '../../../../xspec/support/fixtures.js';
+import type { McpPort, McpToolResult } from '../../../../xspec/support/mcp/port.js';
+
+const __dirname = path.dirname(fileURLToPath(import.meta.url));
+const repoRoot = path.resolve(__dirname, '../../../..');
+const catalogueExample = path.join(repoRoot, 'examples', 'catalogue');
+const paymentsFixture = path.join(__dirname, '..', 'fixtures', 'context-catalogue', 'catalogue');
+
+/** Copy the payments nodes into the repository, beside what the bundle's kinds store. */
+function copyPayments(repoDir: string): void {
+  const target = path.join(repoDir, '.global', 'taxonomy', 'catalogue');
+  fs.mkdirSync(target, { recursive: true });
+  fs.cpSync(paymentsFixture, target, { recursive: true });
+}
+
+/**
+ * The text that goes under `spec:` of config.yaml to configure the context plugin: the
+ * docstring is the plugin's `config` mapping.
+ */
+function pluginsBlock(configYaml: string): string {
+  const body = dedent(configYaml)
+    .split('\n')
+    .map((line) => (line.length > 0 ? `      ${line}` : line))
+    .join('\n');
+  return ['  plugins:', '  - name: context', '    config:', body, ''].join('\n');
+}
+
+/** Append the plugin block to a config file whose `spec:` is its last mapping. */
+function appendPluginConfig(configFile: string, configYaml: string): void {
+  const current = fs.readFileSync(configFile, 'utf-8');
+  expect(current, `${configFile} already configures plugins`).not.toContain('\n  plugins:');
+  fs.writeFileSync(configFile, `${current.replace(/\n*$/, '\n')}${pluginsBlock(configYaml)}`, 'utf-8');
+}
+
+/**
+ * The qualified names of the items in a context answer: from the JSON result (a CLI
+ * `--format json` answer, or an MCP envelope with or without markdown beside it), or from
+ * the markdown, whose item bullets come before the cut report and the policy line.
+ */
+export function contextItemNames(text: string): string[] {
+  let parsed: unknown;
+  try {
+    parsed = JSON.parse(text);
+  } catch {
+    parsed = undefined;
+  }
+  if (parsed !== undefined && parsed !== null && typeof parsed === 'object') {
+    const root = parsed as Record<string, unknown>;
+    const data = (root.data ?? root) as Record<string, unknown>;
+    const result = (data.result ?? data) as { items?: Array<{ qualifiedName: string }> };
+    expect(Array.isArray(result.items), `no items in ${text.substring(0, 300)}`).toBe(true);
+    return result.items!.map((item) => item.qualifiedName);
+  }
+  const names: string[] = [];
+  for (const line of text.split('\n')) {
+    if (line.startsWith('## Cut by the budget') || line.startsWith('_Policy:')) break;
+    const match = /^- .*?`([^`]+)`/.exec(line);
+    if (match) names.push(match[1]);
+  }
+  return names;
+}
+
+const recorded = new Map<string, string[]>();
+
+export function registerContextSteps(test: typeof sharedTest): void {
+  const { Given, When, Then } = createBdd(test);
+
+  // ── CLI ────────────────────────────────────────────────────────────────
+
+  Given(
+    'the payments catalogue is installed',
+    { tags: '@cli' },
+    async ({ cliWorld }: { cliWorld: CliWorld }) => {
+      cliWorld.workDir = createTempDir();
+      runCommand(cliWorld, repoCommand(repoRoot, 'kata tax init -y'));
+      expect(cliWorld.success, `init failed: ${cliWorld.stdout}${cliWorld.stderr}`).toBe(true);
+      runCommand(cliWorld, repoCommand(repoRoot, `kata tax bundle add -y "${catalogueExample}"`));
+      expect(cliWorld.success, `bundle add failed: ${cliWorld.stdout}${cliWorld.stderr}`).toBe(true);
+      copyPayments(cliWorld.workDir);
+    },
+  );
+
+  Given(
+    'the context plugin is configured with:',
+    { tags: '@cli' },
+    async ({ cliWorld }: { cliWorld: CliWorld }, docString: string) => {
+      const home = buildEnv(cliWorld).KATALYST_HOME as string;
+      appendPluginConfig(path.join(home, 'config', 'config.yaml'), docString);
+    },
+  );
+
+  When(
+    'I record the item names of the context output',
+    { tags: '@cli' },
+    async ({ cliWorld }: { cliWorld: CliWorld }) => {
+      expect(cliWorld.exitCode, cliWorld.stderr).toBe(0);
+      const names = contextItemNames(cliWorld.stdout);
+      expect(names.length, 'the answer has no items to record').toBeGreaterThan(0);
+      recorded.set(cliWorld.workDir, names);
+    },
+  );
+
+  Then(
+    'the context output should show the recorded item names',
+    { tags: '@cli' },
+    async ({ cliWorld }: { cliWorld: CliWorld }) => {
+      const before = recorded.get(cliWorld.workDir);
+      expect(before, 'no item names were recorded').toBeTruthy();
+      expect(contextItemNames(cliWorld.stdout)).toEqual(before);
+    },
+  );
+
+  Then(
+    'the output should list {string} before {string}',
+    { tags: '@cli' },
+    async ({ cliWorld }: { cliWorld: CliWorld }, first: string, second: string) => {
+      const out = cliWorld.stdout;
+      const a = out.indexOf(first);
+      const b = out.indexOf(second);
+      expect(a, `"${first}" is not in the output`).toBeGreaterThanOrEqual(0);
+      expect(b, `"${second}" is not in the output`).toBeGreaterThanOrEqual(0);
+      expect(a, `"${first}" should come before "${second}"`).toBeLessThan(b);
+    },
+  );
+
+  // ── MCP ────────────────────────────────────────────────────────────────
+
+  Given(
+    'the payments catalogue is installed in the MCP workspace',
+    { tags: '@mcp' },
+    async ({ mcp }: { mcp: McpPort }) => {
+      const workspace = mcp.getWorkspaceDir();
+      runKata(`kata tax bundle add -y "${catalogueExample}"`, workspace);
+      copyPayments(workspace);
+      await mcp.reconnect();
+    },
+  );
+
+  Given(
+    'the MCP workspace has a profile {string} that is active',
+    { tags: '@mcp' },
+    async ({ mcp }: { mcp: McpPort }, name: string) => {
+      const workspace = mcp.getWorkspaceDir();
+      runKata(`kata config profile create ${name} --copy-from local`, workspace);
+      runKata(`kata config profile use ${name}`, workspace);
+      await mcp.reconnect();
+    },
+  );
+
+  Given(
+    'the context plugin is configured in the MCP workspace with:',
+    { tags: '@mcp' },
+    async ({ mcp }: { mcp: McpPort }, docString: string) => {
+      const workspace = mcp.getWorkspaceDir();
+      appendPluginConfig(path.join(`${workspace}-home`, 'config', 'config.yaml'), docString);
+      await mcp.reconnect();
+    },
+  );
+
+  When(
+    'I record the item names of the MCP context result',
+    { tags: '@mcp' },
+    async ({ mcp, mcpToolResults }: { mcp: McpPort; mcpToolResults: Map<string, McpToolResult> }) => {
+      const result = mcpToolResults.get('_last');
+      expect(result, 'no result to record').toBeTruthy();
+      expect(result!.isError, result!.text).toBe(false);
+      const names = contextItemNames(result!.text);
+      expect(names.length, 'the answer has no items to record').toBeGreaterThan(0);
+      recorded.set(mcp.getWorkspaceDir(), names);
+    },
+  );
+
+  Then(
+    'the markdown of the MCP context result should show the recorded item names',
+    { tags: '@mcp' },
+    async ({ mcp, mcpToolResults }: { mcp: McpPort; mcpToolResults: Map<string, McpToolResult> }) => {
+      const before = recorded.get(mcp.getWorkspaceDir());
+      expect(before, 'no item names were recorded').toBeTruthy();
+      const result = mcpToolResults.get('_last');
+      expect(result, 'no result').toBeTruthy();
+      const markdown = (JSON.parse(result!.text) as { data: { markdown?: string } }).data.markdown;
+      expect(markdown, 'the result has no markdown').toBeTruthy();
+      expect(contextItemNames(markdown!)).toEqual(before);
+    },
+  );
+
+  Then(
+    'the MCP context result should show the recorded item names',
+    { tags: '@mcp' },
+    async ({ mcp, mcpToolResults }: { mcp: McpPort; mcpToolResults: Map<string, McpToolResult> }) => {
+      const before = recorded.get(mcp.getWorkspaceDir());
+      expect(before, 'no item names were recorded').toBeTruthy();
+      const result = mcpToolResults.get('_last');
+      expect(result, 'no result').toBeTruthy();
+      expect(contextItemNames(result!.text)).toEqual(before);
+    },
+  );
+}

katalyst_plugin_context-0.2.1a7/xspec/steps/steps.ts

@@ -0,0 +1,5 @@
+// The context plugin's own steps, on the shared fixtures. The shared steps are registered by xspec/support/steps.ts.
+import { test } from '../../../../xspec/support/fixtures.js';
+import { registerContextSteps } from './context.js';
+
+registerContextSteps(test);

katalyst_plugin_context-0.2.1a7/xspec/tsconfig.json

@@ -0,0 +1,4 @@
+{
+  "extends": "../../../xspec/tsconfig.json",
+  "include": ["steps/**/*.ts", "playwright.config.ts"]
+}