Adds the missing packages field to pnpm-workspace.yaml

Pre-existing file from the original frontend setup - had allowBuilds
and confirmModulesPurge but no packages list, which pnpm 9+ requires
the moment a workspace file exists at all, even for a single package.
Surfaced by the first real pipeline run (frontend-prepare failed with
"packages field missing or empty").

aidlc-docs/features/gitea-deployment-workflow/audit.md

@@ -1429,3 +1429,13 @@ by Infrastructure Design. U5 carries REF-U3-01's Umami origin gate plus FR-21 an
 
 **Context**: OPERATIONS — Deployment Setup naming correction that required a small Construction-phase code change (deploy-scp.yaml)
 ---
+## Deployment Setup — First Real Pipeline Run Hit a Pre-Existing pnpm-workspace.yaml Bug
+
+**Timestamp**: 2026-07-29T01:20:00Z
+
+**User Input**: "Bij het draaien van de pipeline krijg ik bij de front-end prepare job het volgende: [pnpm install --frozen-lockfile fails with 'ERROR packages field missing or empty']"
+
+**AI Response**: "Root cause: frontend/pnpm-workspace.yaml (committed since the original frontend setup, unrelated to this feature) has allowBuilds/confirmModulesPurge settings but never had a packages: field, which modern pnpm requires whenever a pnpm-workspace.yaml file exists at all, even for a single non-monorepo package. Added `packages: - '.'`. Verified locally: pnpm install --frozen-lockfile succeeds, lint clean."
+
+**Context**: OPERATIONS — first real Gitea Actions pipeline run surfaced a pre-existing frontend config defect, fixed per the standing rule that small defects found in passing get fixed, not filed
+---

frontend/pnpm-workspace.yaml

@@ -1,3 +1,5 @@
+packages:
+  - '.'
 allowBuilds:
   '@tailwindcss/oxide': true
   esbuild: true