@cplace/mcp-server 1.6.0 → 1.6.1

package/dist/widget-specifications/_research_from_ga_products/cf-cplace-api-common-config-metadata-SyncMetadataTable/research.md

@@ -1,168 +0,0 @@
-# SyncMetadataTable Widget Research
-
-## Widget Overview
-
-- **Widget ID:** `cf.cplace.api.common.config.metadata.SyncMetadataTable`
-- **Display Name:** "Synchronization status table"
-- **Repository:** `cplace-ecf`
-- **Definition Class:** `cf.cplace.ecf/src/main/java/cf/cplace/ecf/sync/metadata/extension/widget/SyncMetadataTableWidgetDefinition.java`
-- **Icon:** `cf-attribute-selection`
-
-## Short Description
-
-The SyncMetadataTable widget displays a table of all synchronization metadata entries associated with a specific synchronization configuration, showing the relationship and synchronization status between internal cplace entities and external system entities.
-
-## Purpose and Core Functionality
-
-The SyncMetadataTable widget is part of the Enterprise Connectivity Framework (ECF) and serves as the primary interface for monitoring synchronization status between cplace and external systems. It displays synchronization metadata entries that track:
-
-1. **Entity Relationships:** Links between internal cplace entities and their corresponding external system entities
-2. **Synchronization State:** Current status of each synchronized entity (NEW, MODIFIED, SYNCED, ORPHANED, DELETED)
-3. **Sync History:** Timestamps of last synchronization attempts and successful synchronizations
-4. **Error Information:** Error messages from failed synchronization attempts
-
-### Key Data Displayed
-
-The widget displays the following columns (varies by sync mode):
-
-| Column | Description |
-|--------|-------------|
-| Internal Entity | Reference to the cplace page being synchronized |
-| External Entity | Name of the corresponding entity in the external system |
-| Internal State | Synchronization state of the internal entity (OUTBOUND/BIDIRECTIONAL modes) |
-| External State | Synchronization state of the external entity (INBOUND/BIDIRECTIONAL modes) |
-| Last Synchronization Attempt | Timestamp of the most recent sync attempt |
-| Last Successful Synchronization | Timestamp of the last successful sync |
-| Last Outbound Error | Error message from outbound sync failures (OUTBOUND/BIDIRECTIONAL) |
-| Last Inbound Error | Error message from inbound sync failures (INBOUND/BIDIRECTIONAL) |
-
-## Use Cases
-
-### 1. Monitoring Synchronization Status
-Administrators use this widget to monitor the overall health of synchronizations between cplace and external systems. They can quickly identify:
-- Entities pending synchronization (state: NEW or MODIFIED)
-- Successfully synchronized entities (state: SYNCED)
-- Problematic entities with sync failures (via error message columns)
-- Orphaned entities no longer in sync scope (state: ORPHANED)
-
-### 2. Troubleshooting Sync Failures
-When synchronization issues occur, this widget provides detailed error messages and timestamps to help diagnose problems. Each row shows:
-- Which specific entity failed
-- When the failure occurred
-- The error message explaining the failure reason
-
-### 3. Managing Entity Assignments
-The widget includes an action to remove pages from synchronization ("Unassign pages"). This allows administrators to:
-- Remove entities that should no longer be synchronized
-- Clean up orphaned metadata entries
-- Manage the scope of synchronization configurations
-
-### 4. Validating Sync Configuration
-Before enabling a sync configuration, administrators can verify:
-- Which entities will be synchronized
-- The expected sync direction
-- Initial state of entities
-
-## Configuration Concepts
-
-### Widget Configuration Options
-
-The widget has minimal configuration:
-
-| Option | Type | Description |
-|--------|------|-------------|
-| HEIGHT | Number | Widget height (inherited from base mixin) |
-
-### Placement Restrictions
-
-The widget can **only** be embedded on ECF Sync Configuration pages. Attempting to add it to other page types will result in an error:
-> "SyncMetadataTableWidgetDefinition can only be used for Enterprise Connectivity synchronization configuration pages. Make sure that the corresponding Connector App is installed in this workspace"
-
-### Sync Mode Awareness
-
-The widget automatically adapts its displayed columns based on the sync configuration's mode:
-
-- **OUTBOUND:** Shows Internal State, Last Outbound Error
-- **INBOUND:** Shows External State, Last Inbound Error
-- **BIDIRECTIONAL:** Shows both Internal/External States and both error columns
-
-## Context and Related Widgets
-
-### ECF Widget Ecosystem
-
-The SyncMetadataTable is part of a suite of ECF widgets:
-
-1. **SyncMetadataTable** (this widget) - Displays sync status for a configuration
-2. **AttributeMappingTableWidgetDefinition** - Shows attribute mappings between internal and external types
-3. **ConnectorSyncConfigsTableWidgetDefinition** - Lists all sync configurations for a connector
-4. **ServerConnectionTableWidgetDefinition** - Manages server connections
-5. **CleanupConfigTableWidgetDefinition** - Manages cleanup job configurations
-
-### Default Layout Integration
-
-The widget is included in the default layout for ECF sync configuration pages as part of a tabbed interface:
-
-- **Configuration Tab:** Attributes widget + Attribute Mapping Table
-- **Synchronization Tab:** SyncMetadataTable widget (this widget)
-
-This tab structure is automatically applied to all ECF sync configuration types via `SyncConfigurationWidgetDefinitions.applyAlternativeLayouts()`.
-
-### Prerequisites and Dependencies
-
-To use this widget:
-1. The ECF plugin (`cf.cplace.ecf`) must be installed
-2. A Connector App must be deployed in the workspace
-3. The widget must be placed on a page of type `cf.cplace.ecf.syncConfiguration` or its subtypes
-
-### Underlying Data Model
-
-The widget reads from the `ExtSyncMetadata` built-in entity type, which is a non-custom persistent entity that stores:
-- Sync configuration reference
-- Internal entity reference (cplace page)
-- External entity identifiers (namespace, type, ID, name)
-- Synchronization states (internal and external)
-- Timestamps (last attempt, last success, last modification)
-- Error messages (inbound and outbound)
-
-### Table Actions
-
-The widget extends the standard table actions with:
-- **Remove from synchronization:** Allows bulk removal of selected entities from the sync configuration (removes the metadata entry, effectively unassigning the entity)
-
-Export actions are disabled because the `ExtSyncMetadata` built-in type doesn't support export jobs.
-
-## Technical Details
-
-### Class Hierarchy
-
-```
-GenericSearchAsTableWidgetDefinition
-  └── AbstractSyncConfigTableWidgetDefinition
-        └── SyncMetadataTableWidgetDefinition
-```
-
-### Key Implementation Classes
-
-- `SyncMetadataTableWidgetDefinition` - Widget definition and registration
-- `SyncMetadataTableSpecificationHandler` - Table data source and column configuration
-- `AbstractSyncConfigTableWidgetDefinition` - Base class with embedding validation
-- `ExtSyncMetadata` - Underlying data entity
-- `SyncMetadataRepository` - Data access interface
-- `SyncUnassignmentActionsExtension` - Custom table actions
-
-### Search Behavior
-
-The widget constructs its table search using:
-```java
-EcfPlugin.INSTANCE().getMetadataRepository()
-    .createSearch()
-    .syncConfiguration((CustomEntity) entity)
-    .build()
-    .getSearch();
-```
-
-This retrieves all metadata entries referencing the embedding sync configuration entity.
-
-### Link Display Behavior
-
-The widget sets `hideLinks()` to return `true`, meaning entity names are displayed as plain text rather than links. This is because metadata entries don't have their own page/presentation view - the data is only meaningful in the context of the table.

package/dist/widget-specifications/_research_from_ga_products/cf-cplace-breadcrumbs-breadcrumbsWidget/research.md

@@ -1,125 +0,0 @@
-# Breadcrumbs Widget Research
-
-**Widget ID:** `cf.cplace.breadcrumbs.breadcrumbsWidget`
-**Repository:** `cplace-paw`
-**Plugin:** `cf.cplace.breadcrumbs`
-
-## Widget Description
-
-The Breadcrumbs Widget displays a hierarchical navigation path from the current page to the workspace home page. It provides users with visual context about their location within the page hierarchy and enables quick navigation to parent pages.
-
-## Purpose
-
-This widget shows the hierarchical path to the home page of a workspace, helping users understand their current position within the page structure and navigate between hierarchical levels. The breadcrumbs are displayed as clickable links with a distinctive arrow-style visual design.
-
-## Core Functionality
-
-Based on the widget definition class (`BreadcrumbsWidgetDefinition.java`), the widget:
-
-1. **Retrieves Page Hierarchy**: Uses `Page.getPageByUid()` and `getPathToRoot()` to obtain the hierarchical path from the current page to the workspace root (BreadcrumbsWidgetDefinition.java:71-72)
-
-2. **Displays Path in Reverse**: Reverses the path list so it displays from root to current page (BreadcrumbsWidgetDefinition.java:73)
-
-3. **Renders Without Frame**: Configured with `showFrame() = false` and `isNoPadding() = true` for seamless integration into page layouts (BreadcrumbsWidgetDefinition.java:57-62)
-
-4. **Supports Additional Pages**: Allows configuration of additional pages to be displayed at the front of the breadcrumb trail via the `ADDITIONAL_PAGE` attribute (BreadcrumbsWidgetDefinition.java:79)
-
-## Visual Design
-
-The widget uses a distinctive arrow-style breadcrumb design with:
-- Alternating background colors for even/odd breadcrumb items
-- Arrow-shaped connectors between breadcrumb items (created with CSS borders)
-- Hover and active states for interactive feedback
-- Rounded corners on first and last items
-- 40px height with centered text (plugin.less:36-39)
-
-Visual example from screenshot (Breadcrumbs-001.png):
-```
-Sprint 4711/1 > Feature: Schedule Search in Schedule Selection Dialog > QA phase > Write test documents
-```
-
-## Use Cases
-
-### Primary Use Case: Page Hierarchy Navigation
-**When:** Users are viewing any page within a hierarchical workspace structure
-**Purpose:** Show the navigation path and enable quick navigation to parent pages
-**Example:** In a project management workspace, display the path from a task page through its parent sprint, feature, and project pages back to the workspace home
-
-### Use Case: Contextual Awareness
-**When:** Users need to understand where they are within a complex page hierarchy
-**Purpose:** Provide visual context about the current page's position in the structure
-**Example:** Help users understand that they are viewing a specific document that belongs to a QA phase, which is part of a larger feature, which belongs to a sprint
-
-### Use Case: Quick Navigation
-**When:** Users want to navigate to a parent or ancestor page
-**Purpose:** Enable one-click navigation to any page in the hierarchy without using back buttons
-**Example:** Quickly jump from a deep nested page directly to the workspace home or any intermediate level
-
-### Use Case: Custom Navigation Path
-**When:** Users want to add additional navigation links at the beginning of the breadcrumb trail
-**Purpose:** Include related pages or alternative entry points in the navigation path
-**Example:** Add a custom "Dashboard" or "Overview" page link at the start of the breadcrumb trail
-
-## Configuration Options
-
-### Main Configuration Attribute
-
-**Additional Pages** (`ADDITIONAL_PAGE`)
-- **Type:** Multi-Page Reference
-- **Multiplicity:** 0..* (any number)
-- **Description:** "Attach additional sides at the front" (messages_en.properties:5)
-- **Purpose:** Allows users to prepend additional page links to the beginning of the automatically generated breadcrumb path
-- **Use Case:** Add entry points or contextual pages that aren't part of the direct hierarchical path
-
-### Widget Display Settings
-
-The widget is configured with:
-- No frame/border around the widget content
-- No padding to allow seamless integration with page layouts
-- Icon: "cf-pase" (though this may be a typo in BreadcrumbsWidgetDefinition.java:49)
-
-## Technical Implementation Details
-
-### Java Implementation
-- **Definition Class:** `cf.cplace.breadcrumbs.script.BreadcrumbsWidgetDefinition`
-- **Configuration Type:** `BreadcrumbsWidgetTypes.BREADCRUMBS_WIDGET.TYPE`
-- **Key Method:** `getContentSubstitution()` creates template substitution with:
-  - `pathToRoot`: The list of pages from root to current page
-  - `additionalPages`: User-configured additional pages
-
-### Styling
-- **CSS Class:** `.cf-cplace-breadcrumbs-wrapper` containing `.cf-cplace-breadcrumbs`
-- **Customizable Variables:** Defined in `breadcrumbs-customizing-variables.less`
-  - Background colors (odd/even/hover/active)
-  - Font color
-  - Border color
-
-### Dependencies
-- Depends only on `cf.cplace.platform` (version 25.3.80)
-- No TypeScript or JavaScript assets (pure server-side rendering)
-
-## Relationship to Other Features
-
-### Core Platform Integration
-- **Pages:** Directly integrates with cplace's Page concept and hierarchy
-- **Workspaces:** Operates within the context of workspace home pages
-- **Layouts:** Typically added to page layouts to provide consistent navigation
-
-### Typical Placement
-Based on the screenshot and configuration (no frame, no padding), this widget is designed to be placed:
-- At the top of page layouts
-- Below the page title/header area
-- As a horizontal navigation bar spanning the page width
-
-## Notes
-
-- The widget only works with Page entities. When shown in a type definition layout where the entity is not a Page, `embeddingPage` will be null and an empty list is used (BreadcrumbsWidgetDefinition.java:70-72)
-- The breadcrumb path is automatically generated based on the page hierarchy, requiring no manual configuration for basic usage
-- The widget is purely presentational and uses server-side rendering (no client-side JavaScript)
-
-## Key Insights
-
-1. **Automatic Hierarchy**: The widget automatically derives the navigation path from the page structure, requiring minimal configuration
-2. **Flexible Extension**: The "additional pages" feature allows customization of the navigation path without breaking the automatic hierarchy
-3. **Consistent Navigation**: Provides a standard navigation pattern that can be applied across all pages in a workspace
-4. **Visual Design Focus**: The distinctive arrow-style design makes the navigation path immediately recognizable and visually distinct from other page content

package/dist/widget-specifications/_research_from_ga_products/cf-cplace-cboard-main-board/research.md

@@ -1,373 +0,0 @@
----
-date: 2026-01-16
-widget_id: cf.cplace.cboard.main.board
-repository: cplace-board
-status: complete
-tags: [widget, board, kanban, agile, card-view]
----
-
-# Board Widget Research
-
-**Widget ID**: `cf.cplace.cboard.main.board`
-**Repository**: `cplace-board`
-**Definition Class**: `/cf.cplace.cboard.main/src/main/java/cf/cplace/cboard/main/script/BoardWidgetDefinition.java`
-
-## 1. Widget Description
-
-The Board widget enables different agile working methods to be mapped using a configurable board. It displays any cplace pages as visual cards arranged in columns and swimlanes, supporting drag-and-drop to change card positions and status values.
-
-## 2. Purpose and Core Functionality
-
-### What It Does
-
-The Board widget transforms structured data (cplace pages) into a visual, interactive board interface where:
-
-- **Pages become cards**: Any cplace page can be displayed as a card on the board
-- **Attributes define layout**: Card placement is determined by attribute values (e.g., status, priority)
-- **Drag-and-drop updates**: Moving cards updates the underlying page attribute values
-- **Real-time sync**: Multiple users can work on the same board with automatic synchronization
-- **Flexible filtering**: Various filter options provide quick overview of relevant cards
-
-### Key Characteristics
-
-1. **Configurable Board Structure**
-   - Vertical columns (required) - typically representing workflow stages or status values
-   - Horizontal swimlanes (optional) - for grouping by additional criteria
-   - Can be static (predefined) or dynamic (auto-generated from attribute values)
-
-2. **Card Visualization**
-   - Title and description from page attributes
-   - Type icon and color coding
-   - Tags and custom icons
-   - Assignees with avatars
-   - Date information
-   - Attachments
-
-3. **Interactive Features**
-   - Drag-and-drop cards between columns/swimlanes
-   - Click to open card details or edit dialog
-   - Filter by type, assignee, tags, date range
-   - Hide/show columns and swimlanes
-   - Text search across cards
-   - Recent changes highlighting
-
-## 3. Use Cases
-
-### Primary Use Cases
-
-1. **Kanban Board**
-   - **When**: Managing work items through workflow stages
-   - **Example**: Software development tasks with columns: Backlog → In Progress → Review → Done
-   - **Configuration**: Status attribute mapped to columns, optional swimlanes by priority or team
-   - **Benefit**: Visual workflow management with drag-and-drop status updates
-
-2. **Sprint Planning Board**
-   - **When**: Organizing work items for agile sprints
-   - **Example**: User stories and tasks grouped by sprint
-   - **Configuration**: Sprint attribute mapped to swimlanes, status mapped to columns
-   - **Benefit**: Clear view of work distribution across sprints
-
-3. **Project Portfolio View**
-   - **When**: Managing multiple projects with various stages
-   - **Example**: Projects categorized by phase and department
-   - **Configuration**: Project phase as columns, department as swimlanes
-   - **Benefit**: High-level overview of project portfolio status
-
-4. **Order Tracking Board**
-   - **When**: Tracking orders or requests through fulfillment stages
-   - **Example**: Customer orders with status: Open → Processing → Delivering → Closed
-   - **Configuration**: Order status as columns, customer or priority as swimlanes
-   - **Benefit**: Visual order pipeline with quick status updates
-
-5. **Event Planning Timeline**
-   - **When**: Managing events across time periods
-   - **Example**: Events scheduled across weeks or months
-   - **Configuration**: Date ranges as dynamic columns, event type as swimlanes
-   - **Benefit**: Time-based visualization of event distribution
-
-6. **Bug Tracking Board**
-   - **When**: Managing software defects through resolution lifecycle
-   - **Example**: Bugs categorized by severity and status
-   - **Configuration**: Bug state as columns (New → In Progress → Testing → Closed), severity as swimlanes
-   - **Benefit**: Clear overview of bug backlog and resolution progress
-
-### When to Use This Widget
-
-**Choose the Board widget when you need to:**
-
-- Visualize workflow stages or process steps
-- Enable quick status updates via drag-and-drop
-- Provide overview of work distribution across categories
-- Support collaborative work with multiple users
-- Track items through time-based progression
-- Apply complex filtering to focus on relevant items
-
-**Don't use this widget when:**
-
-- You need detailed tabular data analysis (use Table widget instead)
-- The data doesn't have a clear workflow or categorization
-- You need hierarchical tree structures (use Tree widget instead)
-- The primary need is reporting/analytics (use Chart widget instead)
-
-## 4. Configuration Concepts
-
-### 4.1 Search Configurations
-
-**Purpose**: Define which pages appear as cards on the board
-
-**Key Concept**: A board can display cards from multiple searches, each search can target:
-- Specific page types (e.g., only "Order" pages)
-- Specific search criteria (e.g., all open tasks in current space)
-- Different attribute configurations (what to display on cards)
-
-**Configuration Elements**:
-- `searchId`: Reference to a cplace search
-- `attributesConfiguration`: Defines what attributes display on cards
-  - Description attribute
-  - Date attribute for filtering/display
-  - Tags attribute
-  - Custom icons attributes
-  - Display attributes (shown on card)
-
-### 4.2 Column Mapping
-
-**Purpose**: Define vertical columns and how cards map to them
-
-**Key Concepts**:
-
-**Static Columns**:
-- Predefined, fixed set of columns
-- Explicitly defined column labels and mapped values
-- Example: "To Do", "In Progress", "Done"
-
-**Dynamic Columns**:
-- Auto-generated from attribute values
-- Columns appear/disappear based on actual data
-- Example: Auto-create columns for each distinct status value
-- Special support for date-based columns (by year, quarter, month, week, day)
-
-**Configuration Elements**:
-- `dynamic`: Boolean flag for static vs. dynamic
-- `mappedAttributes`: Which page attributes determine column placement
-- `elements`: Static column definitions (labels, icons, mapped values)
-- `timeGranularity`: For date-based dynamic columns (YEAR, QUARTER, MONTH, WEEK, DAY)
-- `dateRange`: Time range for date-based columns
-
-### 4.3 Swimlane Mapping
-
-**Purpose**: Define optional horizontal rows for additional grouping
-
-**Key Concepts**:
-- Uses same configuration structure as columns
-- Optional - board can have no swimlanes (single row)
-- Creates grid layout: each cell is a column × swimlane intersection
-- Cards placed in cells based on both column AND swimlane attribute values
-
-**Common Patterns**:
-- Group by priority (High, Medium, Low)
-- Group by team or person
-- Group by product or project
-- Group by customer or department
-
-### 4.4 Visual Components
-
-**Purpose**: Toggle UI features on/off
-
-**Available Toggles**:
-
-| Component | Purpose | Default |
-|-----------|---------|---------|
-| Unmapped Cards Container | Sidebar showing cards that don't match any column/swimlane | Off |
-| Card Details View | Detail panel when clicking a card | Off |
-| Space After Last Column | Visual spacing after the last column | On |
-| Recent History Button | Button to highlight recently changed cards | Off |
-| Recent History Time Range | How many weeks count as "recent" | 2 weeks |
-| Add Card Button | "+" button to create new cards | On |
-
-### 4.5 Widget Customization
-
-**Title**: Optional multilingual widget title
-**Height**: Optional fixed height in pixels (otherwise auto-sizes)
-
-## 5. Integration and Context
-
-### Relationship to Other Widgets
-
-**Can be embedded in**:
-- Connected Attributes Group Widget (allows conditional display based on page attributes)
-
-**Works well with**:
-- Table Widget: For detailed list view of the same data
-- Chart Widget: For analytics on the same dataset
-- Search Widget: For advanced filtering capabilities
-
-### Data Model Requirements
-
-The Board widget works with:
-- Any cplace page type
-- Pages must have attributes that can serve as:
-  - Column mapping source (e.g., status, phase)
-  - Optional swimlane mapping source (e.g., priority, team)
-  - Display attributes (title, description, dates, tags, icons)
-
-### Platform Features Used
-
-- **Search System**: To query which pages become cards
-- **Attribute System**: To map pages to columns/swimlanes and display information
-- **Permission System**: Cards respect page-level read/write permissions
-- **Real-time Sync**: Automatic board updates when pages change
-- **Drag-and-Drop**: Platform drag-and-drop infrastructure
-- **State Persistence**: User preferences saved (filters, column widths, visibility)
-
-## 6. Technical Architecture Insights
-
-### Backend Architecture
-
-**Definition Layer** (`BoardWidgetDefinition.java:30-129`):
-- Declares widget type: `cf.cplace.cboard.main.board`
-- Defines configuration type: `BOARD_CONFIGURATION`
-- Handles widget rendering via `getContentSubstitution()`
-- Supports configuration migration for backwards compatibility
-
-**Configuration Factory** (`BoardWidgetConfigurationFactory.java`):
-- Transforms widget configuration into runtime DTO
-- Prepares all URLs for backend handlers
-- Includes feature flags and metadata
-
-**Backend Handlers**:
-- `loadBoardHandlerUrl`: Load board structure (columns, swimlanes, metadata)
-- `loadCardsHandlerUrl`: Load/reload card data
-- `addCardUrl`: Create new cards
-- `editCardUrl`: Edit existing cards
-- `changeCardPositionUrl`: Handle drag-and-drop updates
-- `boardSyncUrl`: Real-time synchronization endpoint
-
-### Frontend Architecture
-
-**Main Controller** (`cplaceCboardMainWidget.ts`):
-- Manages widget lifecycle and state
-- Coordinates card loading and rendering
-- Handles user interactions (drag-and-drop, clicks, filters)
-- Manages real-time synchronization polling
-- Persists user state (filter selections, column widths, scroll position)
-
-**Key Services**:
-- `BoardInstance`: Board data model and card management
-- `FilterService`: Filter logic and state
-- `SortableWrapperService`: Drag-and-drop functionality
-- `BoardSyncService`: Real-time synchronization
-- `GridService`: Column layout and resizing
-- `UserStateService`: Persist user preferences
-
-**State Management**:
-- Session storage: Temporary state (scroll position, active filters)
-- Local storage: Persistent preferences (card expansion level)
-- Backend persistence: User state across sessions (column widths, visibility)
-
-### Data Flow
-
-```
-1. Widget Configuration (stored in page layout)
-   ↓
-2. Backend: ConfigurationFactoryImpl reads attributes
-   ↓
-3. Backend: BoardWidgetConfigurationFactory creates DTO
-   ↓
-4. JSON serialization → HTML data attribute
-   ↓
-5. Frontend: Parse configuration and initialize board
-   ↓
-6. Load board structure (columns, swimlanes)
-   ↓
-7. Load cards based on search configurations
-   ↓
-8. Render grid and cards
-   ↓
-9. User interactions → Backend handlers → Reload affected cards
-   ↓
-10. Periodic sync checks for external changes
-```
-
-## 7. Advanced Features
-
-### Dynamic Board Elements
-
-- Columns and swimlanes can be auto-generated from attribute values
-- Dynamic elements update automatically when new values appear
-- Performance limits: Maximum number of dynamic elements configurable
-- Notification system warns users when elements are auto-hidden for performance
-
-### Date-Based Boards
-
-- Special support for time-based columns (weeks, months, quarters)
-- Date range configuration limits the time window
-- Useful for timeline views, release planning, event scheduling
-
-### Unmapped Cards Sidebar
-
-- Shows cards that don't match any column/swimlane combination
-- Useful when card attribute values are incomplete or invalid
-- Can be toggled open/close by users
-- Cards can be dragged from sidebar to board
-
-### Recent Changes Tracking
-
-- Highlight cards modified within a time window (configurable weeks)
-- Helps teams focus on recently updated items
-- Button in toolbar to activate/deactivate highlighting
-
-### Card Details Panel
-
-- Side panel showing full page details
-- Allows editing without leaving the board
-- Changes save automatically and update board
-- Form validation prevents board refresh during editing
-
-### Multi-User Collaboration
-
-- Automatic synchronization polls backend for changes
-- Pauses polling when widget not visible (performance optimization)
-- Pauses when browser tab not active
-- Conflict detection and notification system
-
-## 8. Performance Considerations
-
-### Card Limits
-
-- Configurable limit per search configuration
-- Default and minimum values enforced
-- Prevents performance issues with very large datasets
-
-### Dynamic Element Limits
-
-- Maximum number of dynamic columns/swimlanes
-- Auto-hide elements beyond limit with user notification
-- Users can manually show/hide elements as needed
-
-### Loading Strategies
-
-- Initial load: Load board structure and all cards
-- Incremental updates: Load only changed cards
-- Lazy sidebar loading: Unmapped cards loaded only when sidebar opened
-- Smart polling: Adjusts frequency based on widget visibility
-
-## 9. Code References
-
-### Backend (Java)
-
-- Widget Definition: `cf.cplace.cboard.main/src/main/java/cf/cplace/cboard/main/script/BoardWidgetDefinition.java:30-129`
-- Configuration Types: `cf.cplace.cboard.main/src/main/java/cf/cplace/cboard/main/MainWidgetTypes.java:21-89`
-- Configuration Factory: `cf.cplace.cboard.main/src/main/java/cf/cplace/cboard/main/script/BoardWidgetConfigurationFactory.java`
-- Localization: `cf.cplace.cboard.main/src/main/resources/cf/cplace/cboard/main/messages_en.properties:219-220`
-
-### Frontend (TypeScript)
-
-- Main Widget Controller: `cf.cplace.cboard.main/assets/ts/core/cplaceCboardMainWidget.ts:53-1327`
-- Widget Configuration Interface: `cf.cplace.cboard.main/assets/ts/core/cplaceCboardMainWidget.ts:1146-1175`
-- Card Model: `cf.cplace.cboard.main/assets/ts/card/CardModel.ts:3-47`
-- Board Instance: `cf.cplace.cboard.main/assets/ts/core/BoardInstance.ts`
-
-## 10. Related Documentation
-
-- Previous research on configuration attributes: `/specs/2026-01-14_board-widget-configuration-attributes/research.md`
-- Plugin description (messages_en.properties:2): "This app provides the 'Board' widget which offers a flexible option for mapping various agile working methods."