katalyst-plugin-context 0.2.1a17__tar.gz → 0.2.1a19__tar.gz

{katalyst_plugin_context-0.2.1a17 → katalyst_plugin_context-0.2.1a19}/.gitignore

@@ -125,3 +125,6 @@ node_modules/
 # Bard's built web assets (SPA, server bundle, desktop shell): build output, made by
 # scripts/build_bard_web.sh where Bard is tested, packaged or served. The wheel includes them.
 plugins/bard/src/katalyst_plugin_bard/web_dist/
+
+# `just dev-bundle`: kata without the test bundle
+.venv-bundle/

{katalyst_plugin_context-0.2.1a17 → katalyst_plugin_context-0.2.1a19}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: katalyst-plugin-context
-Version: 0.2.1a17
+Version: 0.2.1a19
 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.1a17 → katalyst_plugin_context-0.2.1a19}/pyproject.toml

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

{katalyst_plugin_context-0.2.1a17 → katalyst_plugin_context-0.2.1a19}/xspec/features/cli/52_kata_context.feature

@@ -30,7 +30,7 @@ Feature: Kata CLI - Context: what an agent working on a node gets
     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_DECISION: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)"
@@ -248,27 +248,27 @@ Feature: Kata CLI - Context: what an agent working on a node gets
   # ─────────────────────────────────────────────────────────────
 
   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"
+    When I run "kata tax relate filesystem:payments.checkout.web-api FOLLOWS_DECISION 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"
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out/FOLLOWS_DECISION: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→"
+    And the output should contain "why: ─FOLLOWS_DECISION→ (+1 more route)"
+    And the output should not contain "package filesystem:httpx ─FOLLOWS_DECISION→"
 
   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"
+    When I run "kata tax relate filesystem:payments.checkout.web-api FOLLOWS_DECISION 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"
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out/FOLLOWS_DECISION: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 contain "why: ─FOLLOWS_DECISION→"
+    And the output should contain "why: ─USES_PACKAGE→ package filesystem:httpx ─FOLLOWS_DECISION→"
     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"
+    When I run "kata tax relate filesystem:payments.checkout.web-api FOLLOWS_DECISION 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"
+    When I run "kata tax context filesystem:payments.checkout.web-api --path USES_PACKAGE:out/FOLLOWS_DECISION: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"
+    And the JSON output at "$.items[?(@.qualifiedName=='filesystem:pin-httpx')].why[0].path" should equal "FOLLOWS_DECISION:out"
 

{katalyst_plugin_context-0.2.1a17 → katalyst_plugin_context-0.2.1a19}/xspec/features/cli/53_kata_context_budget_policy.feature

@@ -33,7 +33,7 @@ Feature: Kata CLI - Context: the budget, profile policy, and lint of the policy
     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"
+    And the JSON output at "$.truncated.hint.budget" should equal "272"
 
   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"
@@ -41,7 +41,7 @@ Feature: Kata CLI - Context: the budget, profile policy, and lint of the policy
     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."
+    And the output should contain "More: ask again with budget 272."
 
   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"
@@ -51,7 +51,7 @@ Feature: Kata CLI - Context: the budget, profile policy, and lint of the policy
     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"
+    When I run "kata tax context filesystem:payments.checkout.web-api --budget 272 --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
@@ -80,7 +80,7 @@ Feature: Kata CLI - Context: the budget, profile policy, and lint of the policy
     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.notes[*].text" should contain "view 'package-decisions' path 'USES_PACKAGE:out/FOLLOWS_DECISION: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"

katalyst_plugin_context-0.2.1a19/xspec/features/cli/54_kata_context_plugin_turned_off.feature

@@ -0,0 +1,52 @@
+@cli @area-context
+Feature: Kata CLI - Context: a plugin turned off in the configuration contributes nothing
+  As an operator who has turned the context plugin off
+  I want it to add no lint rule and no command, whatever else its section of the configuration says
+  So that off means off, in every command
+
+  # `enabled: false` on a plugin of `spec.plugins` stops it everywhere: the lint rules it
+  # adds, the `kata tax context` command, the REST routes and MCP tools. The same configuration with the
+  # plugin on warns in 53_kata_context_budget_policy.feature. See also
+  # mcp/xspec/features/api/19_api_plugin_turned_off.feature (the REST routes).
+  # (github.com/esimplicityinc/katalyst-taxonomy/issues/347)
+
+  Background:
+    Given the payments catalogue is installed
+
+  @smoke
+  Scenario: A plugin turned off adds no lint rule
+    Given I run "kata config profile create reviewer --copy-from local"
+    And the context plugin is turned off and 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 not contain "context-policy"
+    And the output should not contain "Rule warnings"
+
+  Scenario: A plugin turned off adds no command
+    Given the context plugin is turned off and configured with:
+      """
+      policy:
+        max_depth: 3
+      """
+    When I run "kata tax context filesystem:payments.checkout.web-api"
+    Then the command should fail
+    And the output should contain "No such command 'context'"
+
+  Scenario: The same section with the plugin on is linted
+    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 "[context-policy]"

{katalyst_plugin_context-0.2.1a17 → katalyst_plugin_context-0.2.1a19}/xspec/features/mcp/09_mcp_context.feature

@@ -32,7 +32,7 @@ Feature: MCP Server - Context: taxonomy_context_map and taxonomy_context
     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.options.steps" should contain "FOLLOWS_DECISION:out"
     And the JSON result at "$.data.always.items[*].qualifiedName" should contain "filesystem:encrypt-card-data"
 
   @smoke
@@ -132,7 +132,7 @@ Feature: MCP Server - Context: taxonomy_context_map and taxonomy_context
     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.notes[*].text" should contain "view 'package-decisions' path 'USES_PACKAGE:out/FOLLOWS_DECISION: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

{katalyst_plugin_context-0.2.1a17 → katalyst_plugin_context-0.2.1a19}/xspec/steps/context.ts

@@ -35,19 +35,19 @@ function copyPayments(repoDir: string): void {
  * 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 {
+function pluginsBlock(configYaml: string, enabled = true): string {
   const body = dedent(configYaml)
     .split('\n')
     .map((line) => (line.length > 0 ? `      ${line}` : line))
     .join('\n');
-  return ['  plugins:', '  - name: context', '    config:', body, ''].join('\n');
+  return ['  plugins:', '  - name: context', ...(enabled ? [] : ['    enabled: false']), '    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 {
+function appendPluginConfig(configFile: string, configYaml: string, enabled = true): 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');
+  fs.writeFileSync(configFile, `${current.replace(/\n*$/, '\n')}${pluginsBlock(configYaml, enabled)}`, 'utf-8');
 }
 
 /**
@@ -107,6 +107,15 @@ export function registerContextSteps(test: typeof sharedTest): void {
     },
   );
 
+  Given(
+    'the context plugin is turned off and 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, false);
+    },
+  );
+
   When(
     'I record the item names of the context output',
     { tags: '@cli' },