develop-invokta-project

# Develop This Action Engine ## Establish the contract 1. Read `AGENTS.md`, `README.md`, and the existing capability and engine tests. 2. Identify the domain action, public capability ID, input, output, access rule, annotations, timeout, and observable errors affected by the change. 3. Treat capability IDs, schemas, access behavior, and adapter-visible results as compatibility surfaces. Request an explicit decision before breaking one. ## Keep one architecture - Define domain actions with `defineCapability` and explicit input, output, access, and execution contracts. - Inject models, providers, repositories, tools, and policy checks through engine-owned factories or closures. - Register capabilities under literal domain-oriented IDs in `src/engine.ts`. - Keep every execution channel on `engine.invoke`; never call a capability's `run` directly. - Keep business logic out of `src/direct.ts`, `src/cli.ts`, `src/mcp-stdio.ts`, `src/mcp-http.ts`. - Do not add a service locator, runtime registry, plugin discovery, workflow engine, or adapter-specific capability implementation. - Preserve fail-closed authentication in `src/http-auth.ts`; never add a development bypass. ## Deliver the change 1. Add or update an engine-level test that invokes the capability and fails for the missing behavior. 2. Implement the smallest capability, dependency, composition-root, or adapter wiring change that makes the test pass. 3. Cover invalid input, denied access, output validation, cancellation, or dependency failure when relevant to the contract. 4. Keep direct invocation, CLI, MCP stdio, and MCP HTTP behavior consistent by testing the shared engine boundary rather than duplicating handlers. 5. Update project documentation when commands, configuration, capability IDs, or public behavior change. 6. Run `npm run check` and resolve every type, test, formatting, and build failure before completion.