Add a venture capital tenant package

[andreolf]

What this changes

Adds a second example tenant package beside examples/fintech, for a venture fund. Five coworkers, all configuration rather than code:

• Deal Scout (built-in) — screens inbound decks and intros, briefs them against the thesis.
• Diligence Analyst (remote-ag-ui) — first-pass market and company diligence on a governed computer; endpoint read from MANAGED_AGENT_AG_UI_URL with a fallback to the Bot in the box.
• Portfolio Monitor, Fund Knowledge, LP Relations (built-in).

Channels scope them across partners, investment, and platform groups. The point is to show the package format on a second vertical, and to give funds a starting point they can edit rather than author from scratch. Worth doing because the format is easy to get subtly wrong by hand (cross-file agent references, environment fallbacks), and a worked second example is the cheapest way to document it.

Includes a test mirroring fintech-package.test.ts that checks the five files exist, the brand id is present, and — like the clean-checkout test — that every ${VAR} in agents.yaml carries a :- fallback so a fresh clone can read the package with no .env.

Where it runs

No runtime code. This is static YAML loaded by the existing tenant-package reader; it adds no state, no listener, no fan-out.

• New state that outlives a request? None.
• What happens on the second replica? No change; the package is read identically by every replica at startup, as examples/fintech already is.
• Anything serialised? None.
• Anything fanned out to a browser? None.
• New listener, port, or schedule? None.

Boundary and audit

• Every acting call still goes through the gateway: resolve, decide, audit, then act. Unchanged — no acting code here.
• New refusals and new failures each write a row. N/A.
• Nothing new is trusted from the client that the server can resolve itself. N/A.

Proof

$ bun test tests/vc-package.test.ts tests/fintech-package.test.ts
 3 pass, 0 fail

# loaded through the real validator
$ MANAGED_AGENT_AG_UI_URL= bun -e 'import {loadTenantPackage} from "./server/src/tenant-package.ts";
  const p = await loadTenantPackage("./examples/vc"); console.log(p.tenantId, p.agents.length, p.channels.length)'
venture 5 5

$ bun run format:check   # clean
$ bun run lint           # clean (new file)

Run it with TENANT_PACKAGE_DIR=../examples/vc bash scripts/start.sh.

[davidmckayv]

Keeping this open — it's a clean, additive example and the tenant-package mechanism itself scales fine (read from the image at boot, upserted into Postgres in one transaction, no runtime upload). One thing blocks it, and it's small: examples/vc/agents.yaml reuses the agent id knowledge, which examples/fintech already uses, and agents.id is a global primary key. So on any database that has booted the default package once, loading venture dies with a misleading collides with a user-created agent — the command in your own README fails. Rename it fund-knowledge (already its display name). While you're in there, its remote agent falls back to port 4200 (agent-bot) where the rest of the repo uses 4201 (agent-langgraph, the one .env.example says to build on). Fix those two and it's good.