@7365admin1/core 3.47.1-staging.124 → 3.47.1-staging.126

package/.changeset/console-audit-client-status.md

@@ -0,0 +1,20 @@
+---
+"@7365admin1/core": patch
+---
+
+Suspending or reactivating a client is now recorded in the console audit trail.
+
+The audit trail (`console-audit`) already carried `client.suspended` and
+`client.reactivated` with their labels and their allow-listed fields, but nothing
+wrote them: `organization.controller.ts` was deliberately left unhooked while the
+suspend work was still an open PR. Now that it has landed, `updateStatus` records
+one row per status change - the direction taken from the status that was actually
+written, the actor taken from the owner guard's return value and never from the
+request body, and only `status` kept from the change.
+
+The row is written after the status has changed and before the reply, the same
+order as every other recorded action, so a row can never describe something that
+did not happen. `recordConsoleAction` still swallows its own failures, so a lost
+audit row cannot undo a suspension.
+
+`client.created` stays unconnected on purpose and its reminder is unchanged.

package/.github/workflows/main.yml

@@ -15,3 +15,13 @@ jobs:
           cache: "yarn"
       - run: yarn install
       - run: yarn lint && yarn build
+      # Separate step so a red suite is attributable at a glance rather than
+      # buried in a chained command.
+      #
+      # `yarn test` only runs `test/*.test.mjs` — pure functions and assertions
+      # read from source files. None of them opens a database, a Redis or a
+      # network socket, so nothing here needs a secret or a service container.
+      #
+      # `yarn test:e2e` is deliberately NOT run: it needs a live database. It
+      # stays a local/manual check.
+      - run: yarn test