Merge branch 'main' of github.com:finos/traderX into ng-update

Author: mimiflynn

.github/ISSUE_TEMPLATE/meeting-minutes.md

@@ -45,8 +45,6 @@ YYYYMMDD - time
 - [ ] ...
 
 ### Zoom info
-https://zoom.us/j/96264933811
-Meeting ID: 962 6493 3811
-Passcode: 532953
+- [Meeting link](https://zoom-lfx.platform.linuxfoundation.org/meeting/97085484379?password=ec271ed7-f068-4e6d-bcd7-c3171d254b8e)
+- [Registration link](https://zoom-lfx.platform.linuxfoundation.org/meeting/97085484379?password=ec271ed7-f068-4e6d-bcd7-c3171d254b8e&invite=true)
 
-Find your local number: https://zoom.us/u/aHHeTieyi

.github/workflows/generate-openapi.yml

@@ -0,0 +1,27 @@
+name: Generate OpenAPI Specs
+
+on:
+  workflow_dispatch:
+
+jobs:
+  generate:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Generate OpenAPI specs
+        run: scripts/generate-openapi.sh --start-compose
+
+      - name: Commit generated specs
+        run: |
+          git config --local user.email "github-actions[bot]@users.noreply.github.com"
+          git config --local user.name "github-actions[bot]"
+          git add **/openapi.json
+          git diff --staged --quiet || git commit -m "chore: refresh OpenAPI specs"
+          git push

.github/workflows/render-c4-diagrams.yml

@@ -0,0 +1,68 @@
+name: Render C4 Diagrams
+
+on:
+  push:
+    paths:
+      - 'docs/c4/workspace.dsl'
+    branches:
+      - main
+  pull_request:
+    paths:
+      - 'docs/c4/workspace.dsl'
+  workflow_dispatch:  # Allow manual trigger
+
+jobs:
+  render:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Set up Java
+        uses: actions/setup-java@v4
+        with:
+          distribution: 'temurin'
+          java-version: '17'
+
+      - name: Install Graphviz
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y graphviz
+
+      - name: Render C4 diagrams
+        run: |
+          # Download Structurizr CLI
+          curl -L https://github.com/structurizr/cli/releases/download/v2024.07.03/structurizr-cli.zip -o structurizr-cli.zip
+          unzip -o structurizr-cli.zip -d structurizr-cli
+          
+          cd docs/c4
+          
+          # Export to Graphviz DOT format (produces structurizr-{view-key}.dot files)
+          ../../structurizr-cli/structurizr.sh export -workspace workspace.dsl -format dot -output .
+          
+          # Convert DOT to PNG using Graphviz with curved splines
+          for dot_file in structurizr-*.dot; do
+            output_name="${dot_file%.dot}.png"
+            dot -Gsplines=curved -Tpng "$dot_file" -o "$output_name"
+          done
+          
+          # Clean up DOT files (keep only PNGs)
+          rm -f *.dot
+          
+          # List generated files
+          echo "Generated files:"
+          ls -la structurizr-*.png
+
+      - name: Commit rendered diagrams
+        if: github.event_name == 'push'
+        run: |
+          git config --local user.email "github-actions[bot]@users.noreply.github.com"
+          git config --local user.name "github-actions[bot]"
+          git add docs/c4/*.png
+          git diff --staged --quiet || git commit -m "chore: auto-render C4 diagrams from workspace.dsl"
+          git push

.gitignore

@@ -8,6 +8,10 @@ build/
 # Excluding Local Build folder for company-specific building
 .corp
 
+# Structurizr Lite generated files
+docs/c4/workspace.json
+docs/c4/.structurizr
+
 # Exclude package-lock to avoid company builds overriding standard locations
 package-lock.json
 yarn.lock

AGENTS.md

@@ -0,0 +1,66 @@
+# AGENTS.md
+
+This repository is the FINOS TraderX sample trading application. It is intentionally simple, non-production, and designed for local experimentation across a distributed set of services.
+
+## Start here (project context)
+- `README.md` for overall purpose and run modes.
+- `docs/running.md` for default ports, startup sequences, and environment variables.
+- `docs/README.md`, `docs/overview.md`, and `docs/flows.md` for architecture and sequence flows.
+- `docs/c4/workspace.dsl` for the C4 diagram source (use Structurizr Lite to render).
+
+## Repository map (service roots)
+- `database/` (H2 database)
+- `reference-data/` (Node/NestJS reference data)
+- `trade-feed/` (Node/Socket.IO pub-sub)
+- `people-service/` (.NET)
+- `account-service/` (Java/Spring Boot)
+- `position-service/` (Java/Spring Boot)
+- `trade-service/` (Java/Spring Boot)
+- `trade-processor/` (Java/Spring Boot)
+- `web-front-end/` (Angular + React clients)
+- `docs/` and `website/` (documentation site)
+- `gitops/` and `ingress/` (K8s/Tilt and ingress config)
+
+## Quick run options
+- Docker Compose (full system): from repo root, `docker compose up` (see `README.md`).
+- Kubernetes/Tilt: see `gitops/local/Tiltfile` and `docs/running.md` for `tilt up`.
+- Manual run: see `docs/running.md` for the recommended startup sequence and port env vars.
+
+## Service-level guidance
+- Each service has a `README.md` with run details and prerequisites. Read that before editing.
+- OpenAPI specs are generated at runtime (Swagger) and saved as `*/openapi.json` when you run `scripts/generate-openapi.sh`. Swagger UI is typically exposed at `/swagger-ui.html` (or service-specific Swagger routes).
+- Java services use Gradle wrapper (`./gradlew`) from their service directory.
+- Node services use their local `package.json` scripts.
+- `web-front-end/` contains both Angular and React implementations; check each subfolder's README.
+
+## When making changes
+- Prefer small, targeted edits in the service you are touching; do not refactor cross-service behavior unless requested.
+- If behavior or APIs change, refresh the OpenAPI specs via `scripts/generate-openapi.sh` and update any relevant docs in `docs/`.
+- Keep the non-production, demo nature of the project in mind.
+
+## Keeping diagrams in sync
+When adding, removing, or changing services or their interactions, update **all** relevant diagrams:
+
+1. **C4 diagram** (`docs/c4/workspace.dsl`) - The Structurizr DSL is the source of truth for architecture. PNG images are auto-rendered by GitHub Actions on push.
+2. **Mermaid diagrams** in `docs/overview.md` (simplified architecture) and `docs/flows.md` (sequence diagrams).
+3. **Component table** in `README.md` if adding/removing services.
+
+The C4 DSL and Mermaid diagrams should stay consistent—if you update one, check if the other needs the same change.
+
+## Documentation and website
+The project has two content surfaces that may overlap:
+1. **`docs/`** - Markdown files served by Docusaurus (architecture, flows, running instructions)
+2. **`website/src/components/`** - React components for the landing page (feature highlights, intro text)
+
+**Avoid duplication**: The landing page is marketing-style (logo, tagline, feature cards, CTAs). The `docs/` folder is the reference material. If you add content, decide which surface it belongs to—don't put the same text in both places.
+
+**Project history**: When making **major changes** (new services, architectural shifts, significant features), add an entry to `docs/project-history.md`. Minor fixes and routine maintenance do not need to be recorded.
+
+**Relative links in docs**: Links like `../account-service` work on GitHub. The Docusaurus remark plugin (`website/src/remark/transformRelativeLinks.js`) converts them to full GitHub URLs at build time. Keep using relative links in `docs/` markdown files.
+
+## Useful files by task
+- Architecture/flows: `docs/overview.md`, `docs/flows.md`, `docs/c4/workspace.dsl`
+- Local run and ports: `docs/running.md`
+- Docker/K8s: `docker-compose.yml`, `gitops/local/Tiltfile`
+- Front-end: `web-front-end/angular/README.md`, `web-front-end/react/README.md`
+- Docs site: `website/README.md`, `docs/`