@nathapp/nax 0.28.0 → 0.30.0

package/nax/features/nax-compliance/prd.json

@@ -1,52 +0,0 @@
-{
-  "project": "@nathapp/nax",
-  "feature": "nax-compliance",
-  "branchName": "feat/v0.19.0-sec",
-  "createdAt": "2026-03-05T02:37:00Z",
-  "updatedAt": "2026-03-05T02:38:46.450Z",
-  "userStories": [
-    {
-      "id": "US-001",
-      "title": "Node.js API Removal",
-      "description": "Replace all forbidden Node.js APIs (readFileSync, appendFileSync, existsSync, setTimeout) with Bun-native equivalents (Bun.file().text(), Bun.write, Bun.file().exists(), Bun.sleep) across the codebase as per the v0.19.0 roadmap. Refer to .claude/rules/04-forbidden-patterns.md.",
-      "acceptanceCriteria": [
-        "No occurrences of readFileSync or appendFileSync remain in src/",
-        "No occurrences of existsSync remain in src/ (unless performance critical)",
-        "No occurrences of setTimeout remain in src/",
-        "Codebase passes typecheck and lint after changes"
-      ],
-      "status": "failed",
-      "passes": false,
-      "attempts": 1,
-      "routing": {
-        "complexity": "simple",
-        "modelTier": "powerful",
-        "testStrategy": "test-after"
-      },
-      "priorErrors": [
-        "Attempt 1 failed with model tier: fast: Stage requested escalation to higher tier",
-        "Attempt 1 failed with model tier: balanced: Stage requested escalation to higher tier"
-      ],
-      "priorFailures": [
-        {
-          "attempt": 1,
-          "modelTier": "fast",
-          "stage": "escalation",
-          "summary": "Failed with tier fast, escalating to next tier",
-          "timestamp": "2026-03-05T02:37:41.586Z"
-        },
-        {
-          "attempt": 1,
-          "modelTier": "balanced",
-          "stage": "escalation",
-          "summary": "Failed with tier balanced, escalating to next tier",
-          "timestamp": "2026-03-05T02:38:14.713Z"
-        }
-      ],
-      "escalations": [],
-      "dependencies": [],
-      "tags": [],
-      "storyPoints": 1
-    }
-  ]
-}

package/nax/features/nax-compliance/progress.txt

@@ -1 +0,0 @@
-[2026-03-05T02:38:46.450Z] US-001 — FAILED — Node.js API Removal — Execution failed

package/nax/features/orchestration-fixes/prd.json

@@ -1,89 +0,0 @@
-{
-  "project": "nax",
-  "branchName": "feat/v0.18.0-orchestration-fixes",
-  "feature": "orchestration-fixes",
-  "userStories": [
-    {
-      "id": "BUG-021",
-      "title": "Fix misleading Task classified log",
-      "description": "The 'Task classified' log in routing.ts currently logs the raw LLM output even after config/cache overrides are applied. This makes it look like overrides are ignored when they aren't.\n\nFix: Ensure the log reflects the final routing state (ctx.routing) after all overrides and greenfield detection are finished.\n\nAcceptance criteria:\n1. Log shows final testStrategy/complexity/modelTier after all overrides\n2. Existing tests pass",
-      "complexity": "simple",
-      "status": "passed",
-      "attempts": 0,
-      "priorErrors": [
-        "Attempt 1 failed with model tier: fast"
-      ],
-      "escalations": [],
-      "dependencies": [],
-      "tags": [],
-      "acceptanceCriteria": [],
-      "storyPoints": 1,
-      "routing": {
-        "complexity": "simple",
-        "modelTier": "balanced",
-        "testStrategy": "three-session-tdd-lite",
-        "reasoning": "three-session-tdd-lite: strategy:lite"
-      }
-    },
-    {
-      "id": "BUG-022",
-      "title": "Fix story interleaving in getNextStory()",
-      "description": "When a story fails and escalates, getNextStory() currently round-robins to the next pending story. This wastes iterations by jumping between unrelated tasks.\n\nFix: Update getNextStory() in src/execution/sequential-executor.ts to prioritize retrying the current story until max attempts are reached before moving to the next story.\n\nAcceptance criteria:\n1. If current story is failed but has attempts remaining, it is picked again for retry\n2. Run order: S1-I1 -> S1-I2 (retry) -> S2-I1 (if S1 complete/failed out)\n3. Unit test for getNextStory() behavior",
-      "complexity": "simple",
-      "status": "passed",
-      "attempts": 0,
-      "priorErrors": [
-        "Attempt 1 failed with model tier: fast"
-      ],
-      "escalations": [],
-      "dependencies": [],
-      "tags": [],
-      "acceptanceCriteria": [],
-      "storyPoints": 1,
-      "routing": {
-        "complexity": "simple",
-        "modelTier": "balanced",
-        "testStrategy": "three-session-tdd-lite",
-        "reasoning": "three-session-tdd-lite: strategy:lite"
-      }
-    },
-    {
-      "id": "BUG-023",
-      "title": "Log exitCode/stderr on agent failure",
-      "description": "Agent session failures currently log 'rateLimited' but hide the actual exit code and stderr. This makes diagnosing silent failures (like 401, 500, or process crashes) difficult.\n\nFix: Audit src/agents/adapters/claude.ts and src/pipeline/stages/execution.ts. Ensure the 'Agent session failed' event includes exitCode and the tail of stderr in its data payload.\n\nAcceptance criteria:\n1. agent.complete event includes exitCode and stderr tail on failure\n2. Logs are machine-readable and don't break JSONL format",
-      "complexity": "simple",
-      "status": "passed",
-      "attempts": 0,
-      "priorErrors": [],
-      "escalations": [],
-      "dependencies": [],
-      "tags": [],
-      "acceptanceCriteria": [],
-      "storyPoints": 1
-    },
-    {
-      "id": "BUG-025",
-      "title": "Integrate Interaction Chain into Runner Loop",
-      "description": "The Interaction system is initialized but never called from the core orchestrator. This is a major integration task.\n\nFix:\n1. Add 'human-review' to TriggerName in src/interaction/types.ts and metadata in TRIGGER_METADATA\n2. Pass interactionChain from runner.ts -> executeSequential -> Pipeline\n3. Inject 'interaction' into PipelineContext\n4. Call executeTrigger('human-review', ...) when a story reaches max retries or a critical failure occurs\n5. Verify other triggers (security-review, story-ambiguity) are called at relevant pipeline stages\n\nAcceptance criteria:\n1. interactionChain is accessible in PipelineContext\n2. Story reaching max retries triggers a 'human-review' interaction request\n3. Test with CLI interaction plugin (non-headless)",
-      "complexity": "medium",
-      "status": "failed",
-      "attempts": 1,
-      "priorErrors": [
-        "Attempt 1 failed with model tier: balanced"
-      ],
-      "escalations": [],
-      "dependencies": [],
-      "tags": [],
-      "acceptanceCriteria": [],
-      "storyPoints": 1,
-      "routing": {
-        "complexity": "complex",
-        "modelTier": "powerful",
-        "testStrategy": "three-session-tdd-lite",
-        "reasoning": "three-session-tdd-lite: security-critical, strategy:lite"
-      },
-      "failureCategory": "session-failure"
-    }
-  ],
-  "updatedAt": "2026-03-02T16:29:51.415Z"
-}

package/nax/features/orchestration-fixes/progress.txt

@@ -1 +0,0 @@
-[2026-03-02T16:29:51.415Z] BUG-025 — FAILED — Integrate Interaction Chain into Runner Loop — Execution failed

package/nax/features/plugin-integration/US-007-VERIFICATION.md

@@ -1,259 +0,0 @@
-# US-007: Read plugin config entries from nax config.json
-
-## Verification Report
-
-**Date**: 2026-02-26
-**Status**: ✅ COMPLETE (Already Implemented)
-**Test Results**: 10/10 tests passing
-
----
-
-## Implementation Summary
-
-US-007 functionality was already fully implemented. This verification confirms all acceptance criteria are met with comprehensive test coverage.
-
-### Architecture
-
-The implementation follows this flow:
-
-```
-config.json (plugins[])
-  → loadConfig() (src/config/loader.ts)
-  → runner/CLI extracts config.plugins
-  → loadPlugins(globalDir, projectDir, configPlugins, projectRoot)
-  → resolveModulePath() for each plugin
-  → loadAndValidatePlugin(resolvedPath, config)
-  → plugin.setup(config)
-```
-
----
-
-## Acceptance Criteria Verification
-
-### ✅ AC1: plugins[] from config.json passed to loadPlugins()
-
-**Implementation:**
-- `src/execution/runner.ts:201-202`
-- `src/execution/run-lifecycle.ts:88-89`
-- `src/cli/plugins.ts:22-23`
-
-**Code:**
-```typescript
-const configPlugins = config.plugins || [];
-const pluginRegistry = await loadPlugins(globalPluginsDir, projectPluginsDir, configPlugins, workdir);
-```
-
-**Tests:** 2 tests in `config-resolution.test.ts`
-
----
-
-### ✅ AC2: Relative module paths resolved relative to project root
-
-**Implementation:** `src/plugins/loader.ts:173-186`
-
-**Code:**
-```typescript
-function resolveModulePath(modulePath: string, projectRoot?: string): string {
-  // Absolute paths and npm packages work as-is
-  if (path.isAbsolute(modulePath) || (!modulePath.startsWith("./") && !modulePath.startsWith("../"))) {
-    return modulePath;
-  }
-
-  // Relative paths resolved relative to project root
-  if (projectRoot) {
-    return path.resolve(projectRoot, modulePath);
-  }
-
-  return path.resolve(modulePath);
-}
-```
-
-**Tests:** 2 tests in `config-resolution.test.ts`
-- `./relative/path` resolution
-- `../parent/path` resolution
-
----
-
-### ✅ AC3: Absolute paths and npm package names work as-is
-
-**Implementation:** `src/plugins/loader.ts:175-176`
-
-**Logic:**
-- Absolute paths: `path.isAbsolute(modulePath)` → return as-is
-- npm packages: No `./` or `../` prefix → return as-is
-
-**Tests:** 2 tests in `config-resolution.test.ts`
-- Absolute path loading
-- npm package name handling
-
----
-
-### ✅ AC4: Clear error message when plugin module not found
-
-**Implementation:** `src/plugins/loader.ts:230-235`
-
-**Code:**
-```typescript
-if (errorMsg.includes("Cannot find module") || errorMsg.includes("ENOENT")) {
-  console.error(`[nax] Failed to load plugin module '${displayPath}'`);
-  console.error(`[nax] Attempted path: ${modulePath}`);
-  console.error(
-    "[nax] Ensure the module exists and the path is correct (relative paths are resolved from project root)",
-  );
-}
-```
-
-**Error Output Example:**
-```
-[nax] Failed to load plugin module './nonexistent/plugin.ts'
-[nax] Attempted path: /project/root/nonexistent/plugin.ts
-[nax] Ensure the module exists and the path is correct (relative paths are resolved from project root)
-```
-
-**Tests:** 2 tests in `config-resolution.test.ts`
-
----
-
-### ✅ AC5: Plugin-specific config passed to setup() function
-
-**Implementation:** `src/plugins/loader.ts:93, 215-221`
-
-**Code:**
-```typescript
-// Extract config from entry
-const validated = await loadAndValidatePlugin(resolvedModule, entry.config ?? {}, entry.module);
-
-// Inside loadAndValidatePlugin:
-if (validated.setup) {
-  try {
-    await validated.setup(config);
-  } catch (error) {
-    console.error(`[nax] Plugin '${validated.name}' setup failed:`, error);
-    return null;
-  }
-}
-```
-
-**Tests:** 2 tests in `config-resolution.test.ts`
-- Config passed correctly
-- Empty config when undefined
-
----
-
-## Test Coverage
-
-### Unit Tests: `test/integration/plugins/config-resolution.test.ts`
-
-```
-✅ AC1: plugins[] from config.json passed to loadPlugins
-  ✅ loads plugins from config array
-  ✅ loads multiple plugins from config array
-
-✅ AC2: Relative module paths resolved relative to project root
-  ✅ resolves ./relative/path from project root
-  ✅ resolves ../relative/path from project root
-
-✅ AC3: Absolute paths and npm packages work as-is
-  ✅ loads plugin with absolute path
-  ✅ treats non-relative paths as npm packages (doesn't crash)
-
-✅ AC4: Clear error message when plugin module not found
-  ✅ logs helpful error for missing relative path
-  ✅ logs helpful error for missing absolute path
-
-✅ AC5: Plugin-specific config passed to setup()
-  ✅ passes config object to plugin setup function
-  ✅ passes empty config object when config is undefined
-
-Total: 10 tests, 10 passing, 0 failing
-```
-
-### Integration Test: `test/integration/plugins/config-integration.test.ts`
-
-```
-✅ realistic scenario: project with relative plugin paths in config
-  - Creates project with custom-plugins/ directory
-  - Loads multiple plugins with relative paths
-  - Verifies configs passed to each plugin's setup()
-
-Total: 1 test, 1 passing, 0 failing
-```
-
-### Overall Plugin Test Suite
-
-```
-✅ 102 plugin-related tests pass
-✅ 0 failures
-✅ 177 expect() calls
-```
-
----
-
-## Example Usage
-
-### Config Format
-
-```json
-{
-  "version": 1,
-  "plugins": [
-    {
-      "module": "./custom-plugins/my-plugin.ts",
-      "config": {
-        "apiKey": "key-123",
-        "enabled": true
-      }
-    },
-    {
-      "module": "/absolute/path/to/plugin.js",
-      "config": {
-        "timeout": 5000
-      }
-    },
-    {
-      "module": "@org/nax-plugin-package"
-    }
-  ]
-}
-```
-
-### Path Resolution Examples
-
-| Config Path | Project Root | Resolved Path |
-|------------|--------------|---------------|
-| `./plugins/foo.ts` | `/home/user/project` | `/home/user/project/plugins/foo.ts` |
-| `../shared/bar.ts` | `/home/user/project` | `/home/user/shared/bar.ts` |
-| `/abs/path/baz.ts` | `/home/user/project` | `/abs/path/baz.ts` |
-| `@org/plugin` | `/home/user/project` | `@org/plugin` |
-
----
-
-## Files Involved
-
-### Implementation
-- `src/config/schema.ts` - PluginConfigEntry type definition
-- `src/config/loader.ts` - Config loading with plugins[] array
-- `src/plugins/loader.ts` - Plugin loading and path resolution
-- `src/execution/runner.ts` - Runner integration
-- `src/execution/run-lifecycle.ts` - Lifecycle integration
-- `src/cli/plugins.ts` - CLI command integration
-
-### Tests
-- `test/integration/plugins/config-resolution.test.ts` - AC verification (10 tests)
-- `test/integration/plugins/config-integration.test.ts` - E2E test (1 test)
-- `test/integration/cli-plugins.test.ts` - CLI integration (9 tests)
-
----
-
-## Conclusion
-
-✅ **US-007 is fully implemented and verified**
-
-All acceptance criteria are met with comprehensive test coverage. The implementation correctly:
-1. Reads plugins[] from config.json
-2. Resolves relative paths against project root
-3. Handles absolute paths and npm packages
-4. Provides clear error messages
-5. Passes plugin-specific config to setup()
-
-**No code changes required.** Implementation was completed in prior stories.

package/nax/features/plugin-integration/prd.json

@@ -1,208 +0,0 @@
-{
-  "project": "nax",
-  "feature": "plugin-integration",
-  "branchName": "feat/plugin-integration",
-  "createdAt": "2026-02-26T22:00:00Z",
-  "updatedAt": "2026-02-28T06:34:45Z",
-  "userStories": [
-    {
-      "id": "US-001",
-      "title": "Wire plugin loading into the runner startup",
-      "description": "The runner (src/execution/runner.ts) should call loadPlugins() at startup and store the resulting PluginRegistry in the pipeline context. Currently loadPlugins() exists in src/plugins/loader.ts but is never called. The runner should: 1) resolve global dir (~/.nax/plugins), project dir (<workdir>/nax/plugins), and config.plugins[] entries, 2) call loadPlugins(), 3) store the registry on the RunContext or pass it through the pipeline. On teardown (run end), call registry.teardownAll().",
-      "acceptanceCriteria": [
-        "Runner calls loadPlugins() during initialization before story loop starts",
-        "PluginRegistry is accessible from pipeline context (RunContext or similar)",
-        "registry.teardownAll() is called on both success and failure paths",
-        "If no plugins are found, an empty registry is used (no error)",
-        "Plugin loading errors are logged but do not abort the run"
-      ],
-      "dependencies": [],
-      "tags": [],
-      "status": "passed",
-      "passes": true,
-      "attempts": 1,
-      "escalations": [],
-      "priorErrors": []
-    },
-    {
-      "id": "US-002",
-      "title": "Context providers inject into agent prompts",
-      "description": "Before agent execution in the pipeline, call all registered context providers (registry.getContextProviders()) for the current story. Each provider returns {content, estimatedTokens, label}. Append provider content to the agent prompt under labeled sections, respecting a configurable token budget (default 2000 tokens total for all providers). If a provider throws, log warning and skip it. Add contextProviderTokenBudget to ExecutionConfig.",
-      "acceptanceCriteria": [
-        "All registered context providers are called before agent execution",
-        "Provider content is appended to the prompt under a markdown section with the provider's label",
-        "Total injected tokens respect the token budget (providers are added in order until budget exhausted)",
-        "Provider errors are caught, logged, and skipped without failing the story",
-        "Token budget is configurable via execution.contextProviderTokenBudget in config"
-      ],
-      "dependencies": [
-        "US-001"
-      ],
-      "tags": [],
-      "status": "passed",
-      "passes": true,
-      "attempts": 2,
-      "escalations": [],
-      "priorErrors": [
-        "Implemented directly with Claude outside nax. Marked passed on cleanup 2026-02-28."
-      ],
-      "routing": {
-        "complexity": "medium",
-        "modelTier": "powerful",
-        "testStrategy": "three-session-tdd-lite",
-        "reasoning": "three-session-tdd-lite: security-critical, strategy:lite"
-      }
-    },
-    {
-      "id": "US-003",
-      "title": "Review plugins run after built-in verification",
-      "description": "After the built-in review checks (typecheck/lint/test) pass in the pipeline's review stage (src/pipeline/stages/), call all registered reviewer plugins (registry.getReviewers()). Each reviewer's check(workdir, changedFiles) returns {passed, output, exitCode?}. If any reviewer fails, treat it the same as a built-in check failure (triggers retry/escalation). Include reviewer output in the story result for debugging.",
-      "acceptanceCriteria": [
-        "Plugin reviewers run after built-in checks pass",
-        "Each reviewer receives the workdir and list of changed files",
-        "Reviewer failure triggers the same retry/escalation as built-in check failures",
-        "Reviewer output is included in the story execution result",
-        "If a reviewer throws an exception, it counts as a failure with the exception message as output",
-        "Multiple reviewers run sequentially; first failure short-circuits remaining reviewers"
-      ],
-      "dependencies": [
-        "US-001"
-      ],
-      "tags": [],
-      "status": "passed",
-      "passes": true,
-      "attempts": 2,
-      "escalations": [],
-      "priorErrors": [
-        "Implemented directly with Claude outside nax. Marked passed on cleanup 2026-02-28."
-      ],
-      "routing": {
-        "complexity": "medium",
-        "modelTier": "powerful",
-        "testStrategy": "three-session-tdd-lite",
-        "reasoning": "three-session-tdd-lite: strategy:lite"
-      }
-    },
-    {
-      "id": "US-004",
-      "title": "Reporter plugins receive lifecycle events",
-      "description": "Fire reporter events at the appropriate points in the runner loop: onRunStart when the run begins, onStoryComplete after each story finishes (success or failure), onRunEnd when the run completes. All reporter calls are fire-and-forget (errors logged, never block pipeline). Build event objects from existing run state (RunStartEvent, StoryCompleteEvent, RunEndEvent as defined in src/plugins/types.ts).",
-      "acceptanceCriteria": [
-        "onRunStart fires once at run start with runId, feature, totalStories, startTime",
-        "onStoryComplete fires after each story with storyId, status, durationMs, cost, tier, testStrategy",
-        "onRunEnd fires once at run end with runId, totalDurationMs, totalCost, storySummary counts",
-        "Reporter errors are caught and logged but never block execution",
-        "Multiple reporters all receive events (not short-circuited on error)",
-        "Events fire even when the run fails or is aborted (onRunEnd still fires)"
-      ],
-      "dependencies": [
-        "US-001"
-      ],
-      "tags": [],
-      "status": "passed",
-      "passes": true,
-      "attempts": 1,
-      "escalations": [],
-      "priorErrors": [
-        "Implemented directly with Claude outside nax. Marked passed on cleanup 2026-02-28."
-      ],
-      "routing": {
-        "complexity": "medium",
-        "modelTier": "powerful",
-        "testStrategy": "three-session-tdd-lite",
-        "reasoning": "three-session-tdd-lite: strategy:lite"
-      }
-    },
-    {
-      "id": "US-005",
-      "title": "Plugin routing strategies integrate into router chain",
-      "description": "Insert plugin routing strategies (registry.getRouters()) before the built-in router in the routing chain (src/routing/). When routing a story, iterate plugin routers first; if any returns a routing decision, use it. If all plugin routers return null/undefined, fall back to the built-in strategy. This allows plugins to override routing for specific stories (e.g., always route security-tagged stories to premium).",
-      "acceptanceCriteria": [
-        "Plugin routers are tried before the built-in routing strategy",
-        "First plugin router that returns a non-null result wins",
-        "If all plugin routers return null, built-in strategy is used as fallback",
-        "Plugin routers receive the same story context as built-in routers",
-        "Router errors are caught and logged; fallback to next router in chain"
-      ],
-      "dependencies": [
-        "US-001"
-      ],
-      "tags": [],
-      "status": "passed",
-      "passes": true,
-      "attempts": 2,
-      "escalations": [],
-      "priorErrors": [
-        "Implemented directly with Claude outside nax. Marked passed on cleanup 2026-02-28."
-      ]
-    },
-    {
-      "id": "US-006",
-      "title": "CLI 'nax plugins list' command",
-      "description": "Add a 'plugins' subcommand to the CLI (src/cli/) with a 'list' action. It should: 1) load plugins from global + project + config sources (reuse loadPlugins), 2) display a table with name, version, provides[], and source (global/project/config), 3) exit cleanly. If no plugins found, print a helpful message pointing to docs.",
-      "acceptanceCriteria": [
-        "Running 'nax plugins list' prints a formatted table of installed plugins",
-        "Each row shows: plugin name, version, extension types provided, source location",
-        "If no plugins found, prints 'No plugins installed' with help text",
-        "Works in both project directory and outside (global-only scan outside project)",
-        "Exit code 0 on success"
-      ],
-      "dependencies": [],
-      "tags": [],
-      "status": "passed",
-      "passes": true,
-      "attempts": 1,
-      "escalations": [],
-      "priorErrors": []
-    },
-    {
-      "id": "US-007",
-      "title": "Read plugin config entries from nax config.json",
-      "description": "The config loader (src/config/loader.ts) already supports a plugins[] array in the schema. Ensure that when config is loaded, the plugins[] entries are passed to loadPlugins() as the configPlugins parameter. Each entry has {module, config?}. Validate that module paths resolve correctly (relative to project root). Add a helpful error message if a configured plugin module cannot be found.",
-      "acceptanceCriteria": [
-        "plugins[] from config.json are passed to loadPlugins() as configPlugins parameter",
-        "Relative module paths in plugins[].module are resolved relative to project root",
-        "Absolute module paths and npm package names work as-is",
-        "If a plugin module cannot be found, a clear error message is logged with the path tried",
-        "Plugin-specific config (plugins[].config) is passed to the plugin's setup() function"
-      ],
-      "dependencies": [],
-      "tags": [],
-      "status": "passed",
-      "passes": true,
-      "attempts": 1,
-      "escalations": [],
-      "priorErrors": []
-    },
-    {
-      "id": "US-008",
-      "title": "Sample console reporter plugin with tests",
-      "description": "Create a sample reporter plugin at examples/plugins/console-reporter/ that demonstrates the plugin API. It should: 1) implement IReporter with onRunStart (print banner), onStoryComplete (print status line), onRunEnd (print summary table), 2) have a setup() that reads config.verbose for detail level, 3) include unit tests in the same directory. This serves as both documentation and a smoke test for the plugin system.",
-      "acceptanceCriteria": [
-        "Plugin exports a valid NaxPlugin with provides: ['reporter']",
-        "onRunStart prints a run banner with feature name and story count",
-        "onStoryComplete prints a status line (\u2713/\u2717) with story ID, tier, duration, cost",
-        "onRunEnd prints a summary table with total stories, pass/fail counts, total cost, total duration",
-        "setup() reads config.verbose (boolean, default false) for extra detail",
-        "Plugin passes validatePlugin() from src/plugins/validator.ts",
-        "Unit tests verify all three event handlers produce expected output"
-      ],
-      "dependencies": [
-        "US-004",
-        "US-007"
-      ],
-      "tags": [],
-      "status": "passed",
-      "passes": true,
-      "attempts": 1,
-      "escalations": [],
-      "priorErrors": [
-        "Implemented directly with Claude outside nax. Marked passed on cleanup 2026-02-28."
-      ]
-    }
-  ],
-  "analyzeConfig": {
-    "maxStories": 15,
-    "granularity": "medium"
-  }
-}

package/nax/features/plugin-integration/progress.txt

@@ -1,5 +0,0 @@
-[2026-02-26T16:06:18.213Z] US-001 — FAILED — Wire plugin loading into the runner startup — All tiers exhausted
-[2026-02-26T16:18:45.006Z] US-006 — FAILED — CLI 'nax plugins list' command — All tiers exhausted
-[2026-02-26T16:27:59.795Z] US-007 — FAILED — Read plugin config entries from nax config.json — All tiers exhausted
-[2026-02-26T17:26:43.751Z] US-002 — FAILED — Context providers inject into agent prompts — All tiers exhausted
-[2026-02-26T17:27:52.898Z] US-003 — FAILED — Review plugins run after built-in verification — All tiers exhausted