karti
74e37f3e76
Work in progress from the Codex session, committed so nothing sits undeployed. Verified before committing: typecheck clean across all packages, 139 unit tests and the e2e suite green, migrations apply to an empty Postgres. Adds the HubSpot integration boundary (OAuth, client, contracts, webhook signature verification, sync), a growth route, customer-lifecycle service, Piggy lifecycle tools, a Growth page, and shared lifecycle/hubspot types. Two things are deliberately incomplete and should not be mistaken for finished: `packages/db/src/schema/hubspot.ts` is NOT exported from the schema index, so it is inert — no tables, no migration. That is the correct order (the shape can settle before it becomes a migration), but it does mean the HubSpot routes have no persistence behind them yet. `pnpm-workspace.yaml` and `pnpm-lock.yaml` are left uncommitted on purpose. The workspace file contains a literal unanswered placeholder — "esbuild: set this to true or false" — and this repository installs with npm, which is also what CI runs. Committing a second package manager's lockfile would make the install ambiguous. If the move to pnpm is intended it should be a deliberate change that updates CI and the Dockerfile together. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
21 lines
858 B
TypeScript
21 lines
858 B
TypeScript
import { strict as assert } from 'node:assert';
|
|
import { describe, it } from 'node:test';
|
|
import type { Database } from '@pig/db';
|
|
import { createInteractivePigTools } from '../src/chat-tools';
|
|
|
|
describe('interactive lifecycle tool boundary', () => {
|
|
it('exposes deterministic lifecycle context only for the account in focus', () => {
|
|
const accountTools = createInteractivePigTools({} as Database, {
|
|
type: 'account',
|
|
id: '10000000-0000-4000-8000-000000000001',
|
|
});
|
|
const contractTools = createInteractivePigTools({} as Database, {
|
|
type: 'contract',
|
|
id: '20000000-0000-4000-8000-000000000001',
|
|
});
|
|
|
|
assert.deepEqual(accountTools.map((tool) => tool.name), ['pig_get_record', 'pig_get_account_lifecycle']);
|
|
assert.equal(contractTools.some((tool) => tool.name === 'pig_get_account_lifecycle'), false);
|
|
});
|
|
});
|