CellixJs/cellixjs
46.6
Weak · 8 November 2026
43.9k
lines of production code
TypeScript
primary language
7
measurements over time
What this system is
This system is a monorepo-based platform for managing communities and staff operations, built on Azure Functions, React, and GraphQL. It provides a shared framework layer that standardizes infrastructure services like Azure storage, MongoDB persistence, and OIDC authentication across multiple frontend and backend applications. The codebase enforces strict architectural patterns through Domain-Driven Design principles, automated testing, and AI-assisted development guidelines to ensure consistency and maintainability.
How it got here
2025 — Monorepo migration and infrastructure foundation
38 changes.
The project transitioned to a pnpm-based monorepo structure, establishing a comprehensive CI/CD pipeline and removing legacy Azure Functions entry points in favor of a centralized API bootstrap. This period focused on building foundational Infrastructure as Code modules for Azure services and implementing core Domain-Driven Design seedwork packages for event handling and persistence. Concurrently, initial scaffolding was completed for the API, UI Community, and shared UI core components to support the new architecture.
2026 — Staff portal launch and framework standardization
29 changes.
This period focused on launching the new Staff UI application with role-based access control and Azure infrastructure, while simultaneously standardizing the development environment through shared configuration packages for Vitest, Rolldown, and local development utilities. Significant effort was also directed toward strengthening architectural integrity via new ArchUnit tests, expanding AI agent skills, and refactoring core services like Azure Functions and OAuth2 mocks to support better isolation and testing.
Features
API app restructured with new build, local dev, and deployment configurations
The API application has been reorganized under the apps/api directory, introducing a complete set of configuration files to support the new monorepo structure. This includes a new Azure Pipelines deployment definition (deploy-api.yml) that handles infrastructure setup, artifact download, and Azure Functions deployment, alongside updated host.json settings enabling OpenTelemetry telemetry. Local development is now standardized via new entry points (start-dev.ts, start-azurite.ts) and configuration files (local-settings.e2e.json, globals.d.ts) that define required environment variables for OIDC, storage, and database connections. The build process utilizes a new rolldown bundler configuration (rolldown.config.ts) and updated TypeScript configs (tsconfig.json, tsconfig.rolldown.json) to bundle the API for deployment, while turbo.json defines the build and dev tasks within the workspace.
apps/api · high confidence
Add Azure storage and queue configuration modules
The API application now includes dedicated configuration modules for Azure services. The new \azure-storage\ module exports environment-based account name and connection string values, supporting managed identity in production and SharedKey signing for local development with Azurite. The \queue-storage\ module provides a logging configuration for the queue service, enabling logging to a 'queue-logs' container with synchronous writes disabled.
apps/api/src/service-config/azure-storage, apps/api/src/service-config/queue-storage · high confidence
Add OIDC configuration for the community UI
The community frontend application now includes a dedicated OpenID Connect (OIDC) configuration file that defines the authentication settings, including authority, client ID, and redirect URI. These values are primarily sourced from environment variables (prefixed with VITE\_APP\_UI\_COMMUNITY\_END\_USER\B2C\) but fall back to mock defaults for local development. The configuration also specifies the OAuth2 response type as 'code' and implements a sign-in callback that restores the user's previous navigation path from session storage after authentication.
apps/ui-community/src/config · high confidence
Add OpenTelemetry configuration for API services
The API service configuration now includes an OpenTelemetry starter module that initializes the Otel service. In development environments, this configuration is set to export traces to the console and use simple processors, enabling easier debugging and visibility into service operations during local development.
apps/api/src/service-config · high confidence
Add theme context with dark/light mode toggle and keyboard shortcut
The ui-community app now includes a ThemeContext provider that manages light, dark, and custom theme states using Ant Design's theming system. Users can switch between light and dark modes via a 'Toggle Dark/Light' button, and the selected theme is persisted to local storage. Additionally, pressing Cmd+Shift+K toggles the visibility of the theme controls.
apps/ui-community/src/contexts · high confidence
Added .claude skills symlinks for various frameworks and tools
The .claude directory now includes symlinks to a range of agent skills, including serenity-tests, ant-design, antd, apollo-client, apollo-mcp-server, apollo-server, browser-testing-with-devtools, cellix-tdd, graphql-operations, graphql-schema, madr-enforcement, mongodb-connection, mongodb-mcp-setup, mongodb-query-optimizer, mongodb-schema-design, plan-feature, queue-authoring, review-diff, run-validation, turbo-graph-optimization, turborepo, typescript-advanced-types, vercel-react-best-practices, and vitest. These symlinks point to corresponding directories under .agents/skills, making these skills available for use within the .claude environment.
.claude · high confidence
Added AuthLanding component and Storybook story
A new AuthLanding component has been introduced in the UI community module, which automatically redirects users to the community accounts page. A corresponding Storybook story has been added to verify that the component renders without errors, utilizing a MemoryRouter to handle the navigation context.
apps/ui-community/src/components/ui/molecules · high confidence
Added Mongoose configuration for Azure Cosmos DB integration
The API service now includes a dedicated Mongoose configuration module that connects to Azure Cosmos DB using the MongoDB API. This change introduces connection options tailored for the Cosmos DB emulator in development and test environments (enabling insecure TLS) and production, along with settings for connection pooling, auto-indexing, and debug logging. A README has also been added to document the required Cosmos DB database setup, specifically noting the recommended autoscale throughput limits.
apps/api/src/service-config/mongoose · high confidence
Added event handlers for community member provisioning
The event-handler package now includes logic to automatically provision members and default roles when a new community is created. This is implemented via a new integration event handler that listens for the CommunityCreatedEvent and invokes the CommunityProvisioningService, with registration functions exposed in both domain and integration handler index files.
packages/ocom/event-handler/src/handlers/domain, packages/ocom/event-handler/src/handlers/integration · high confidence
Added global resource naming conventions and location code mappings
The infrastructure-as-code module now includes standardized resource naming conventions and location code mappings. A new Bicep module (\resource-naming-convention.bicep\) generates consistent prefixes for Azure resources based on environment and application prefix, adhering to Microsoft's cloud adoption best practices. Supporting JSON files define abbreviations for common resource types (e.g., \rg\ for resource group, \st\ for storage account) and map specific Azure regions (eastus2, westus3) to short codes, ensuring uniformity across deployed resources.
iac/global · high confidence
Added infrastructure for deploying static websites via Azure Storage and CDN
This change introduces Infrastructure as Code (Bicep) templates in the \iac/static-website\ directory to provision Azure Storage accounts configured for static website hosting, along with optional Azure CDN endpoints for content delivery. The solution includes a PowerShell deployment script to enable the static website feature and inject index/error documents, a configuration file for content compression types, and support for custom domains and CORS policies, enabling the deployment of frontend applications.
iac/static-website · high confidence
Define portal token configuration map
A new configuration module has been introduced at apps/api/src/service-config/token-validation to manage portal token mappings. This change adds a Map object that associates specific portal identifiers, such as 'AccountPortal' and 'StaffPortal', with their corresponding token keys ('ACCOUNT\_PORTAL' and 'STAFF\_PORTAL'), providing a centralized source for these token definitions within the API service configuration.
apps/api/src/service-config/token-validation · high confidence
Expanded AI agent skills for Ant Design, Apollo Client, and CellixJS workflows
The .agents/skills directory now includes new structured guidance for AI coding assistants. For UI development, skills for Ant Design (including the @ant-design/cli for offline API lookup and migration) and Apollo Client 4.x (covering caching, fragments, and framework integrations like Next.js) have been added. CellixJS-specific skills have also been introduced or updated, including a consumer-first TDD workflow, MADR enforcement for architectural standards, queue authoring, and skills for Turborepo optimization, Serenity/JS testing, and feature planning. These skills provide domain expertise and enforcement rules to help agents write code that aligns with project patterns and best practices.
.agents · high confidence
Initial Azure Search Service infrastructure module
The search-service location now includes the core Bicep module (main.bicep) and its configuration (bicepconfig.json). This module provisions an Azure Cognitive Search resource using API version 2025-05-01, allowing users to configure location, tags, replica and partition counts, and SKU tier (including storage-optimized options). It also supports role-based access control via configurable role assignments and enforces a warning for outdated module versions.
iac/search-service · high confidence
Initial Function App infrastructure with managed identity and RBAC
This change introduces the initial Bicep infrastructure for the Function App, including the main deployment module, configuration, and role assignment helpers. It provisions the Function App with a system-assigned managed identity and automatically assigns it the 'Key Vault Secrets User' role for secret access, as well as 'Storage Blob Data Contributor' and 'Storage Queue Data Contributor' roles for storage operations. The deployment is configured for Node.js 20 on the Functions \~4 runtime, with specific app settings for Azure WebJobs storage, Application Insights connection, and CORS origins.
iac/function-app · high confidence
Initial Infrastructure as Code for API environment
This change introduces the foundational Infrastructure as Code (IaC) for the API application, adding the main Bicep module and its corresponding development environment parameters. It defines the deployment of core Azure resources including an App Service Plan (SKU B1), a Function App, a Storage Account with Blob, Queue, and Table services, a Cosmos DB MongoDB instance, Application Insights, and a Search Service. The configuration sets specific parameters for the development environment, such as the 'dev' environment tag, 'eastus2' region, and CORS settings for 'https://ownercommunity.org'.
apps/api/iac · high confidence
Initial Storybook configuration and Apollo mocks for the community UI
This change introduces the Storybook setup for the @ocom/ui-community package, enabling developers to view and test community-related components in isolation. It adds the core configuration files (main.ts, preview.tsx) and an apollo-mocks.ts file that provides sample data for GraphQL queries related to communities, members, and the current end user. The preview layer integrates Ant Design styles, a theme provider, and a mocked Apollo client to ensure components render correctly without a live backend.
apps/ui-community/.storybook · high confidence
Initial community application shell with routing and authentication
The \apps/ui-community/src\ directory now contains the foundational entry point and application shell for the community interface. This includes the main \App.tsx\ component which establishes React Router routes for the root, authentication redirect, and community sections (including admin and accounts views), wrapped in an Apollo GraphQL client and OIDC authentication provider. The entry point \main.tsx\ initializes the React root with Ant Design theming, a theme context provider, and Helmet support. Supporting files include CSS styles for the application layout and UI components, Storybook stories for testing the app's rendering under different routes, and TypeScript environment declarations.
apps/ui-community/src · high confidence
Initial infrastructure for the UI Staff portal
Added Bicep templates to provision the storage account and static website that back the UI Staff portal. The configuration defaults to the Standard\_RAGZRS storage SKU and includes parameters for environment, instance naming, CORS settings, and tagging, following the existing infrastructure-as-code pattern used by other applications.
apps/ui-staff/iac · high confidence
Initial monorepo scaffolding and CI/CD pipeline configuration
Establishes the foundational structure for the CellixJS monorepo, introducing a pnpm workspace with a centralized dependency catalog (including Vite 8, Vitest 4, TypeScript 6, and Ant Design 6) and Turborepo for task orchestration. Adds an Azure Pipelines configuration that integrates SonarCloud for code quality, Snyk for security scanning, and EdgeScan for vulnerability assessment, alongside a \.force-deploy\ mechanism to manually override deployment triggers for specific application packages (API, UI, UI Staff, Docs).
(repo-wide) · high confidence
Initial release of api-services-spec package
The new api-services-spec package introduces TypeScript interfaces for service lifecycle management, defining ServiceBase and SyncServiceBase to standardize startUp and shutDown operations for both asynchronous and synchronous services. This package is configured with a TypeScript build setup extending the cellix node configuration and is tagged as a backend dependency within the monorepo's build system.
packages/cellix/api-services-spec · high confidence
Initial release of the Staff UI application
This change introduces the new \ui-staff\ application, a Vite-based React frontend dedicated to staff operations. It includes the core infrastructure for local development and testing, such as mock OIDC configuration files (\mock-oidc.json\, \mock-oidc.users.json\) defining staff-specific user roles (e.g., \Staff.CaseManager\), and environment variables for connecting to the mock authentication authority and GraphQL API. The app is configured to run on port 3001, uses Tailwind CSS for styling, and includes a CI/CD deployment pipeline definition (\deploy-ui-staff.yml\) and IaC templates for Azure deployment.
apps/ui-staff · high confidence
Initialize Storybook configuration for cellix/ui-core
Storybook is now configured for the cellix/ui-core package, enabling developers to view and test UI components in isolation. The setup includes essential addons for documentation, accessibility, and Vitest integration, and applies a global React Router decorator to ensure components relying on routing context render correctly within stories.
packages/cellix/ui-core/.storybook · high confidence
Introduce @cellix/service-queue-storage for type-safe Azure Queue operations
This change adds the \@cellix/service-queue-storage\ package, providing a framework-level service for sending, receiving, and peeking at Azure Queue Storage messages with JSON Schema validation. It introduces a \defineQueue\ helper and a \registerQueues\ factory that generate strongly-typed methods (e.g., \sendMessageToOrderCreatedQueue\) based on payload schemas. The service supports both connection-string and managed identity authentication, includes auto-provisioning for local development, and offers optional blob-backed message logging with payload-derived metadata.
packages/cellix/service-queue-storage · high confidence
Introduce Apollo GraphQL connection layer for the staff portal
The staff portal now includes a dedicated Apollo Client configuration that automatically attaches authentication tokens (via react-oidc-context) and contextual headers (x-community-id, x-member-id) to GraphQL requests. It also implements request batching for performance and supports a separate REST link for country data, ensuring the staff UI can communicate with backend services using the same header conventions as other UI packages.
apps/ui-staff/src/components/ui/organisms · high confidence
Introduce ApolloConnection component with configurable GraphQL link chains
The \ApolloConnection\ component in the community UI now wraps the application with an Apollo Client provider that dynamically configures the request link chain. It automatically injects authentication headers (supporting both \react-oidc-context\ tokens and local storage fallbacks in development) and adds custom headers for community and member IDs based on the current route. The component also implements a routing mechanism to split requests between a primary GraphQL endpoint and a separate REST endpoint for country data, ensuring the correct data source is used for each operation.
apps/ui-community/src/components/ui/organisms · high confidence
Introduce Mongoose Seedwork infrastructure for MongoDB persistence
The @cellix/mongoose-seedwork package now provides concrete MongoDB/Mongoose implementations for the Cellix domain seedwork abstractions. It includes MongoRepositoryBase for aggregate persistence with pre-commit domain event dispatching and post-commit integration event collection, MongoUnitOfWork for managing Mongoose transactions and scoped repositories, and MongoTypeConverter for bridging Mongoose documents and domain objects. Additional utilities include MongooseDomainAdapter for mapping documents to domain props, MongoosePropArray for handling document arrays, and modelFactory for lazy model registration. The package also exports base types (Base, SubdocumentBase, NestedPath) and comprehensive Cucumber feature tests covering repository, unit of work, type conversion, and connection behaviors.
packages/cellix/mongoose-seedwork/src · high confidence
Introduce Node.js event bus implementations with OpenTelemetry tracing
This change adds the \NodeEventBus\ and \InProcEventBus\ implementations for the \@cellix/event-bus-seedwork-node\ package, providing a singleton-based event bus that supports registering handlers, dispatching events, and removing listeners. The \NodeEventBus\ integrates OpenTelemetry to create spans for publishing and processing events, injects propagation context into event payloads, and ensures errors in handlers do not propagate to the caller while recording exceptions. The \InProcEventBus\ offers a simpler in-process alternative. Both implementations are accompanied by comprehensive Cucumber-style feature tests and unit tests validating handler registration, dispatch order, error handling, and singleton behavior.
packages/cellix/event-bus-seedwork-node/src · high confidence
Introduce UI Community application with local development and deployment scaffolding
The UI Community app is now available as a standalone Vite + React + TypeScript application within the monorepo. This change provides the foundational structure for the community-facing interface, including environment configuration files for local and E2E testing, a Tailwind CSS setup, and a Vite build configuration that conditionally applies node polyfills in production and a visualizer plugin in development. It also introduces a local development runner (\start-dev.ts\) that integrates with the existing mock OIDC server for authentication testing, alongside Azure Pipelines deployment definitions and Infrastructure-as-Code (Bicep) templates to support automated deployment to Azure static websites.
apps/ui-community · high confidence
Introduce foundational DDD domain seedwork package
The \@cellix/domain-seedwork\ package now provides the core building blocks for Domain-Driven Design, including base classes for \AggregateRoot\, \DomainEntity\, and \ValueObject\, along with interfaces for \Repository\, \UnitOfWork\, and \TypeConverter\. It introduces a typed event system with \DomainEvent\ and \EventBus\ contracts, a \HandleEvent\ mechanism for subscriptions, and an \EventPublisher\ for dispatching. The package also includes \PermissionError\ and \NotFoundError\ for domain exceptions, a \PropArray\ interface for managing embedded collections, and a \BaseDomainExecutionContext\ marker, all supported by comprehensive Cucumber-style test coverage.
packages/cellix/domain-seedwork/src · high confidence
Introduce managed-identity blob service with optional client-signing subclass
The \@cellix/service-blob-storage\ package now provides two distinct framework services: \ServiceBlobStorage\ for server-side blob operations (upload, list, delete) using managed identity, and \ServiceClientBlobStorage\ which extends the base service to add SharedKey signing capabilities for direct client uploads and downloads. This split isolates connection-string usage to the client-signing subclass, ensuring the base service remains strictly managed-identity-backed and does not accept connection strings.
packages/cellix/service-blob-storage · high confidence
Introduce staff portal with role-based route access
The new \ui-staff\ application provides a staff portal that routes authenticated users to specific management sections based on their permissions. The \App.tsx\ entry point and \AuthLanding\ component use the \useStaffPermissions\ hook to query the current user's role and determine the default landing page, prioritizing Tech Admin, Finance, Community Management, and User Management sections in that order. The \StaffRoutes\ component dynamically renders these sections only if the user holds the corresponding permissions (e.g., \canManageFinance\, \canManageCommunities\), ensuring that unauthorized sections are hidden. An \Unauthorized\ page is displayed for users who do not meet the criteria for any section.
apps/ui-staff/src · high confidence
Introduce static codegen plugins and schema builder for rolldown compatibility
This change introduces \@cellix/graphql-codegen\ and updates \@cellix/graphql-core\ to replace runtime glob-based file discovery with static, build-time generated artifacts, enabling the rolldown bundler to analyze imports at bundle time. The new package provides two graphql-codegen plugins: \static-type-defs\ (which outputs a static TypeScript array of SDL strings) and \resolver-manifest\ (which generates static imports for resolver and permission files). These plugins generate artifacts consumed by the new \buildCellixSchema\ function, which merges base Cellix types, application type definitions, and resolvers into an executable GraphQL schema. Additionally, \@cellix/graphql-core\ now exports a \getRequestedFieldPaths\ utility for extracting leaf field paths from GraphQL resolve info, along with base schema definitions for MongoDB models and mutation results.
packages/cellix/graphql-core · high confidence
Introduce theme persistence via localStorage
Users can now have their UI theme preference (light, dark, or custom) automatically remembered across sessions. This is implemented by a new \theme-storage.ts\ module that reads from and writes to the browser's \localStorage\ under the key \themeProp\, and the package's public API now exports this storage logic alongside the component exports.
packages/cellix/ui-core/src · high confidence
Introduces theme context with light, dark, and custom modes for the staff UI
The staff application now includes a ThemeContext provider that manages UI appearance across light, dark, and custom themes. Users can switch between these modes, with their preference persisted in local storage and restored on subsequent visits. Additionally, a keyboard shortcut (Meta+Shift+K) is available to toggle the visibility of the theme controls.
apps/ui-staff/src/contexts · high confidence
Mock OAuth2 server now supports multiple named OIDC configurations per frontend portal
The mock OAuth2 server has been refactored to support multiple distinct OIDC configurations (e.g., 'end-user', 'admin') within a single frontend application. This is achieved through a new \discoverPortalConfigs\ utility that scans \ui-\*\ app directories for \mock-oidc.json\ files, allowing each file to define one or more named configs. The \createMockOAuth2Manager\ now registers these configurations as separate named routes (e.g., \/community-end-user\), enabling isolated login/signup flows and user stores for each config. User definitions in \mock-oidc.users.json\ can now include an \oidcConfigName\ field to scope them to specific configurations, and the file-based user store filters users accordingly. This allows developers to simulate multiple identity providers or user roles within a single mock server instance.
packages/cellix/server-oauth2-mock-seedwork/src · high confidence
New @cellix/config-rolldown package for Azure Functions bundling and deployment
This change introduces the \@cellix/config-rolldown\ package, which provides a standardized Rolldown configuration factory for Cellix Azure Functions applications and a CLI tool to prepare the deployment artifact. The package automatically builds a CommonJS alias map to handle mixed workspace and npm dependencies, configures the bundler for Node.js ESM output with sourcemaps, and includes a \prepare:deploy\ step that copies \host.json\ and generates a minimal \package.json\ for the \deploy/\ directory. It also ships with a CLI (\cellix-prepare-azure-functions-deploy\) and comprehensive tests to ensure correct behavior.
packages/cellix/config-rolldown · high confidence
New @cellix/local-dev package for generic local development helpers
A new \@cellix/local-dev\ package has been introduced to provide reusable, policy-free mechanics for local development across the monorepo. It includes worktree-aware utilities for deriving deterministic MongoDB and Azurite ports, sanitizing branch names into DNS-safe hostnames, and transforming URL-based environment variables. The package also offers generic dev runners for Vite, Docusaurus, Azure Functions, and Node processes, along with helpers for parsing \.env\ files, syncing JSON settings, and managing child process exit codes. This centralizes local development logic, allowing app-specific wrapper scripts to focus on project-specific configuration while leveraging shared infrastructure for worktree isolation and service orchestration.
packages/cellix/serenity-framework · high confidence
New App Service Plan Bicep module with configurable SKU and OS
A new Bicep module has been added to define an App Service Plan, allowing users to specify the SKU (including Shared, Free, Basic, Standard, Premium, and Isolated tiers) and the operating system (Linux). The module enforces resource naming conventions using an application prefix, environment, and instance name, and outputs the plan's ID, name, and location for use by other infrastructure components.
iac/app-service-plan · high confidence
New UI Core Molecule Components: ComponentQueryLoader and RequireAuth
The \packages/cellix/ui-core/src/components/molecules\ directory now exports two new reusable UI components. \ComponentQueryLoader\ simplifies data-fetching states in Apollo Client applications by automatically rendering loading skeletons, error messages, or custom content based on query status, with support for custom error, loading, and no-data fallbacks. \RequireAuth\ provides a route-guarding component that integrates with \react-oidc-context\ to handle authentication flows, displaying a loading spinner while authenticating, redirecting unauthenticated users to the login page (optionally preserving the current route via \forceLogin\), and rendering protected children only when authenticated. Both components include Storybook stories demonstrating their various states and behaviors.
packages/cellix/ui-core/src/components/molecules · high confidence
New application services for community and member management
The \@ocom/application-services\ package now exposes a structured \CommunityContextApplicationService\ that provides operations for creating, querying, and updating community settings, as well as comprehensive member management including creation, account association, profile updates, role assignment, activation/deactivation, and removal. This includes new capabilities for inviting members (both single and bulk) with configurable expiry and messages, and ensures that bulk operations respect a maximum batch size of 100 while continuing on per-member failures. The implementation integrates with blob storage and queue storage during community creation to log events and trigger downstream processes, and is supported by extensive BDD and unit tests covering these new service behaviors.
packages/ocom · high confidence
New build-pipeline scripts for IaC, SonarCloud, and coverage merging
Added several new scripts to the build-pipeline to enhance CI/CD capabilities. The \build-bicep.js\ script automates the compilation of Bicep infrastructure files to JSON, targeting the \iac/build\ directory for Snyk IaC scanning. A new \check-sonar-quality-gate.cjs\ script allows local development and CI to poll SonarCloud for quality gate status, while \merge-coverage.js\ combines LCOV reports from monorepo packages into a single file. Additionally, \detect-changes.cjs\ and \get-pr-number.cjs\ provide robust change detection and PR number resolution using \execSync\ with \shell: false\ for security, replacing previous shell-execution approaches.
build-pipeline/scripts · high confidence
New cellix-tdd agent skill with utility fixtures
The cellix-tdd agent skill now includes a set of TypeScript fixture packages that demonstrate common utility patterns and testing scenarios. These fixtures provide implementations for parsing host and port configurations, reading required and optional environment variables, parsing boolean flags and comma-separated string lists, generating URL-safe slugs with configurable separators, merging HTTP headers with case-insensitive normalization, creating deterministic retry policies with exponential backoff, and dispatching commands via a normalized router. Each fixture includes corresponding unit tests using Vitest to validate the behavior of these utilities.
(repo-wide) · high confidence
New seedwork package for in-memory MongoDB replica sets
Added the \@cellix/server-mongodb-memory-mock-seedwork\ package, which provides reusable startup logic for spinning up a local, single-node MongoDB replica set in memory using \mongodb-memory-server\. This package exports a programmatic API to start the replica set (pinned to MongoDB binary version 7.0.14) and supports optional database seeding via Mongoose, intended for use by the \@apps/server-mongodb-memory-mock\ app package during development and testing.
packages/cellix/server-mongodb-memory-mock-seedwork · high confidence
New shared Vitest configuration package for testing environments
Introduces the \@cellix/config-vitest\ package, providing pre-configured Vitest setups for different testing contexts. This includes a base configuration with Istanbul code coverage, a Node.js environment config with type-checking via tsgo, a Storybook integration config supporting Playwright browser testing across multiple instances, and a specific config for archunit tests. The package also exports utility functions and TypeScript configurations to standardize how tests are run and type-checked across the monorepo.
packages/cellix/config-vitest · high confidence
New storage account Bicep module with configurable services and policies
The \iac/storage-account\ directory now contains a new Bicep module structure that provisions a StorageV2 account with configurable blob, queue, and table services. Users can enable specific services via boolean flags (\enableBlobService\, \enableQueueService\, \enableTableService\) and define containers, queues, or tables through array parameters. The blob service module supports CORS configuration (origins, methods, headers, max age) and blob versioning. Additionally, the storage account supports lifecycle management policies to automatically delete blobs after a specified number of days, and enforces TLS 1.2 and HTTPS-only traffic.
iac/storage-account · high confidence
Removals
Removal of Azure Functions HTTP entry point
The \packages/api/src/index.ts\ file, which previously served as the entry point for the Azure Functions application, has been deleted. This file contained the registration of HTTP triggers for both REST and GraphQL endpoints, as well as the application start and terminate hooks that initialized and shut down the \startupObject\. Its removal indicates that the API service is no longer exposed via these specific Azure Functions HTTP handlers.
packages/api/src · high confidence
Removal of GraphQL server entry point and context module
The \packages/api-graphql/src/index.ts\ file, which previously exported the \graphHandlerCreator\ function to initialize the Apollo Server and wire it to Azure HTTP handlers, has been deleted. Additionally, the empty \Context\ class in \packages/api-graphql/src/context.ts\ has been removed. This change eliminates the local GraphQL server setup and its associated context definition from this package.
packages/api-graphql/src · high confidence
Removal of api-services-spec and api-services packages
The \api-services-spec\ and \api-services\ packages have been removed from the repository. This deletion eliminates the \StartupObject\ interface and the \startupObject\ class implementation that previously handled service lifecycle management (startup and shutdown states), along with their associated TypeScript configuration and Prettier formatting rules.
packages/api-services-spec · high confidence
Removal of legacy Azure Functions HTTP handler entry point
The \packages/api-rest/src/index.ts\ file has been deleted, removing the previous implementation of the Azure Functions HTTP handler entry point. This file previously exported the \HttpHandler\ type and a \restHandlerCreator\ function that returned a static "Hello World!" response, indicating that this specific wiring and entry point are no longer part of the API-rest package.
packages/api-rest/src · high confidence
Behavioural changes
API bootstrap restructured to use centralized infrastructure registry
The API application entry point has been refactored to initialize services via a centralized \Cellix\ infrastructure registry rather than direct instantiation. This change introduces environment-aware configuration for Azure Blob Storage and Queue Storage, switching to managed identity in production and connection strings in development. It also registers specific HTTP handlers for GraphQL and REST endpoints, configures Apollo Server with permissions middleware and query depth limits, and wires up event handlers and data sources through the new service context.
apps/api/src · high confidence
Apply patches to @azure/functions and storybook-addon-apollo-client
This change introduces two patch files to resolve compatibility issues with specific dependencies. The patch for @azure/functions (v4.11.0) adds the undici-types dependency and updates type imports to support modern web standards. The patch for storybook-addon-apollo-client (v10.0.0) provides an empty preset export, reflecting that the addon's functionality is now handled by manager and preview modules rather than a preset.
patches · high confidence
Extracted Azure Functions bootstrap into @cellix/api-core
The inlined \Cellix\ bootstrap class has been moved from the API application into a new \@cellix/api-core\ package. This package now owns the phased startup facade for Azure Functions API hosts, handling infrastructure service registration, context building, request-scoped application host creation, and HTTP handler binding. The observable behavior remains unchanged: \startUp()\ registers handlers and lifecycle hooks without starting services, while actual service startup, context creation, and host creation occur later during the Azure Functions \appStart\ hook. The API application now imports \Cellix\ from this new package instead of a local file.
packages/cellix/api-core · high confidence
Mock MongoDB service now seeds realistic community data
The \server-mongodb-memory-mock\ application has been refactored to initialize the in-memory database with a predefined set of seed data, including users, communities, roles, members, properties, and services. This change ensures that local development and testing environments start with a consistent, realistic state (e.g., the 'Riverside Community' with specific admin and member roles) rather than an empty database, reducing the setup effort required to reproduce scenarios.
apps/server-mongodb-memory-mock · high confidence
Mock OAuth2 server now supports multiple named OIDC configurations
The mock OAuth2 server has been refactored to support multiple distinct OIDC configurations, allowing different frontend portals to be served with their own specific settings. The server now automatically discovers portal configurations from \mock-oidc.json\ files located in application directories and registers each as a named OIDC provider. This enables testing scenarios where multiple applications or tenants require separate identity configurations, with user stores and subject resolution handled per portal rather than globally.
apps/server-oauth2-mock/src · high confidence
Mock OAuth2 server now supports multiple named OIDC portals with path-based routing
The mock OAuth2 server has been refactored to expose multiple named OpenID Connect portals via a single HTTP server, where each portal is accessible at a distinct path (e.g., \/{name}/.well-known/openid-configuration\). Configuration is now driven by \mock-oidc.json\ files located in each UI app directory, which map environment variable names for client IDs and redirect URIs rather than containing hardcoded values. This change introduces support for multiple login configurations per portal and per-user overlay files for local development, while removing support for the previous \mock-oidc.local.json\ claim overrides. The server automatically discovers these portals by scanning for UI app directories, allowing developers to manage distinct OIDC identities for different parts of the application through a unified mock service.
apps/server-oauth2-mock · high confidence
Fixes
Configure pre-commit hook to format staged files and verify
The pre-commit hook in .husky has been updated to automatically format staged files using the \format:staged\ script before running the \verify\ command. This ensures that code formatting is applied consistently to changes before they are committed, followed by a verification step to catch potential issues early in the development workflow.
.husky · high confidence
Test coverage
Added E2E test coverage for staff role management and authentication flows; Added architecture test for API dependency rules; Added archunit-tests package for OCom architecture verification; Added integration tests for MongoUnitOfWork; Added tests for the server-oauth2-mock-seedwork package; Added tests for ui-core public components; Initial E2E test infrastructure for ocom-verification; New API acceptance test suite for staff role management and community creation; New architectural fitness tests for the Cellix framework.
Dependencies
Initial monorepo structure and package definitions
This change introduces the foundational package.json definitions for the CellixJS monorepo, establishing the workspace structure with apps (api, docs, ui-community, ui-staff, server-mongodb-memory-mock, server-oauth2-mock) and shared packages (cellix, ocom, ocom-verification). It sets up the dependency graph using pnpm workspaces and catalogs, defining core tooling like TypeScript (tsgo), Vitest, Biome, and Vite, while also introducing specific libraries such as Ant Design, Apollo Client, and Azure Functions SDKs.
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.
Score
- CAI 47 → 47 (-0.8)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 63 → 63 (-0.4)
- Architecture 56 → 55 (-1.8)
- Maturity 60 → 87 (+26.8)
- Readiness 44 → 44 (+0.0)
- Security 54 → 48 (-5.5)
- Domain Modelling 51 → 51 (+0.0)
- Accessibility 47 → 45 (-1.5)
- Performance 60 → 60 (+0.0)
Resolved (25)
- ADR decides a question another record already decided (apps/docs/docs/decisions/0003-domain-driven-design.md)
- ADR decides a question another record already decided (apps/docs/docs/decisions/0005-authorization.md)
- ADR decides a question another record already decided (apps/docs/docs/decisions/0008-white-label.md)
- ADR decides a question another record already decided (apps/docs/docs/decisions/0011-bicep.md)
- ADR has no Consequences section (apps/docs/docs/decisions/0001-madr-architecture-decisions.md)
- ADR has no Consequences section (apps/docs/docs/decisions/0008-white-label.md)
- ADR has no Consequences section (apps/docs/docs/decisions/0010-react-router-loaders.md)
- Ambiguous naming for utility functions that likely perform similar string manipulation on URLs. normalizeUrl, normalizeOrigin, and normalizeBaseUrl have overlapping intents. Without distinct documentation, it is unclear when to use which, especially since 'Origin' and 'Base URL' are often used interchangeably in web contexts.
- Critical CVE: [GHSA redacted] (pnpm-lock.yaml)
- Critical CVE: [GHSA redacted] (pnpm-lock.yaml)
- Cross-context type ServiceTicketV1 (domain → persistence) (packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.repository.ts)
- Cross-context type ServiceTicketV1 (domain → persistence) (packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.repository.ts)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- Inconsistent parameter signature for resetting test server state. MongoMemory servers accept an optional seed data function to re-seed the database after reset, whereas the base TestServer interface does not accept this parameter. This forces implementers to either ignore the seed data or handle it outside the reset method, breaking the abstraction.
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium: security finding (details withheld)
- …and 5 more
New (121)
- ADR consequences name no cost (apps/docs/docs/decisions/0027-typescript-6-upgrade.md)
- ADR consequences name no cost (apps/docs/docs/decisions/0030-typescript-7-upgrade.md)
- ADR considers only one option (apps/docs/docs/decisions/0005-authorization.md)
- ADR considers only one option (apps/docs/docs/decisions/0009-cache-purging.md)
- ADR decides a question another record already decided (apps/docs/docs/decisions/0004-identity-access.md)
- ADR decides a question another record already decided (apps/docs/docs/decisions/0006-maps.md)
- Classify ADR enforcement: 0029: Turbo watch dev-mode (apps/docs/docs/decisions/0029-turbo-watch-dev-mode.md)
- Classify ADR enforcement: Addressing Node.js 16 End-of-Life in SonarCloud (apps/docs/docs/decisions/0015-sonarcloud.md)
- Classify ADR enforcement: Adopt Agent Skills Framework to Enforce MADR Standards in Code (apps/docs/docs/decisions/0024-madr-agent-skills.md)
- Classify ADR enforcement: Adopt Portless For Local Development (apps/docs/docs/decisions/0028-portless-local-development.md)
- Classify ADR enforcement: Adopt Rolldown for Azure Functions API Applications and Static GraphQL Code Generation (apps/docs/docs/decisions/0025-rolldown-azure-functions-graphql-codegen.md)
- Classify ADR enforcement: Automatically Refresh Screen on Application Update (apps/docs/docs/decisions/0009-cache-purging.md)
- Classify ADR enforcement: Azure Blob Storage and Client Uploads (apps/docs/docs/decisions/0032-azure-blob-storage-client-uploads.md)
- Classify ADR enforcement: Azure DevOps Monorepo Pipeline Architecture (apps/docs/docs/decisions/0020-azure-devops-monorepo-pipeline.md)
- Classify ADR enforcement: Azure Queue Storage via Typed Registered Services (apps/docs/docs/decisions/0033-azure-queue-storage-typed-services.md)
- Classify ADR enforcement: Bicep Resource Scoping Strategy (apps/docs/docs/decisions/0021-bicep-resource-scoping-strategy.md)
- Classify ADR enforcement: Bypassing SonarCloud Code Duplication Checks for Unit Tests (apps/docs/docs/decisions/0016-sonarcloud-code-duplication-checks.md)
- Classify ADR enforcement: Chrome Content Overrides for FeatureFlags.json (apps/docs/docs/decisions/0017-chrome-content-overrides.md)
- Classify ADR enforcement: Integrate Snyk for Security Scanning at Inception (apps/docs/docs/decisions/0022-snyk-security-integration.md)
- Classify ADR enforcement: Monorepo Structure with Turborepo (apps/docs/docs/decisions/0019-monorepo-turborepo.md)
- …and 101 more
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
CellixJs/cellixjs was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 8 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 0dda578701214d524dd961849c9ae3e39f882834 — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-45ab2cab63de.