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

{katalyst_plugin_context-0.2.1a17 → katalyst_plugin_context-0.2.1a18}/.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.1a18}/PKG-INFO

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

@@ -1,6 +1,6 @@
 [project]
 name = "katalyst-plugin-context"
-version = "0.2.1a17"
+version = "0.2.1a18"
 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.1a18/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.1a18}/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' },