sh-mcp/packages/tasks/src/index.ts

34 lines
1.4 KiB
TypeScript
Raw Normal View History

Phase 0b slice: monorepo scaffold + @sh-mcp/shared core + integration packages (#2) * Phase 0b slice: monorepo scaffold + shared core + integration packages The 0a-INDEPENDENT code slice (one-shot via af-0b-package-slice workflow: Haiku scaffold + Sonnet packages, Sonnet fix-to-green). Nothing deploys; no CDK/servers. - Monorepo scaffold: npm workspaces, strict TS (NodeNext), vitest (80% gate), eslint 9 flat config, prettier; ci.yaml/deploy.yaml callers (Node 24, enable-qemu). - @sh-mcp/shared: transport-agnostic core — Scope/AuthContext/ToolDef, ToolRegistry, redact()+maskValue() (PII), OpenAPI 3.1 generator. AUTH STUBBED behind an AuthProvider interface (TODO auth-layer-0a); JWT/aud/client_id/JWKS/deny-list deferred per design.md §2. - 9 integration packages (qbo, google-maps, internal-data, payments, knowledge-base, gmail, calendar, tasks, reminders): tools against shared, external deps mocked behind injected client interfaces; finance handlers call redact(). Verified green: tsc -b clean, vitest 245/245, eslint 0 errors. Auth mechanism intentionally deferred until the 0a spike resolves it (G16/§0.4). * Complete Cognito auth provider + Phase 1 build brief Finish the WIP CognitoAuthProvider (client_id allow-list as audience boundary, finance TTL ceiling, deny-list, scope-prefix stripping) with its test suite, and check in docs/build-plan-phase-1.md so the Phase 1 work has its governing brief in-tree (design.md §2.5). * ci: disable cdk synth for Phase 0b (no CDK app yet) The reusable ci-typescript-cdk workflow defaults run-cdk-synth: true, but the Phase 0b package scaffold has no cdk.json or stacks, so cdk synth fails with '--app is required'. Disable it here; Phase 1 re-enables it with the server CDK stubs.
2026-06-26 12:42:17 -04:00
/**
* @sh-mcp/tasks — public entry point.
*
* Exports the tool definitions built against a DynamoDBTasksClient.
* The MCP server imports `tools` (the live array) and the tool factory
* `buildTaskTools` for cases where an alternate client must be injected
* (e.g. local dev, custom test harnesses).
*
* Wire transport (OpenAPI / Streamable-HTTP MCP) is generated from the tool
* registry in packages/shared; this package only defines the tools.
*/
export { buildTaskTools } from './tools.js';
export type { TasksClient, Task, CreateTaskInput, ListTasksInput, CompleteTaskInput, DeleteTaskInput } from './client.js';
export { DynamoDBTasksClient } from './client.js';
// The `tools` export is the live array used by the MCP server at runtime.
// It is constructed with the real DynamoDB client, which guard-throws in test
// environments to ensure tests always go through buildTaskTools(mockClient).
import { buildTaskTools } from './tools.js';
import { DynamoDBTasksClient } from './client.js';
// Only instantiate the real client outside of test environments.
// In test environments, tests import buildTaskTools directly and inject a mock.
const _client =
process.env['NODE_ENV'] === 'test'
? null
: new DynamoDBTasksClient();
export const tools =
_client !== null
? buildTaskTools(_client)
: ([] as unknown as ReturnType<typeof buildTaskTools>);