@tailor-platform/erp-kit 0.8.0 → 0.9.0

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # @tailor-platform/erp-kit
 
+## 0.9.0
+
+### Minor Changes
+
+- afa2455: - Add seed:validate script and skill step to scaffold template
+  - Add vitest to module scaffold template
+  - Add version self-checking to all erp-kit skills
+  - Fix command return properties to use full model names across all modules
+  - Fix tree-shaking by adding sideEffects annotations to all module defineModule exports
+  - Fix scaffold app integration tests
+  - Fix inactive users being able to access the scaffold app
+  - Fix skills CLI version check, remove erp-kit-shared dependency
+  - Refactor audit pages out of user-management directory into standalone location
+  - Remove audit dependency from coa-management module
+
 ## 0.8.0
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tailor-platform/erp-kit",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "description": "Opinionated ERP toolkit for building business applications on Tailor Platform",
   "license": "MIT",
   "bin": {

package/skills/erp-kit-app-1-requirements/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-app-1-requirements
 description: Create Tier 1-2 documentation (requirements, actors, business-flow) for an application. Use when starting a new application or documenting high-level requirements and workflows.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Application Requirement Analysis Workflow
 
 Create Tier 1-2 documentation: Requirements, Actors, and Business Flows.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## Progress Logging
 
 Log to the audit trail at every checkpoint. See [erp-kit-app-shared/references/progress-protocol.md](../erp-kit-app-shared/references/progress-protocol.md) for the full protocol.

package/skills/erp-kit-app-2-requirements-review/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-app-2-requirements-review
 description: Review requirements quality and documentation consistency for applications. Use after creating Tier 1-2 documentation (requirements, actors, business-flow) with erp-kit-app-1-requirements.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Requirements Review
 
 Review **requirements quality** and **documentation consistency** for an application's Tier 1-2 documentation.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## Progress Logging
 
 Log to the audit trail at every checkpoint. See [erp-kit-app-shared/references/progress-protocol.md](../erp-kit-app-shared/references/progress-protocol.md) for the full protocol.

package/skills/erp-kit-app-3-plan/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-app-3-plan
 description: Create Tier 3-4 documentation (screens, resolvers) by breaking down business flows and existing stories. Use after completing requirements review with erp-kit-app-2-requirements-review.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Business Flow Breakdown to Stories, Screens, and Resolvers
 
 Convert Tier 2 business flows and stories into Tier 3 (screens) and Tier 4 (resolvers) documentation using parallel extraction agents.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## Progress Logging
 
 Log to the audit trail at every checkpoint. See [erp-kit-app-shared/references/progress-protocol.md](../erp-kit-app-shared/references/progress-protocol.md) for the full protocol.

package/skills/erp-kit-app-4-plan-review/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-app-4-plan-review
 description: Review parity between Tier 2 (business flows, actors, stories) and Tier 3-4 (screens, resolvers). Use after creating plan documentation with erp-kit-app-3-plan to validate completeness.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Documentation Parity Review
 
 Review **documentation consistency** across Tier 2 (business flows, actors, stories), Tier 3 (screens), and Tier 4 (resolvers) documentation.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## Progress Logging
 
 Log to the audit trail at every checkpoint. See [erp-kit-app-shared/references/progress-protocol.md](../erp-kit-app-shared/references/progress-protocol.md) for the full protocol.

package/skills/erp-kit-app-5-impl-backend/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-app-5-impl-backend
 description: Implement backend code for applications using erp-kit modules. Use after completing plan review with erp-kit-app-4-plan-review. Triggers when implementing backend resolvers, wiring modules, configuring applications, or when the user mentions implementing backend, writing resolvers, or connecting erp-kit modules.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Application Backend Implementation
 
 Implement backend resolvers and application configuration for an application, driven by Tier 1-4 documentation (actors, business flows, stories, screens, resolvers).
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## Progress Logging
 
 Log to the audit trail at every checkpoint. See [erp-kit-app-shared/references/progress-protocol.md](../erp-kit-app-shared/references/progress-protocol.md) for the full protocol.
@@ -117,6 +123,7 @@ After resolvers are done, implement the story integration test stubs generated i
 - **Seed data** (`seed/`) — `exec.mjs` runner + `data/*.jsonl` (records) and `data/*.schema.ts` (validation).
   1. **Module seed** — Run `pnpm erp-kit app generate seed -p <app-path>` to generate module-provided defaults (currencies, units, UoM categories, exchange rates). This writes JSONL files to `seed/data/`, skipping files that already exist.
   2. **App-specific seed** — Manually create seed records for permissions, roles, test users, and domain-specific data. Seeded users must have concrete permission keys required by the wired modules.
+  3. **Validate seed** — Run `pnpm run seed:validate` and fix any errors before proceeding.
 
 ### Phase 6: Deploy Backend & Next Steps
 

package/skills/erp-kit-app-6-impl-frontend/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-app-6-impl-frontend
 description: Implement frontend code for applications. Use after deploying the backend with erp-kit-app-5-impl-backend. Triggers when implementing frontend pages, creating React components from screen specs, or when the user mentions implementing frontend, creating pages, or building UI for an application.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Application Frontend Implementation
 
 Implement frontend pages for an application, driven by screen spec documentation and a deployed backend.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## Progress Logging
 
 Log to the audit trail at every checkpoint. See [erp-kit-app-shared/references/progress-protocol.md](../erp-kit-app-shared/references/progress-protocol.md) for the full protocol.

package/skills/erp-kit-app-7-impl-review/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-app-7-impl-review
 description: Review implementation parity between documentation and code for applications. Use after frontend implementation (step 6) to validate code matches documentation.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Implementation Parity Review
 
 Review **implementation consistency** between Tier 3-4 documentation and actual backend/frontend code.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## Progress Logging
 
 Log to the audit trail at every checkpoint. See [erp-kit-app-shared/references/progress-protocol.md](../erp-kit-app-shared/references/progress-protocol.md) for the full protocol.

package/skills/erp-kit-app-shared/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: erp-kit-app-shared
 description: Shared references for erp-kit app skills. Not invoked directly — referenced by erp-kit-app-1 through erp-kit-app-7.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # erp-kit-app-shared

package/skills/erp-kit-mock-scenario/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-mock-scenario
 description: Scaffold a new Mockoon mock scenario with CRUD routes, error scenarios, and registry updates
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Mock Scenario Scaffolder
 
 Generate a complete Mockoon mock API config for a new provider scenario and wire it into the registry.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## Workflow
 
 ### Step 1: Identify target API

package/skills/erp-kit-module-1-requirements/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-module-1-requirements
 description: Create ERP module requirements and feature documentation. Use when starting a new module, defining requirements, scoping features, or designing module architecture. Guides collaborative research, scoping, and iterative feature breakdown.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Module Requirements Workflow
 
 Autonomous workflow for creating ERP module requirements. Uses parallel agents for research, then automatically decides scope based on recommendations.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## Workflow
 
 ```

package/skills/erp-kit-module-2-requirements-review/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-module-2-requirements-review
 description: Review requirements quality and module boundary consistency. Use after creating requirements (step 1) to validate best practices and cross-module boundaries.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Requirements Review
 
 Review **requirements quality** and **module boundary consistency** for a module.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## When to Use
 
 - After writing module requirements and feature documentation (step 1)

package/skills/erp-kit-module-3-plan/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-module-3-plan
 description: Create implementation plan by breaking down feature specs into model, command, and query documentation. Use after requirements review (step 2) to plan the implementation structure.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Feature Breakdown to Model/Command/Query Docs
 
 Convert feature specifications into structured model, command, and query documentation. The main agent creates the plan and populates scaffolded docs, then parallel subagents refine each doc type.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## When to Use
 
 - User has feature specs (e.g., `docs/features/*.md`) and wants implementation docs

package/skills/erp-kit-module-3-update-plan/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-module-3-update-plan
 description: Update model/command/query documentation based on plan review (step 4) feedback. Use after erp-kit-module-4-plan-review returns NEEDS CHANGES to apply targeted fixes without re-creating existing docs.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Fix Plan Documentation from Review Feedback
 
 Apply targeted fixes to model, command, and query documentation based on plan review feedback. Unlike erp-kit-module-3-plan which creates docs from scratch, this skill reads the review report and applies only the necessary changes.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## When to Use
 
 - After erp-kit-module-4-plan-review returns **NEEDS CHANGES**

package/skills/erp-kit-module-4-plan-review/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-module-4-plan-review
 description: Review parity between feature documentation and command/model/query documentation. Use after creating implementation plan (step 3) to validate completeness.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Feature Parity Review
 
 Review **documentation consistency** between feature specs and command/model/query docs.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## When to Use
 
 - After writing feature documentation, check for gaps in command/model/query documentation

package/skills/erp-kit-module-5-impl/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-module-5-impl
 description: Implement features in modules using TDD. Use after plan review (step 4) to implement database models, commands, and queries with test-driven development.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # TDD Implementation for Module Development
 
 Implement features in modules using Test-Driven Development with per-item agent delegation.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## When to Use
 
 - Implementing new domain commands in any module

package/skills/erp-kit-module-6-impl-review/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-module-6-impl-review
 description: Review implementation parity between documentation and code. Use after TDD implementation (step 5) to validate code matches documentation.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Implementation Parity Review
 
 Review **implementation consistency** between documentation and actual code.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## When to Use
 
 - After TDD implementation (step 4), verify it matches documentation

package/skills/erp-kit-module-shared/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: erp-kit-module-shared
 description: Shared references for erp-kit module skills. Not invoked directly — referenced by erp-kit-module-1 through erp-kit-module-6.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # erp-kit-module-shared

package/skills/erp-kit-module-shared/references/commands.md

@@ -179,6 +179,9 @@ const units = await db
 
 - **Error handling**: Use `ok()` / `err()` from `@tailor-platform/erp-kit/module` — do not throw
 - **Validation**: Check referenced entities exist before operating, return `err()` if not found
+- **Return property naming**: Use the full model name in camelCase as the return property key — never abbreviate. This keeps property names unambiguous across modules.
+  - `return ok({ stockMovement: ... })` — not `movement`
+  - `return ok({ inventoryAdjustment: ... })` — not `adjustment`
 
 ## Update Command Input Type
 

package/skills/erp-kit-update/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: erp-kit-update
 description: Route requirements changes to the correct erp-kit skill. Use when requirements change midway — adding features, modifying business flows, updating screens, changing module specs, or when unsure which erp-kit skill to re-run after a change.
+metadata:
+  erp-kit-version: "0.9.0"
 ---
 
 # Requirements Update Router
 
 Route mid-workflow changes to the correct erp-kit skill. Dynamically discovers available skills — no hardcoded routing tables.
 
+## Version Check
+
+Run `npx erp-kit --version` and compare against this skill's `metadata.erp-kit-version`. If they differ, the local skills are outdated — tell the user to run `pnpm erp-kit update skills` and stop.
+
 ## Workflow
 
 ```

package/src/modules/accounting/command/assignProfitCenterToHierarchyNode.test.ts

@@ -29,7 +29,7 @@ describe("assignProfitCenterToHierarchyNode", () => {
     );
 
     const value = expectOk(result);
-    expect(value.assignment).toEqual(baseProfitCenterHierarchyAssignment);
+    expect(value.profitCenterHierarchyAssignment).toEqual(baseProfitCenterHierarchyAssignment);
     expect(spies.insert).toHaveBeenCalled();
     expect(spies.update).not.toHaveBeenCalled();
   });
@@ -56,7 +56,7 @@ describe("assignProfitCenterToHierarchyNode", () => {
     );
 
     const value = expectOk(result);
-    expect(value.assignment.hierarchyNodeId).toBe(childProfitCenterNode.id);
+    expect(value.profitCenterHierarchyAssignment.hierarchyNodeId).toBe(childProfitCenterNode.id);
     expect(spies.update).toHaveBeenCalled();
     expect(spies.insert).not.toHaveBeenCalled();
   });
@@ -90,7 +90,7 @@ describe("assignProfitCenterToHierarchyNode", () => {
     );
 
     const value = expectOk(result);
-    expect(value.assignment.hierarchyNodeId).toBe(secondHierarchyNode.id);
+    expect(value.profitCenterHierarchyAssignment.hierarchyNodeId).toBe(secondHierarchyNode.id);
     expect(spies.insert).toHaveBeenCalled();
     expect(spies.update).not.toHaveBeenCalled();
   });

package/src/modules/accounting/command/assignProfitCenterToHierarchyNode.ts

@@ -67,5 +67,5 @@ export async function run(
         .returningAll()
         .executeTakeFirstOrThrow();
 
-  return ok({ assignment });
+  return ok({ profitCenterHierarchyAssignment: assignment });
 }

package/src/modules/accounting/command/createCostCenterHierarchyNode.test.ts

@@ -83,7 +83,7 @@ describe("createCostCenterHierarchyNode", () => {
     );
 
     const value = expectOk(result);
-    expect(value.node).toEqual(rootCostCenterNode);
+    expect(value.costCenterHierarchyNode).toEqual(rootCostCenterNode);
   });
 
   it("creates child node with correct computed level", async () => {
@@ -105,8 +105,8 @@ describe("createCostCenterHierarchyNode", () => {
     );
 
     const value = expectOk(result);
-    expect(value.node).toEqual(childCostCenterNode);
-    expect(value.node.level).toBe(1);
+    expect(value.costCenterHierarchyNode).toEqual(childCostCenterNode);
+    expect(value.costCenterHierarchyNode.level).toBe(1);
   });
 
   it("returns error when node references itself as parent", async () => {

package/src/modules/accounting/command/createCostCenterHierarchyNode.ts

@@ -113,5 +113,5 @@ export async function run(
     .returningAll()
     .executeTakeFirst();
 
-  return ok({ node: node! });
+  return ok({ costCenterHierarchyNode: node! });
 }

package/src/modules/accounting/command/moveCostCenterHierarchyNode.test.ts

@@ -104,7 +104,7 @@ describe("moveCostCenterHierarchyNode", () => {
     );
 
     const value = expectOk(result);
-    expect(value.node).toEqual(movedNode);
+    expect(value.costCenterHierarchyNode).toEqual(movedNode);
   });
 
   it("updates level based on new parent level", async () => {
@@ -130,6 +130,6 @@ describe("moveCostCenterHierarchyNode", () => {
     );
 
     const value = expectOk(result);
-    expect(value.node.level).toBe(1);
+    expect(value.costCenterHierarchyNode.level).toBe(1);
   });
 });

package/src/modules/accounting/command/moveCostCenterHierarchyNode.ts

@@ -77,5 +77,5 @@ export async function run(
     .returningAll()
     .executeTakeFirst();
 
-  return ok({ node: updatedNode! });
+  return ok({ costCenterHierarchyNode: updatedNode! });
 }

package/src/modules/accounting/module.ts

@@ -190,6 +190,7 @@ export interface DefineModuleParams<
   };
 }
 
+/* @__NO_SIDE_EFFECTS__ */
 export const defineModule = <
   const CeF extends Record<string, TailorAnyDBField> = EmptyFields,
   const CcF extends Record<string, TailorAnyDBField> = EmptyFields,

package/src/modules/business-partner/command/createPartnerBankAccount.test.ts

@@ -67,7 +67,7 @@ describe("createPartnerBankAccount", () => {
 
     expect(result.ok).toBe(true);
     if (result.ok) {
-      expect(result.value.bankAccount).toEqual(baseDefaultBankAccount);
+      expect(result.value.partnerBankAccount).toEqual(baseDefaultBankAccount);
     }
   });
 
@@ -204,7 +204,7 @@ describe("createPartnerBankAccount", () => {
 
     expect(result.ok).toBe(true);
     if (result.ok) {
-      expect(result.value.bankAccount.partnerId).toBe("partner-1");
+      expect(result.value.partnerBankAccount.partnerId).toBe("partner-1");
     }
   });
 
@@ -221,7 +221,7 @@ describe("createPartnerBankAccount", () => {
 
     expect(result.ok).toBe(true);
     if (result.ok) {
-      expect(result.value.bankAccount.partnerId).toBe("partner-3");
+      expect(result.value.partnerBankAccount.partnerId).toBe("partner-3");
     }
   });
 

package/src/modules/business-partner/command/createPartnerBankAccount.ts

@@ -110,5 +110,5 @@ export async function run<CF extends Record<string, unknown>>(
     .returningAll()
     .executeTakeFirstOrThrow();
 
-  return ok({ bankAccount });
+  return ok({ partnerBankAccount: bankAccount });
 }

package/src/modules/business-partner/module.ts

@@ -92,6 +92,7 @@ export interface DefineModuleParams<
   };
 }
 
+/* @__NO_SIDE_EFFECTS__ */
 export const defineModule = <
   const BPF extends Record<string, TailorAnyDBField> = EmptyFields,
   const PRF extends Record<string, TailorAnyDBField> = EmptyFields,

package/src/modules/coa-management/command/activateAccount.test.ts

@@ -107,19 +107,4 @@ describe("activateAccount", () => {
       expect(result.value.account.status).toBe("ACTIVE");
     }
   });
-
-  it("emits audit event recording status transition from DRAFT to ACTIVE", async () => {
-    const { db, spies } = createMockDb<Transaction>();
-    const activated = { ...baseDraftAccount, status: "ACTIVE" };
-    spies.select.mockReturnValueOnce(baseDraftAccount).mockReturnValueOnce(baseActiveCoa);
-    spies.update.mockReturnValue(activated);
-
-    const result = await run(db, { id: baseDraftAccount.id }, ctx);
-
-    // Audit event is emitted as part of successful activation
-    expect(result.ok).toBe(true);
-    if (result.ok) {
-      expect(result.value.account.status).toBe("ACTIVE");
-    }
-  });
 });

package/src/modules/coa-management/command/activateAccount.ts

@@ -1,4 +1,3 @@
-import { randomUUID } from "node:crypto";
 import type { Transaction } from "../generated/kysely-tailordb";
 import {
   AccountNotFoundError,
@@ -12,35 +11,13 @@ export interface ActivateAccountInput {
   from?: string[];
 }
 
-export interface AuditCommands {
-  logAuditEvent: (
-    db: Transaction,
-    input: {
-      eventId: string;
-      actorType: string;
-      actorId: string;
-      entityType: string;
-      entityId: string;
-      operationType: string;
-      companyId?: string;
-      changes: { fieldName: string; oldValue?: unknown; newValue?: unknown }[];
-    },
-    ctx: CommandContext,
-  ) => Promise<{ ok: true; value: unknown }>;
-}
-
 /**
  * Function: activateAccount
  *
  * Transitions a GL account from DRAFT to ACTIVE status, making it eligible
  * to receive journal postings from downstream modules.
  */
-export async function run(
-  db: Transaction,
-  input: ActivateAccountInput,
-  ctx: CommandContext,
-  auditCommands?: AuditCommands,
-) {
+export async function run(db: Transaction, input: ActivateAccountInput, _ctx: CommandContext) {
   const { id, from = ["DRAFT"] } = input;
 
   // 1. Find account with forUpdate
@@ -83,23 +60,5 @@ export async function run(
     .returningAll()
     .executeTakeFirst();
 
-  // 6. Emit audit event
-  if (auditCommands) {
-    await auditCommands.logAuditEvent(
-      db,
-      {
-        eventId: randomUUID(),
-        actorType: "USER",
-        actorId: ctx.actorId,
-        entityType: "Account",
-        entityId: id,
-        operationType: "UPDATE",
-        companyId: coa.companyId,
-        changes: [{ fieldName: "status", oldValue: account.status, newValue: "ACTIVE" }],
-      },
-      ctx,
-    );
-  }
-
   return ok({ account: updated! });
 }