Merge branch 'main' into piotrkorkus_codeql_upload

Author: FScholPer

.devcontainer/devcontainer.json

@@ -1,6 +1,6 @@
 {
   "name": "eclipse-s-core",
-  "image": "ghcr.io/eclipse-score/devcontainer:v1.3.0",
+  "image": "ghcr.io/eclipse-score/devcontainer:v1.7.0",
   "mounts": [
     "source=/var/run/docker.sock,target=/var/run/docker.sock,type=bind"
   ],

.devcontainer/prepare_workspace.sh

@@ -1,4 +1,16 @@
 #!/bin/bash
+# *******************************************************************************
+# Copyright (c) 2026 Contributors to the Eclipse Foundation
+#
+# See the NOTICE file(s) distributed with this work for additional
+# information regarding copyright ownership.
+#
+# This program and the accompanying materials are made available under the
+# terms of the Apache License Version 2.0 which is available at
+# https://www.apache.org/licenses/LICENSE-2.0
+#
+# SPDX-License-Identifier: Apache-2.0
+# *******************************************************************************
 set -euo pipefail
 
 # Install pipx

.github/workflows/build_and_test_ebclfsa.yml

@@ -28,7 +28,7 @@ jobs:
     name: aarch64
     runs-on: ubuntu-latest
     container:
-      image: ghcr.io/eclipse-score/devcontainer:v1.1.0
+      image: ghcr.io/eclipse-score/devcontainer:v1.7.0
     steps:
       - name: Clean disk space
         uses: eclipse-score/more-disk-space@v1

.github/workflows/copyright.yml

@@ -0,0 +1,35 @@
+# *******************************************************************************
+# Copyright (c) 2026 Contributors to the Eclipse Foundation
+#
+# See the NOTICE file(s) distributed with this work for additional
+# information regarding copyright ownership.
+#
+# This program and the accompanying materials are made available under the
+# terms of the Apache License Version 2.0 which is available at
+# https://www.apache.org/licenses/LICENSE-2.0
+#
+# SPDX-License-Identifier: Apache-2.0
+# *******************************************************************************
+name: Copyright check
+on:
+  pull_request:
+    types: [opened, reopened, synchronize]
+  merge_group:
+    types: [checks_requested]
+jobs:
+  copyright-check:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+      - name: Set up Python 3
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+      # Runs the `copyright` hook from .pre-commit-config.yaml (cr_checker from
+      # eclipse-score/tooling). The hook reports any file missing a copyright
+      # header and fails the job, gating PRs without touching Bazel.
+      - name: Run cr_checker via pre-commit
+        uses: pre-commit/action@v3.0.1
+        with:
+          extra_args: copyright --all-files

.pre-commit-config.yaml

@@ -0,0 +1,26 @@
+# *******************************************************************************
+# Copyright (c) 2026 Contributors to the Eclipse Foundation
+#
+# See the NOTICE file(s) distributed with this work for additional
+# information regarding copyright ownership.
+#
+# This program and the accompanying materials are made available under the
+# terms of the Apache License Version 2.0 which is available at
+# https://www.apache.org/licenses/LICENSE-2.0
+#
+# SPDX-License-Identifier: Apache-2.0
+# *******************************************************************************
+# Runs cr_checker (copyright header check) directly from the eclipse-score/tooling
+# repo as a pre-commit hook, instead of via the Bazel `//:copyright` target.
+#
+# Rationale (see https://github.com/eclipse-score/reference_integration/issues/166):
+# the Bazel target pulls in the docs() -> needs_json -> @score_process graph, which
+# fails to resolve because score_process/score_platform are dev_dependencies in the
+# score modules and are therefore invisible when reference_integration aggregates
+# them. The pre-commit hook runs the checker as a standalone script over the repo's
+# files, so it is unaffected by Bazel module resolution.
+repos:
+  - repo: https://github.com/eclipse-score/tooling
+    rev: 31ff8eee214e4e97ef8f5cb46e443273515b63ec
+    hooks:
+      - id: copyright

.vscode/rustfmt.sh

@@ -1,3 +1,15 @@
 #!/usr/bin/env bash
+# *******************************************************************************
+# Copyright (c) 2026 Contributors to the Eclipse Foundation
+#
+# See the NOTICE file(s) distributed with this work for additional
+# information regarding copyright ownership.
+#
+# This program and the accompanying materials are made available under the
+# terms of the Apache License Version 2.0 which is available at
+# https://www.apache.org/licenses/LICENSE-2.0
+#
+# SPDX-License-Identifier: Apache-2.0
+# *******************************************************************************
 
 bazel run @score_tooling//format_checker:rustfmt_with_policies

BUILD

@@ -12,7 +12,7 @@
 # *******************************************************************************
 
 load("@score_docs_as_code//:docs.bzl", "docs")
-load("@score_tooling//:defs.bzl", "copyright_checker", "setup_starpls", "use_format_targets")
+load("@score_tooling//:defs.bzl", "setup_starpls", "use_format_targets")
 
 # Docs-as-code
 docs(
@@ -41,27 +41,6 @@ setup_starpls(
     visibility = ["//visibility:public"],
 )
 
-# Copyright check
-copyright_checker(
-    name = "copyright",
-    srcs = [
-        ".github",
-        "bazel_common",
-        "docs",
-        "feature_integration_tests",
-        "images",
-        "runners",
-        "rust_coverage",
-        "scripts",
-        "showcases",
-        "//:BUILD",
-        "//:MODULE.bazel",
-    ],
-    config = "@score_tooling//cr_checker/resources:config",
-    template = "@score_tooling//cr_checker/resources:templates",
-    visibility = ["//visibility:public"],
-)
-
 # Add target for formatting checks
 use_format_targets()
 

bazel_common/score_images.MODULE.bazel

@@ -1,3 +1,15 @@
+# *******************************************************************************
+# Copyright (c) 2026 Contributors to the Eclipse Foundation
+#
+# See the NOTICE file(s) distributed with this work for additional
+# information regarding copyright ownership.
+#
+# This program and the accompanying materials are made available under the
+# terms of the Apache License Version 2.0 which is available at
+# https://www.apache.org/licenses/LICENSE-2.0
+#
+# SPDX-License-Identifier: Apache-2.0
+# *******************************************************************************
 bazel_dep(name = "rules_oci", version = "2.3.1")
 git_override(
     module_name = "rules_oci",

docs/integration_process/checklist.rst

@@ -0,0 +1,48 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2026 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Checklist
+=========
+
+Use this as a final review before opening your pull request:
+
+.. list-table::
+   :header-rows: 1
+   :widths: 40 60
+
+   * - Step
+     - Done when…
+   * - 1 · Add module (register, regenerate, patches)
+     - module entry added under ``modules.target_sw`` with ``repo`` + ``hash``;
+       ``update_module_from_known_good.py`` ran and generated files committed;
+       patches referenced if needed; ``known_good_correct`` and ``bzlmod-lock``
+       checks green.
+   * - 2 · Documentation
+     - ``needs_json`` added to ``//:docs`` data and toctree entry in
+       ``sw_components.rst``; ``//:docs_combo`` shows the module.
+   * - 3 · Unit tests (default platform)
+     - module compiles and unit tests pass on ``--config=linux-x86_64`` via
+       ``quality_runners.py``; ``metadata`` tuned if needed.
+   * - 4 · Platforms (build & test)
+     - ``score_pkg_bundle`` + ``*.score.json`` added and registered in
+       ``showcases/BUILD`` (ships into every image); ``bazel test
+       @score_my_module//...`` passes.
+   * - 5 · Component tests
+     - *not available yet — to be introduced.*
+   * - 6 · Integration tests
+     - tests added under ``feature_integration_tests/itf``.
+   * - 7 · Reporting
+     - Rust coverage generated; verification/status tables updated.
+   * - 8 · Code quality
+     - formatting, Bazel Clippy (Rust) and the CodeQL/MISRA C++ scan pass.

docs/integration_process/integration_process.rst

@@ -12,5 +12,77 @@
    # SPDX-License-Identifier: Apache-2.0
    # *******************************************************************************
 
+###################
 Integration Process
 ###################
+
+This document is a step-by-step *how-to* for module owners who want to integrate
+their own S-CORE module into the **Reference Integration** — whether for the
+first time, when bringing it back after an exclusion, or to make it part of the
+S-CORE releases in general.
+
+It walks you through everything from registering the module in
+``known_good.json`` over wiring it into the Bazel build, the showcases, the
+images and the CLI, up to adding it to the CI/CD pipelines and the consolidated
+reporting (documentation, coverage and verification reports).
+
+
+What "integration" means here
+=============================
+
+The Reference Integration is a single `Bazel (bzlmod) <https://bazel.build/external/overview#bzlmod>`_
+build that pulls every S-CORE module together at a defined commit, builds them
+against each other and runs their tests, showcases and reports.
+
+Integrating a module is **incremental**: each step below builds on the previous
+one and *extends the reach* of your module a little further into the
+integration. You climb the ladder only as far as your module needs — a pure
+library may stop after it builds in-tree, while a module with a runnable example
+goes all the way to running on every target platform and being exercised by
+integration tests.
+
+The chapters that follow walk this ladder in order. Stop at whatever rung makes
+sense for your module.
+
+
+Prerequisites
+=============
+
+Before you start, make sure that:
+
+* Your module lives in its own GitHub repository under the ``eclipse-score``
+  organization and is a **bzlmod module**, i.e. it has a top-level
+  ``MODULE.bazel`` with a ``module(name = "score_<your_module>")`` declaration.
+* The module name follows the ``score_<name>`` convention (e.g.
+  ``score_communication``). The same name is used as the Bazel
+  ``bazel_dep`` / repository name (``@score_<name>//...``).
+* Your module is registered in the
+  `S-CORE Bazel registry <https://github.com/eclipse-score/bazel_registry>`_ so
+  that it can be resolved as a ``bazel_dep`` during the integration.
+* The module builds and tests pass standalone on all four currently supported
+  target platforms: Linux ``x86_64``, QNX 8 ``x86_64``, Red Hat AutoSD
+  ``x86_64`` and EB corbos Linux (Safety Apps) ``aarch64``.
+* You know the commit hash you want to pin (the integration always pins an exact
+  commit, never a floating branch).
+
+
+The integration steps
+======================
+
+Work through the chapters in order — each one extends the reach of your module a
+little further into the integration:
+
+.. toctree::
+   :maxdepth: 2
+   :numbered:
+
+   step_1_add_module
+   step_2_documentation
+   step_3_unit_tests
+   step_4_platforms
+   step_5_component_tests
+   step_6_integration_tests
+   step_7_reporting
+   step_8_code_quality
+   checklist
+   reference