@elevasis/core 0.2.0 → 0.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/core",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "license": "MIT",
   "description": "Minimal shared constants across Elevasis monorepo",
   "sideEffects": false,

package/src/README.md

@@ -6,26 +6,33 @@ This package is the source of truth for shared types, schemas, and contract help
 
 ## Import Rules
 
-- Use `@elevasis/core` for browser-safe shared types and schemas.
-- Use `@elevasis/core/server` only for Node.js-only helpers and services.
-- Use `@elevasis/core/test-utils` for test fixtures and mocks.
-- Prefer the narrowest published subpath that matches the work you are doing.
+- Use `@elevasis/core` (root export) for browser-safe shared types and schemas.
+- Use `@elevasis/core/organization-model` for the semantic contract layer.
+- These are the only two subpaths available to external consumers of the published npm package.
+- Paths like `@elevasis/core/server`, `@elevasis/core/test-utils`, `@elevasis/core/platform`, etc. are internal monorepo paths (`@repo/core/...`) and are NOT available to external consumers.
 
 ## Published Surface Groups
 
-- `platform` - shared constants, utilities, registry, SSE, and API types.
-- `auth` - multi-tenancy types for organizations, users, memberships, invitations, and credentials.
-- `execution` - workflow, agent, scheduler, calibration, and execution-interface contracts.
-- `commands` - command queue types and schemas.
-- `deployments` - deployment response types.
-- `operations` - sessions, notifications, observability, activities, triggers, and debug logs.
-- `business` - acquisition and SEO contracts, plus the PDF surface under its own subpaths.
-- `organization-model` - the semantic contract layer for CRM, lead gen, delivery, features, branding, and navigation.
-- `supabase` - generated database types and helpers.
-- `forms` - shared form schemas and form-facing types.
-- `integrations` - OAuth and credential contracts.
-- `projects` - project management request and response schemas.
-- `content` - published content metadata types.
+The published `@elevasis/core` npm package exposes exactly two subpaths:
+
+- `.` (`@elevasis/core`) - browser-safe shared types, schemas, and constants.
+- `./organization-model` (`@elevasis/core/organization-model`) - the semantic contract layer for CRM, lead gen, delivery, features, branding, and navigation.
+
+Within the monorepo, the internal `@repo/core` package exposes additional subpaths for use by `apps/` and other packages:
+
+- `@repo/core/server` - Node.js-only helpers and services.
+- `@repo/core/platform` - shared constants, utilities, registry, SSE, and API types.
+- `@repo/core/auth` - multi-tenancy types for organizations, users, memberships, invitations, and credentials.
+- `@repo/core/execution` - workflow, agent, scheduler, calibration, and execution-interface contracts.
+- `@repo/core/commands` - command queue types and schemas.
+- `@repo/core/operations` - sessions, notifications, observability, activities, triggers, and debug logs.
+- `@repo/core/supabase` - generated database types and helpers.
+- `@repo/core/integrations/...` - OAuth and credential contracts.
+- `@repo/core/projects/api-schemas` - project management request and response schemas.
+- `@repo/core/content` - published content metadata types.
+- `@repo/core/test-utils` - test fixtures and mocks (internal use only).
+
+These `@repo/core/*` subpaths are NOT available in the published `@elevasis/core` package.
 
 ## When To Read Deeper
 

package/src/platform/constants/versions.ts

@@ -1,3 +1,3 @@
 export const VERSION = {
-  CURRENT: '1.5.6'
+  CURRENT: '1.5.7'
 }