feat(connector-microsoft): vendor in-tree as workspace package

[AnishRane]

Summary

Brings @boringos/connector-microsoft into the monorepo as a first-party workspace package, mirroring the in-tree placement of @boringos/connector-google. The connector previously lived as a standalone sibling repo depending on the published @boringos/module-sdk@^0.13.0.

This PR is vendoring only — no agent-facing tools yet. Surface is unchanged: ConnectorDefinition + typed clients for Outlook Mail, Calendar, Contacts, and OneDrive (Microsoft Graph). A follow-up will add createMicrosoftModule in @boringos/core (the Google factory's counterpart).

What changed

• New package at packages/@boringos/connector-microsoft/ — 4 services (Mail / Calendar / Contacts / Files), 29 unit tests.
• package.json: SDK dep switched from ^0.13.0 → workspace:*; added repository field for parity with connector-google.
• tsconfig.json: extends ../../../tsconfig.base.json with rootDir / outDir / composite: true, matching connector-google's setup.
• pnpm-lock.yaml regenerated.

No changes to existing packages.

Out of scope (follow-ups)

• createMicrosoftModule factory in @boringos/core/src/modules/microsoft.ts (mirrors google.ts) — wires outlook.* / ms_calendar.* / outlook_contacts.* / onedrive.* tools.
• Static registration in the dev-host boot list.
• Webhooks / delta / events (deferred in the connector itself).

Test plan

• pnpm install — clean
• pnpm -r build — all packages green, including connector-microsoft
• pnpm -r typecheck — all packages green
• pnpm -F @boringos/connector-microsoft test — 29/29 pass
• pnpm test:run — 542 pass, 1 skipped. The 1 failure (tests/phase3-golden.test.ts) fails identically on main (pre-existing, environment-dependent CLI-subprocess test).
• Reviewer: spot-check that the vendored package matches the standalone repo's last green build (commit 23b5cbe in the sibling repo).

🤖 Generated with Claude Code

[AnishRane]

Manually tested the connector end-to-end on a live host — found and fixed one wiring gap.

Pushed 017f858 to this branch.

The fix: the workspace root package.json was missing @boringos/connector-microsoft (it had connector-google and connector-slack). The host discovers connectors by scanning <cwd>/node_modules/@boringos/connector-* at boot, and pnpm only links a workspace package into the root node_modules when the root depends on it. @boringos/core declared the dep, but the root didn't — so on a fresh clone the Microsoft OAuth definition never registered (the module's tools loaded, but discoverConnectors() skipped it). Boot log before vs after:

# before: only google, slack
# after:  [connector-discovery] registered microsoft from @boringos/connector-microsoft

Evidence (dev host on :3030):

• /api/connectors/oauth/microsoft/authorize → correct 302 to login.microsoftonline.com with the right client_id, framework-derived redirect_uri (/api/connectors/oauth/microsoft/callback), all four service scopes + offline_access, signed state, prompt=consent.
• Full OAuth round-trip completed: an Outlook account connects and persists to connector_accounts (status active, encrypted credentials, granted scopes). Google verified the same way as a control.
• tests/microsoft.test.ts 6/6 green; tsc clean for connector-microsoft + core.

Heads-up (separate, env-only): connecting also requires BORINGOS_ENCRYPTION_KEY to be set (tokens are AES-256-GCM encrypted before storage) and MICROSOFT_CLIENT_ID/MICROSOFT_CLIENT_SECRET. Neither is in the .env.example from #25 yet — noted there.