fix(build): drop examples/personal-finance from root workspaces — unblock image builds

[buremba]

Reproducer

0.105 error: Workspace not found \"examples/personal-finance\"
0.105     at /app/package.json:8:5
ERROR: failed to build: ... bun install ... exit code: 1

Every `Build and Push Images` workflow run on `main` since #911 merged (13:25 UTC today) has failed at the `bun install` layer of all three Dockerfiles (embeddings-service, worker, app). Prod K8s is stuck on the pre-#911 image tag `20260519-123954`; 8 merged PRs are sitting on `main` un-deployable:

• feat(evals)!: drop in-house YAML runner, ship @lobu/promptfoo-provider #911 promptfoo-provider
• feat(promptfoo-provider): support vars.transcript for multi-turn evals #913/fix: revert #913 to restore #914 + #916 changes lost in bad squash #920 vars.transcript multi-turn (+ revert)
• chore(build): bun lockfile docs, login polling cleanup, migration idempotency #914 build-chore
• feat: guardrails schema extensions + judge engine + pii-scan #915 guardrails schema
• feat: wire guardrails runtime end-to-end + secret-scan and forbidden-tools built-ins #919 guardrails runtime
• feat(auth): install_operator bootstrap — unblock headless installs #923 install_operator (whose `principal_kind` migration is what broke local `make dev` for me earlier)
• chore: bump owletto submodule to ship guardrails UI #924 owletto guardrails-UI bump
• chore(scripts): task-clean repo resolution, drop mac symlink, surface PORT #912 task script fixes
• chore: bump owletto pointer for loading-skeleton sweep (#193) #925 owletto loading-skeletons bump (chore: release main #193 in owletto)

Root cause

PR #911 added `examples/personal-finance` to the root `package.json` workspaces array. The Dockerfiles' `bun install` layer explicitly COPYs every workspace's `package.json` (or stubs ones it doesn't need) — but the example was added to `workspaces` without a matching Dockerfile update. `packages/*` is a glob (forgiving when a path doesn't exist); `examples/personal-finance` is an explicit path (strict — must exist).

Fix

Two options, picked the cleaner one:

1. Stub the example in all three Dockerfiles. Treats the symptom; couples prod build pipeline to whatever exists under `examples/`. Wrong direction.
2. Take the example out of root workspaces entirely. ← Chosen. Examples are docs/demos; they don't belong in the prod build graph.

Side effects of (2)

• Example's dependency on `@lobu/promptfoo-provider` switched from `workspace:*` (workspace-protocol-only) to `file:../../packages/promptfoo-provider`. Resolves locally without requiring workspace membership.
• Consumers running the example now do: `cd packages/promptfoo-provider && bun run build && cd ../../examples/personal-finance && bun install` once. Worth a docs note in the example's README as follow-up.
• `bun.lock` regenerated. Most of the -1,109 LOC diff is bun's "linked workspaces" table shrinking — no upstream version churn.

Verification

Simulated the Docker build context (root files + stubbed `packages/*` manifests + `packages/promptfoo-provider` stub, no `examples/` directory at all) and ran `bun install` cleanly. No "Workspace not found" error.

`tsc --noEmit` clean (pre-commit hook).

Test plan

• Image build on this PR's branch passes (the actual production reproducer).
• Once merged + image rolls, prod app pods come up on the new tag and the `principal_kind` migration applies automatically via the gateway's boot-time `assertSchemaUpToDate` → `dbmate up` path.

Summary by CodeRabbit

• Chores
  • Reorganized monorepo workspace configuration and updated how project dependencies are referenced across the development environment.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d9f7d216-4e57-47da-a37f-afbac3ad866f

📥 Commits

Reviewing files that changed from the base of the PR and between 5369c5b and 7b75140.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• examples/personal-finance/package.json
• package.json

---

📝 Walkthrough

Walkthrough

The monorepo structure is updated to remove examples/personal-finance from the root workspaces configuration and change the example's dependency resolution from workspace protocol to a direct file path to the provider package.

Changes

Workspace and Dependency Restructuring

Layer / File(s)	Summary
Workspace and dependency configuration update package.json, examples/personal-finance/package.json	Root package.json removes examples/personal-finance from the workspaces array. The example's @lobu/promptfoo-provider dependency switches from workspace:* to file:../../packages/promptfoo-provider.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A workspace takes its leave,
File paths now deceive,
No more shared the way,
The rabbit hops away.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: removing examples/personal-finance from root workspaces to fix Docker image build failures.
Description check	✅ Passed	The description is comprehensive and well-structured, covering reproducer, root cause, fix rationale, side effects, and verification. However, the Test plan section uses unchecked checkboxes without evidence of completion.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/example-personal-finance-out-of-workspaces

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!