@carecard/validate 3.6.0 → 3.6.1

package/.agents/skills/carecard-workspace-standards/SKILL.md

@@ -5,6 +5,10 @@ description: 'Follow the shared SO_CareCardCa/CareCard workspace coding, testing
 
 # CareCard Workspace Standards
 
+Non-negotiable TDD rule: Always write the failing test first, run it to confirm it fails for the intended reason, then implement the code and rerun the test until it passes. Test Driven Development is required for all coding work and must not be skipped. For documentation- or skill-only edits, add or update the relevant validation check before changing the prose.
+
+Non-negotiable code organization rule: Functions with the same or equivalent behavior must use the same or clearly corresponding descriptive names across CareCard repositories, and equivalent functionality must live in files with the same names within each repository's established architecture. No backward compatibility names, aliases, or duplicate locations are allowed.
+
 ## Purpose
 
 Use before modifying, testing, reviewing, or debugging any CareCard workspace repository or cross-repository contract.

package/.agents/skills/github-pr-create-update/SKILL.md

@@ -5,6 +5,10 @@ description: 'Use only when the user explicitly asks for remote Git or GitHub PR
 
 # Pull Request Create
 
+Non-negotiable TDD rule: Always write the failing test first, run it to confirm it fails for the intended reason, then implement the code and rerun the test until it passes. Test Driven Development is required for all coding work and must not be skipped. For documentation- or skill-only edits, add or update the relevant validation check before changing the prose.
+
+Non-negotiable code organization rule: Functions with the same or equivalent behavior must use the same or clearly corresponding descriptive names across CareCard repositories, and equivalent functionality must live in files with the same names within each repository's established architecture. No backward compatibility names, aliases, or duplicate locations are allowed.
+
 ## Purpose
 
 After the user explicitly asks for remote Git or GitHub PR work, create,

package/.agents/skills/github-pr-merge-cleanup/SKILL.md

@@ -5,6 +5,10 @@ description: 'Use only when the user explicitly asks for remote Git or GitHub PR
 
 # Pull Request Merge Close
 
+Non-negotiable TDD rule: Always write the failing test first, run it to confirm it fails for the intended reason, then implement the code and rerun the test until it passes. Test Driven Development is required for all coding work and must not be skipped. For documentation- or skill-only edits, add or update the relevant validation check before changing the prose.
+
+Non-negotiable code organization rule: Functions with the same or equivalent behavior must use the same or clearly corresponding descriptive names across CareCard repositories, and equivalent functionality must live in files with the same names within each repository's established architecture. No backward compatibility names, aliases, or duplicate locations are allowed.
+
 ## Purpose
 
 After the user explicitly asks for remote Git or GitHub PR work, push the

package/.agents/skills/logged-in-user-profile-page/SKILL.md

@@ -5,6 +5,10 @@ description: 'Use when changing shared validation behavior for app-dashboard log
 
 # Logged-In User Profile Page
 
+Non-negotiable TDD rule: Always write the failing test first, run it to confirm it fails for the intended reason, then implement the code and rerun the test until it passes. Test Driven Development is required for all coding work and must not be skipped. For documentation- or skill-only edits, add or update the relevant validation check before changing the prose.
+
+Non-negotiable code organization rule: Functions with the same or equivalent behavior must use the same or clearly corresponding descriptive names across CareCard repositories, and equivalent functionality must live in files with the same names within each repository's established architecture. No backward compatibility names, aliases, or duplicate locations are allowed.
+
 ## Scope
 
 Use this skill inside `pkg-validate` when dashboard profile/settings behavior

package/.agents/skills/npm-package-flow/SKILL.md

@@ -5,6 +5,10 @@ description: 'Use in pkg-* repositories when publishable package code changes re
 
 # npm Package Flow
 
+Non-negotiable TDD rule: Always write the failing test first, run it to confirm it fails for the intended reason, then implement the code and rerun the test until it passes. Test Driven Development is required for all coding work and must not be skipped. For documentation- or skill-only edits, add or update the relevant validation check before changing the prose.
+
+Non-negotiable code organization rule: Functions with the same or equivalent behavior must use the same or clearly corresponding descriptive names across CareCard repositories, and equivalent functionality must live in files with the same names within each repository's established architecture. No backward compatibility names, aliases, or duplicate locations are allowed.
+
 ## Purpose
 
 Use this skill in a `pkg-*` repository when package code changes need to be

package/.agents/skills/pkg-validate-validation-library/SKILL.md

@@ -5,6 +5,10 @@ description: 'Use when changing pkg-validate validators, sanitizers, whitelist b
 
 # Package Validate
 
+Non-negotiable TDD rule: Always write the failing test first, run it to confirm it fails for the intended reason, then implement the code and rerun the test until it passes. Test Driven Development is required for all coding work and must not be skipped. For documentation- or skill-only edits, add or update the relevant validation check before changing the prose.
+
+Non-negotiable code organization rule: Functions with the same or equivalent behavior must use the same or clearly corresponding descriptive names across CareCard repositories, and equivalent functionality must live in files with the same names within each repository's established architecture. No backward compatibility names, aliases, or duplicate locations are allowed.
+
 ## Purpose
 
 CareCard validation package for deterministic validators, sanitization, whitelist validation, nested paths, error mapping, exports, and tests.

package/.agents/skills/software-design-patterns-and-clean-code/SKILL.md

@@ -5,6 +5,10 @@ description: 'Use every time before coding, refactoring, debugging, or reviewing
 
 # Software Design Patterns And Clean Code
 
+Non-negotiable TDD rule: Always write the failing test first, run it to confirm it fails for the intended reason, then implement the code and rerun the test until it passes. Test Driven Development is required for all coding work and must not be skipped. For documentation- or skill-only edits, add or update the relevant validation check before changing the prose.
+
+Non-negotiable code organization rule: Functions with the same or equivalent behavior must use the same or clearly corresponding descriptive names across CareCard repositories, and equivalent functionality must live in files with the same names within each repository's established architecture. No backward compatibility names, aliases, or duplicate locations are allowed.
+
 ## Purpose
 
 Use this skill with every coding, refactoring, debugging, or review task in

package/.codex/AGENTS.md

@@ -1,5 +1,7 @@
 # Codex Instructions For pkg-validate
 
+Non-negotiable code organization rule: Functions with the same or equivalent behavior must use the same or clearly corresponding descriptive names across CareCard repositories, and equivalent functionality must live in files with the same names within each repository's established architecture. No backward compatibility names, aliases, or duplicate locations are allowed.
+
 These instructions apply to the `pkg-validate` repository. This file is self-contained:
 it includes the workspace-level instructions that were previously read from
 `/Users/pankajpriscilla/SO_CareCardCa/.codex/AGENTS.md`, followed by

package/.github/workflows/ci.yml

@@ -46,7 +46,7 @@ jobs:
 
         steps:
             - name: Checkout repository
-              uses: actions/checkout@v4
+              uses: actions/checkout@v5
 
             - name: Set up Node.js
               uses: actions/setup-node@v4

package/lib/validateNewUserRoleRequest.js

@@ -59,7 +59,12 @@ function shouldRequireScope(roleRequest, requireScope) {
     if (requireScope === true) return true;
     if (requireScope !== REQUIRE_SCOPE_WHEN_ROLE_OR_SCOPE_PRESENT) return false;
 
-    return roleRequest.role_name !== undefined || roleRequest.institution_id !== undefined || roleRequest.campus_id !== undefined;
+    return (
+        roleRequest.role_name !== undefined ||
+        roleRequest.institution_id !== undefined ||
+        roleRequest.campus_id !== undefined ||
+        roleRequest.program_id !== undefined
+    );
 }
 
 function requireNewUserRoleRequestScope(roleRequest) {

package/lib/validateProperties.js

@@ -167,6 +167,8 @@ function validateProperties(obj = {}) {
             case 'campusId':
             case 'program_id':
             case 'programId':
+            case 'program_term_id':
+            case 'programTermId':
             case 'template_id':
             case 'templateId':
             case 'program_template_id':

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@carecard/validate",
-    "version": "3.6.0",
+    "version": "3.6.1",
     "repository": {
         "type": "git",
         "url": "git+https://github.com/CareCard-ca/pkg-validate.git"

package/readme.md

@@ -9,6 +9,12 @@ invalid values from `validateProperties`, and throws CareCard `BAD_INPUT` errors
 from `validateWhitelistProperties` when required or provided whitelist values do
 not pass validation.
 
+## Development Rule
+
+Non-negotiable TDD rule: Always write the failing test first, run it to confirm it fails for the intended reason, then implement the code and rerun the test until it passes. Test Driven Development is required for all coding work and must not be skipped. For documentation- or skill-only edits, add or update the relevant validation check before changing the prose.
+
+Non-negotiable code organization rule: Functions with the same or equivalent behavior must use the same or clearly corresponding descriptive names across CareCard repositories, and equivalent functionality must live in files with the same names within each repository's established architecture. No backward compatibility names, aliases, or duplicate locations are allowed.
+
 ## Installation
 
 ```sh