feat: enhance deployment results with file paths, hierarchical grouping, and resource type indicators (#30)

* Initial plan

* feat: enhance deployment logging with file paths and building block indicators

Co-authored-by: vobu <6573426+vobu@users.noreply.github.com>

* test(deploy): add comprehensive tests for deployment logging enhancements

Co-authored-by: vobu <6573426+vobu@users.noreply.github.com>

* refactor: use logger.info consistently instead of console.log

Co-authored-by: vobu <6573426+vobu@users.noreply.github.com>

* refactor: move file paths to deployment results table

Per feedback, file names and paths now appear as a column in the results
table after successful deployment, rather than being listed before deployment.
Building block indicators (🧱) are preserved in the File column.

Co-authored-by: vobu <6573426+vobu@users.noreply.github.com>

* refactor: simplify redundant ternary operators

Cleaned up unnecessary ternary checks - Map.get() already returns undefined
for missing keys.

Co-authored-by: vobu <6573426+vobu@users.noreply.github.com>

* test: add batched deployment test for process application

Added comprehensive test that verifies batched deployment behavior when
.process-application file is present. The test verifies:
- Batch deployment note is shown
- All resources in the directory are deployed together (2 files)
- Deployment attempt is made with all resources as a batch

Co-authored-by: vobu <6573426+vobu@users.noreply.github.com>

* refactor: improve test code quality and robustness

- Increased timeout to 10s for slower CI environments
- Extracted executeDeployment helper to reduce code duplication
- Improved error handling for successful deployment scenario

Co-authored-by: vobu <6573426+vobu@users.noreply.github.com>

* refactor: group process application resources in table instead of note

Per feedback, removed the general "(batch deployment from process application)"
note and instead mark process application resources with 📦 emoji in the
results table, grouped alongside building blocks and standalone resources.

- Added isProcessApplication field to ResourceFile interface
- Detect .process-application files during resource collection
- Updated sorting to group: building blocks → process apps → regular
- Show 📦 emoji for process application resources in table
- Updated tests to reflect new behavior (no more batch note)
- Updated documentation with new output examples

Co-authored-by: vobu <6573426+vobu@users.noreply.github.com>

* test: add mixed resources sample

* test: add simple BPMN process definition

* fix: properly group nested resources in building blocks and process applications

Resources are now correctly grouped based on their folder hierarchy, not just
immediate parent. All resources in a folder with _bb-* or .process-application
(including nested subdirectories) are grouped together.

- Added findGroupRoot() to traverse up directory tree
- Added groupPath field to track which group a resource belongs to
- Updated sorting to group by groupPath within BB and PA categories
- Added test for mixed resources with nested structure
- Updated documentation to explain hierarchical grouping

Co-authored-by: vobu <6573426+vobu@users.noreply.github.com>

* refactor: improve cross-platform path handling and type safety

- Use relative() for cross-platform path comparison instead of startsWith()
- Improve type safety with discriminated union for findGroupRoot return type
- Ensures proper behavior on Windows with different drive letters

Co-authored-by: vobu <6573426+vobu@users.noreply.github.com>

* docs: update README to include deployment from multiple paths

* refactor: enhance deployment log output by grouping resources and normalizing structure

* chore: update version to 2.0.0-alpha.4 in package.json

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: vobu <6573426+vobu@users.noreply.github.com>
Co-authored-by: Volker Buzek <dev@metalodge.com>

Author: Copilot

EXAMPLES.md

@@ -224,9 +224,76 @@ c8 deploy
 # Deploys all BPMN/DMN/Form files in specified directory and subdirectories
 c8 deploy ./my-project
 
-# Building block folders (containing _bb- in name) are prioritized
-# Order: _bb-* folders first, then other files
-```
+# Building block folders (containing _bb- in name) are prioritized and marked with 🧱
+# Process applications (folders with .process-application file) are marked with 📦
+# Example output:
+#   Deploying 4 resource(s)...
+#   ✓ Deployment successful [Key: 123456789]
+#   
+#   File                              | Type    | ID              | Version | Key
+#   ----------------------------------|---------|-----------------|---------|-------------------
+#   🧱 _bb-shared/common-process.bpmn | Process | common-process  | 1       | 2251799813685249
+#   📦 my-app/process.bpmn            | Process | my-proc         | 1       | 2251799813685250
+#   📦 my-app/decision.dmn            | Decision| my-dec          | 1       | 2251799813685251
+#   processes/order-process.bpmn      | Process | order-process   | 1       | 2251799813685252
+```
+
+### Process Application Deployment
+
+If a directory contains a `.process-application` file, **all resources in that directory and its subdirectories** are marked with the 📦 emoji in the deployment results table. Resources are grouped together based on their location:
+
+```bash
+# Directory structure:
+# my-project/
+#   _bb-shared/
+#     common.bpmn
+#     nested/
+#       util.bpmn        # Also part of _bb-shared group
+#   my-app/
+#     .process-application
+#     process.bpmn
+#     subfolder/
+#       form.form        # Also part of my-app group
+#   standalone.bpmn
+
+c8 deploy ./my-project
+
+# Output shows resources grouped by their folder hierarchy:
+# Deploying 5 resource(s)...
+# ✓ Deployment successful [Key: 123456789]
+#
+# File                            | Type    | ID            | Version | Key
+# --------------------------------|---------|---------------|---------|-------------------
+# 🧱 _bb-shared/common.bpmn       | Process | common        | 1       | 2251799813685249
+# 🧱 _bb-shared/nested/util.bpmn  | Process | util          | 1       | 2251799813685250
+# 📦 my-app/process.bpmn          | Process | my-proc       | 1       | 2251799813685251
+# 📦 my-app/subfolder/form.form   | Form    | form-id       | 1       | 2251799813685252
+# standalone.bpmn                 | Process | standalone    | 1       | 2251799813685253
+```
+
+### Resource Grouping Rules
+
+Resources are automatically grouped based on their folder hierarchy:
+
+1. **Building Block Groups** - All resources in a folder with `_bb-` in the name (and its subdirectories) belong to the same group and are marked with 🧱
+2. **Process Application Groups** - All resources in a folder containing `.process-application` file (and its subdirectories) belong to the same group and are marked with 📦
+3. **Standalone Resources** - Resources not in a building block or process application folder are treated as standalone
+
+In the deployment output:
+- Building block groups are listed first, grouped together
+- Process application groups are listed next, grouped together
+- Standalone resources are listed last
+
+### Deployment Output Details
+
+The deployment results table shows:
+- **File column** - Shows the file name with relative path
+  - 🧱 emoji indicates building block resources (from `_bb-*` folders, including nested files)
+  - 📦 emoji indicates process application resources (from folders with `.process-application` file, including nested files)
+- **Type column** - Resource type (Process, Decision, or Form)
+- **ID column** - The process/decision/form ID
+- **Version column** - Version number assigned by Camunda
+- **Key column** - Unique key assigned by Camunda
 
 ### Important: Duplicate Process IDs
 

IMPLEMENTATION.md

@@ -43,7 +43,7 @@ All requirements from the plan have been successfully implemented and tested.
    - **Jobs** (`jobs.ts`): list, activate, complete, fail
    - **Messages** (`messages.ts`): publish, correlate
    - **Topology** (`topology.ts`): get cluster topology
-   - **Deployments** (`deployments.ts`): deploy with `_bb-` folder prioritization and duplicate ID validation
+   - **Deployments** (`deployments.ts`): deploy with `_bb-` folder prioritization, duplicate ID validation, results table with file paths, building block indicators (🧱), and process application indicators (📦 for folders with `.process-application` file)
    - **Run** (`run.ts`): deploy + create process instance
    - **Profiles** (`profiles.ts`): list, add, remove
    - **Session** (`session.ts`): use profile/tenant, output format

README.md

@@ -9,7 +9,9 @@ A minimal-dependency CLI for Camunda 8 operations built on top of `@camunda8/orc
 - **Profile Management**: Store and manage multiple cluster configurations
 - **Camunda Modeler Integration**: Automatically import and use profiles from Camunda Modeler
 - **Plugin System**: Extend c8ctl with custom commands via npm packages
-- **Building Block Deployment**: Automatic prioritization of `*_bb-*` folders during deployment
+- **Building Block Deployment**: Automatic prioritization of `*_bb-*` folders during deployment, marked with 🧱 in results
+- **Process Application Support**: Resources in folders with `.process-application` file marked with 📦 in results
+- **Enhanced Deployment Results**: Table view showing file paths, visual indicators, resource details, and versions
 - **Watch Mode**: Monitors a folder for changes to `*.{bpmn,dmn,form}` and auto-redeploys 
 - **Flexible Output**: Switch between human-readable text and JSON output modes
 
@@ -101,6 +103,9 @@ c8ctl deploy ./my-process.bpmn
 # Deploy current directory
 c8ctl deploy
 
+# Deploy from multiple paths
+c8ctl deploy ./processes ./forms ./building-blocks
+
 # Watch mode (using alias 'w')
 c8ctl w
 c8ctl watch

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camunda8/cli",
-  "version": "2.0.0-alpha.2",
+  "version": "2.0.0-alpha.4",
   "description": "Camunda 8 CLI - minimal-dependency CLI for Camunda 8 operations",
   "type": "module",
   "engines": {