tasks-core-node-ts

Independent npm package for task and care-reminder bootstrap, feature-flag parsing, and minimal Express integration.

Current scope:

• feature flag parsing from env-like input
• bootstrap helper for Express integration
• minimal status endpoint for activation checks
• reusable task domain model with lifecycle states
• in-memory repository and task service for package-level workflows

Package commands:

• npm run build compiles src into dist
• npm run typecheck validates the package without emitting output
• npm test runs package-level tests using in-memory Express wiring
• npm pack --dry-run can be used to inspect the published payload after prepack

Positioning:

• intended to be published and versioned as its own package
• targeted at a concrete care/tasks project, not as a narrative artifact of the gateway repository
• consumable from npm by host applications that want to enable the module through configuration
• canonical source repository: https://github.com/Fundacion-UNID/tasks-core-node-ts
• npm package name: tasks-core-node-ts

Publication notes:

• the package builds its own dist from src
• prepack runs build plus package tests before packaging
• publish command (token-based): npm publish --access public --//registry.npmjs.org/:_authToken="$NPM_TOKEN"
• roadmap items are tracked in TODO.md inside the package
• repository, homepage, and issue tracker metadata point to the dedicated package repository

Testing strategy:

• package tests should use in-memory adapters and deterministic fixtures
• real PostgreSQL integration tests belong to the host gateway or application integration layer

Phase 2 exports:

• TaskService and createTaskService(...) for reusable task lifecycle operations
• InMemoryTaskRepository for local development and package-level tests
• core types such as TaskRecord, CreateTaskInput, ListTasksQuery, and TaskStatus

Reminder routing contract:

• this package targets tenant-scoped reminder runtime paths under /:tenantId/...
• it is not a host-registry onboarding package
• reminder/task claims may carry passthrough metadata such as permission overlays or contact-routing data, but canonical subject onboarding still belongs to tenant-scoped Communication flows