fix(audit-api): resolve TypeScript linting errors for type safety

[4eckd]

• Remove unused JWT import from auth module
• Replace implicit 'any' casts with proper Prisma enum types (AuditServiceType, AuditStatus, AuditPriority)
• Remove unnecessary eslint-disable directive now that types are properly specified
• Generate Prisma client to ensure type exports are available

Fixes merge-to-parent by resolving all ESLint errors and TypeScript type issues.

https://claude.ai/code/session_019tv2bPxnA5omaHZC1NjBWg

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
design-vln-site	Ready	Preview, Comment	Feb 26, 2026 5:58pm
docs-vln	Ready	Preview, Comment	Feb 26, 2026 5:58pm
vln	Error		Feb 26, 2026 5:58pm

[github-actions]

Code Signature Verification

Status: ✅ All checks passed

Commit Signatures

Check	Count
Valid signatures	2 (SSH: 1, GPG: 1)
Unsigned commits	0
Invalid signatures	0

Author Verification

• ✅ Author identity: Verified

---

How to Sign Commits

Option 1: SSH Signing (Recommended)

1. Generate an SSH key (if needed):

   ssh-keygen -t ed25519 -C "your_email@example.com"

2. Configure Git for SSH signing:

   git config --global gpg.format ssh
   git config --global user.signingkey ~/.ssh/id_ed25519.pub
   git config --global commit.gpgsign true

3. Add your SSH key to GitHub:
   Go to GitHub Settings > SSH and GPG keys > New SSH key
   Select "Signing Key" as the key type

Option 2: GPG Signing

1. Generate GPG Key:

   gpg --full-generate-key

2. List your GPG keys:

   gpg --list-secret-keys --keyid-format=long

3. Configure Git:

   git config --global user.signingkey YOUR_KEY_ID
   git config --global commit.gpgsign true

4. Add GPG key to GitHub:

   gpg --armor --export YOUR_KEY_ID

   Copy the output and add it to GitHub Settings > SSH and GPG keys

---

Automated security verification by VLN Security Bot

[github-actions]

Code Signature Verification

Status: ✅ All checks passed

Commit Signatures

Check	Count
Valid signatures	3 (SSH: 2, GPG: 1)
Unsigned commits	0
Invalid signatures	0

Author Verification

• ✅ Author identity: Verified

---

How to Sign Commits

Option 1: SSH Signing (Recommended)

1. Generate an SSH key (if needed):

   ssh-keygen -t ed25519 -C "your_email@example.com"

2. Configure Git for SSH signing:

   git config --global gpg.format ssh
   git config --global user.signingkey ~/.ssh/id_ed25519.pub
   git config --global commit.gpgsign true

3. Add your SSH key to GitHub:
   Go to GitHub Settings > SSH and GPG keys > New SSH key
   Select "Signing Key" as the key type

Option 2: GPG Signing

1. Generate GPG Key:

   gpg --full-generate-key

2. List your GPG keys:

   gpg --list-secret-keys --keyid-format=long

3. Configure Git:

   git config --global user.signingkey YOUR_KEY_ID
   git config --global commit.gpgsign true

4. Add GPG key to GitHub:

   gpg --armor --export YOUR_KEY_ID

   Copy the output and add it to GitHub Settings > SSH and GPG keys

---

Automated security verification by VLN Security Bot