Restores green build after the May 12 Docker/UI regression. Root cause: pnpm-workspace.yaml referenced a sibling path (../learning_ai/learning_ai_common_plat/...) that did not exist on dev/CI hosts. .pnpmfile.cjs fell back to ../learning_ai_common_plat for some packages but missed others, so @bytelyst/ui was pulled from a stale Gitea 0.1.0 tarball with zero exports (breaking web typecheck + 26 tests) and @bytelyst/monitoring was never linked into node_modules (breaking backend typecheck + 2 test suites). Changes: - pnpm-workspace.yaml now references ../learning_ai_common_plat/packages/* directly - .pnpmfile.cjs swaps DEFAULT/LEGACY common-plat roots so the canonical path is the default and the older nested path is the fallback - scripts/docker-prep.sh, scripts/local-smoke.sh, scripts/release-guard-audit.sh follow the same canonical-first / legacy-fallback pattern - .github/workflows/ci.yml symlinks directly to ../learning_ai_common_plat - pnpm-lock.yaml regenerated with @bytelyst/ui@0.1.9 and @bytelyst/monitoring@0.1.5 linked to the local common-plat checkout Verified: - pnpm run verify: backend 373/373, web 96/96, mobile 97/97 - pnpm run audit:release-guards: passes - backend, web, mobile lint all exit 0 (advisory warnings retained) |
||
|---|---|---|
| .. | ||
| e2e | ||
| public | ||
| scripts | ||
| src | ||
| test-results | ||
| .env.example | ||
| .gitignore | ||
| Dockerfile | ||
| eslint.config.mjs | ||
| next-env.d.ts | ||
| next.config.ts | ||
| package.json | ||
| playwright.config.ts | ||
| tsconfig.json | ||
| vitest.config.ts | ||