@clipboard-health/ai-rules 2.14.14 → 2.14.16

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clipboard-health/ai-rules",
-  "version": "2.14.14",
+  "version": "2.14.16",
   "description": "Pre-built AI agent rules for consistent coding standards.",
   "keywords": [
     "ai",

package/rules/backend/architecture.md

@@ -12,6 +12,7 @@ All NestJS microservices follow a three-tier layered architecture:
 │  Logic (NestJS services, message publishers, background jobs)   │
 │  - ALL business logic; works with DOs only                      │
 │  - Knows nothing about HTTP or database specifics               │
+│  - Can depend on other modules' logic (cross-module composition)│
 ├─────────────────────────────────────────────────────────────────┤
 │  Data (Data repositories, gateways)                             │
 │  - Database via ORM (Prisma/Mongoose), DAO ↔ DO translation     │

package/rules/backend/restApiDesign.md

@@ -96,7 +96,7 @@ GET /shifts?filter[verified]=true&sort=startDate,-urgency&page[cursor]=abc&page[
 Use helpers from `@clipboard-health/contract-core` instead of raw Zod methods in contract packages:
 
 - Use `dateTimeSchema()` for date fields — not `z.coerce.date()` (too permissive), `z.string().datetime()` (gives string, not Date), or `z.date()` (won't parse JSON strings)
-- Use `requiredEnumWithFallback`/`optionalEnumWithFallback` for enums — not bare `z.enum()` (breaks old mobile clients when new values are added) or `z.enum().catch()` (doesn't compose with `.optional()`)
+- Use `requiredEnumWithFallback`/`optionalEnumWithFallback` for enums — not bare `z.enum()` (breaks old mobile clients when new values are added) or `z.enum().catch()` (doesn't compose with `.optional()`). These helpers automatically append `ENUM_FALLBACK` (`"UNRECOGNIZED_"`) to the output type — do not pass a fallback value
 - Do not use `.default()` in contracts — client and server can drift on defaults. Set defaults in the service layer.
 - Name schemas with a `Schema` suffix: `ShiftAttributeSchema`, not `shiftAttribute`
 - Export at the DTO boundary (request/response schemas), not every intermediate schema

package/scripts/constants.js

@@ -6,7 +6,6 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.PROFILES = exports.CATEGORIES = exports.RULE_FILES = exports.FILES = exports.PATHS = void 0;
 exports.toRulePath = toRulePath;
 const node_path_1 = __importDefault(require("node:path"));
-// Root directory of the ai-rules package
 const PACKAGE_ROOT = node_path_1.default.join(__dirname, "..");
 exports.PATHS = {
     packageRoot: PACKAGE_ROOT,