docs: add missing pages to root toctree

Sphinx (warnings-as-errors) failed because
docs/s_core_v_1/index.rst and docs/verification_report/platform_verification_report.rst
were referenced via grid-cards but not listed in any toctree.

Author: antonkri

.github/skills/overall-status/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: overall-status
-description: "Update the Feature and Process Status table in docs/s_core_v_1/roadmap/overall_status.rst. Use when: checking module status, updating feature status tracker, refreshing work product status, deriving completion status from eclipse-score GitHub repos for Baselibs, Communication, Logging, Orchestrator, Persistency, Time, Config Management, Lifecycle, Security/Crypto."
+description: "Update the Feature and Process Status table in docs/s_core_v_1/roadmap/overall_status.rst. Use when: checking module status, updating feature status tracker, refreshing work product status, deriving completion status from eclipse-score GitHub repos for Baselibs, Communication, Logging, Persistency, Time, Config Management, Lifecycle, Security/Crypto."
 argument-hint: "optional: module name or 'all'"
 ---
 
@@ -151,6 +151,8 @@ The pie chart diagrams are computed live by sphinx-needs at build time — they
 
 ## Modules and Repos
 
+> **EXCLUDED MODULES**: **Orchestrator** is intentionally not tracked in `overall_status.rst` and must NOT be added to any of the PA tables, even though `score_orchestrator` is pinned in `known_good.json` and the module exists in `eclipse-score/score` / `eclipse-score/orchestrator`. Do not query or generate rows for it.
+
 > **IMPORTANT**: Each module has its own dedicated repo in the `eclipse-score` GitHub org AND content in `eclipse-score/score`. **Always check BOTH** the module's own repo and `eclipse-score/score` when counting needs elements. Never rely on `eclipse-score/score` alone.
 
 > **VERSION PINNING**: Always use the commit hash pinned in `known_good.json` (column `known_good.json key`) — **never use `main`** for source repos. This ensures data matches exactly the versions that `reference_integration` is currently testing against. For modules not listed in `known_good.json` (marked `—`), fall back to `main`.
@@ -160,7 +162,6 @@ The pie chart diagrams are computed live by sphinx-needs at build time — they
 | Baselibs | `score_baselibs` | `eclipse-score/baselibs` (no sphinx-needs RST so far) | `docs/modules/baselibs/**`, `docs/features/baselibs/docs` |
 | Communication | `score_communication` | `eclipse-score/communication` (no sphinx-needs RST so far) | `docs/modules/communication/**`, `docs/features/communication/docs` |
 | Logging | `score_logging` | `eclipse-score/logging` (no sphinx-needs RST so far) | `docs/modules/logging/**`, `docs/features/analysis-infra/logging/docs` |
-| Orchestrator | `score_orchestrator` | `eclipse-score/orchestrator` | `docs/modules/orchestrator/**`, `docs/features/orchestration` |
 | Persistency | `score_persistency` | `eclipse-score/persistency` — has `docs/persistency/kvs/` with comp_req/comp_arc ✅ | `docs/features/persistency` |
 | Time | `—` (not in known_good) | `eclipse-score/inc_time` (no sphinx-needs RST so far) | `docs/features/time/docs` |
 | Config Management | `—` (not in known_good) | `eclipse-score/config_management` (no sphinx-needs RST so far) | `docs/features/configuration` |
@@ -197,7 +198,7 @@ for repo in ["eclipse-score/score", "eclipse-score/<module_own_repo>"]:
 - **✅ Available**: A closed GitHub Issue with "Feature Request" or "Contribution Request" for the module exists in `eclipse-score/score`
 - **❌ Open**: No such issue found
 
-Known closed CRs: Baselibs (#549), Communication (#69), Logging (#68), Orchestrator (#273), Persistency (#95), Time (#910), Config Management (#754, #1764), Lifecycle (#909), Security/Crypto (#905)
+Known closed CRs: Baselibs (#549), Communication (#69), Logging (#68), Persistency (#95), Time (#910), Config Management (#754, #1764), Lifecycle (#909), Security/Crypto (#905)
 
 ### Process Area 2 — Feature Requirements
 - **✅ Available**: 100% of individual needs elements (e.g. `.. feat_req::`) inside the requirements doc have `:status: valid`
@@ -260,7 +261,7 @@ See :ref:`verification_workflows`.
    CI (``Code Quality & Documentation`` workflow, ``bazel coverage --config=ferrocene-coverage``).
    C0 = line coverage, C1 = branch coverage. Rust coverage reports line coverage only.
    Modules not yet integrated into the reference_integration CI (Time, Config Mgmt) or with
-   disabled coverage extraction (Orchestrator) show ❌ Open.
+   Modules not yet integrated into the reference_integration CI (Time, Config Mgmt) show ❌ Open.
 
 .. note::
 
@@ -379,7 +380,6 @@ gh api "repos/eclipse-score/reference_integration/actions/jobs/$JOB_ID/logs" \
 | Baselibs | `score_baselibs_cpp` | `score_baselibs_rust_rust` |
 | Communication | `score_communication_cpp` | — (disabled) |
 | Logging | `score_logging_cpp` | `score_logging_rust` |
-| Orchestrator | — (disabled) | — (disabled) |
 | Persistency | `score_persistency_cpp` | `score_persistency_rust` |
 | Time | not in CI | — |
 | Config Mgmt | not in CI | — |
@@ -459,7 +459,6 @@ Static analysis CI exists at two levels:
 | Baselibs | `✅ 0 findings` | [clang-tidy lint.yml](https://github.com/eclipse-score/baselibs/blob/main/.github/workflows/lint.yml) |
 | Communication | `🔄 Configured` | [static_analysis.bazelrc](https://github.com/eclipse-score/communication/blob/main/quality/static_analysis/static_analysis.bazelrc) + [CodeQL/MISRA](https://github.com/eclipse-score/communication/tree/main/quality/static_analysis) — no CI enforcement yet |
 | Logging | `❌ Open` | — |
-| Orchestrator | `✅ 0 findings` | [Clippy clippy.yml](https://github.com/eclipse-score/orchestrator/blob/main/.github/workflows/clippy.yml) |
 | Persistency | `✅ 0 findings` | [Clippy clippy.yml](https://github.com/eclipse-score/persistency/blob/main/.github/workflows/clippy.yml) |
 | Time | `❌ Open` | — |
 | Config Mgmt | `✅ 0 findings` | [clang-tidy static-analysis.yml](https://github.com/eclipse-score/config_management/blob/main/.github/workflows/static-analysis.yml) |
@@ -495,7 +494,6 @@ Dynamic analysis is performed via sanitizer CI workflows (ASan/UBSan/LSan for C+
 | Baselibs | `✅ 0 findings` | [sanitizers_linux.yml](https://github.com/eclipse-score/baselibs/blob/main/.github/workflows/sanitizers_linux.yml) — ASan+UBSan+LSan |
 | Communication | `✅ 0 findings` | [ASan/UBSan/LSan](https://github.com/eclipse-score/communication/blob/main/.github/workflows/address_undefined_behavior_leak_sanitizer.yml), [TSan](https://github.com/eclipse-score/communication/blob/main/.github/workflows/thread_sanitizer.yml) |
 | Logging | `❌ Open` | — |
-| Orchestrator | `❌ Open` | — |
 | Persistency | `❌ Open` | — |
 | Time | `❌ Open` | — |
 | Config Mgmt | `❌ Open` | — |
@@ -560,7 +558,6 @@ REFS = {
     "baselibs":            pinned_ref("score_baselibs"),
     "communication":       pinned_ref("score_communication"),
     "logging":             pinned_ref("score_logging"),
-    "orchestrator":        pinned_ref("score_orchestrator"),
     "persistency":         pinned_ref("score_persistency"),
     "lifecycle":           pinned_ref("score_lifecycle_health"),
     "inc_time":            "main",   # not in known_good
@@ -597,7 +594,6 @@ tree_score    = get_tree("eclipse-score/score",         REFS["score"])
 tree_baselibs = get_tree("eclipse-score/baselibs",      REFS["baselibs"])
 tree_comm     = get_tree("eclipse-score/communication", REFS["communication"])
 tree_log      = get_tree("eclipse-score/logging",       REFS["logging"])
-tree_orch     = get_tree("eclipse-score/orchestrator",  REFS["orchestrator"])
 tree_pers     = get_tree("eclipse-score/persistency",   REFS["persistency"])
 tree_life     = get_tree("eclipse-score/lifecycle",     REFS["lifecycle"])
 tree_time     = get_tree("eclipse-score/inc_time",      REFS["inc_time"])
@@ -694,9 +690,6 @@ Use these exact filters when calling `count_files()`. Verify printed file counts
 | Baselibs | Comp. Arch | score | `lambda p: 'modules/baselibs' in p and 'architecture' in p and p.endswith('.rst') and 'chklst' not in p` |
 | Baselibs | Arch. Inspection | score | `lambda p: 'baselibs' in p and 'chklst_arc_inspection' in p` |
 | Baselibs | Impl. Inspection | score | `lambda p: 'baselibs' in p and 'chklst_impl_inspection' in p` |
-| Orchestrator | Feat. Req | score | `lambda p: 'features/orchestration' in p and 'requirements' in p and p.endswith('.rst')` |
-| Orchestrator | Comp. Req | score | `lambda p: 'modules/orchestrator' in p and 'requirements' in p and p.endswith('.rst') and 'chklst' not in p` |
-| Orchestrator | Comp. Arch | score | `lambda p: 'modules/orchestrator' in p and 'architecture' in p and p.endswith('.rst') and 'chklst' not in p` |
 | Persistency | Feat. Req | score | `lambda p: 'features/persistency' in p and 'requirements' in p and p.endswith('.rst') and 'chklst' not in p` |
 | Persistency | Feat. Arch | score | `lambda p: 'features/persistency' in p and 'architecture' in p and p.endswith('.rst') and 'chklst' not in p` |
 | Persistency | Comp. Req | pers | `lambda p: 'kvs' in p and 'requirements' in p and p.endswith('.rst') and 'chklst' not in p` |

docs/_assets/custom.css

@@ -155,3 +155,14 @@ body.wide-content-page .bd-content .bd-article-container {
     padding: 0.4rem 0.6rem;
     font-size: 0.78rem;
 }
+
+/* ---------------------------------------------------------------------------
+ * Landing-page grid cards (docs/index.rst): white text, original background.
+ * ---------------------------------------------------------------------------*/
+
+.landing-grid .sd-card *,
+.landing-grid .sd-card a,
+.landing-grid .sd-card a:visited,
+.landing-grid .sd-card a:hover {
+    color: #ffffff !important;
+}

docs/_assets/pi_timeline_2026.drawio.svg

@@ -34,9 +34,10 @@ documentation set that downstream product distributions can build on.
 
 .. grid:: 1 1 3 3
    :gutter: 3
+   :class-container: landing-grid
 
    .. grid-item-card:: 📊 Status & Roadmap
-      :link: s_core_v_1/index
+      :link: s_core_v_1/roadmap/roadmap
       :link-type: doc
 
       :doc:`S-Core v1.0 Roadmap <s_core_v_1/roadmap/roadmap>` and PI planning.
@@ -73,7 +74,10 @@ documentation set that downstream product distributions can build on.
 .. toctree::
    :hidden:
 
-   sw_components
-   integration_process/integration_process
-   process_methods_tools
-   s_core_v_1/releases/releases
+   Modules <sw_components>
+   Integration Process <integration_process/integration_process>
+   Integration Status <https://eclipse-score.github.io/reference_integration/main/status_dashboard.html>
+   Process & Tools <process_methods_tools>
+   S-Core v1.0 <s_core_v_1/index>
+   Releases <s_core_v_1/releases/releases>
+   Verification Report <verification_report/platform_verification_report>

docs/index.rst

@@ -109,7 +109,7 @@ See :ref:`chm_change_workflows`.
           :colors: LimeGreen, Gold, LightBlue, LightGray
           :filter-func: needs_filters.area_verification_status(change_management)
 
-.. rubric:: Implementation status: 🔄 92% (11/12 deliverables complete)
+.. rubric:: Implementation status: 🔄 91% (10/11 deliverables complete)
 
 .. list-table::
    :header-rows: 1
@@ -128,9 +128,6 @@ See :ref:`chm_change_workflows`.
    * - Logging
      - ✅ Available
 
-   * - Orchestrator
-     - ✅ Available
-
    * - Persistency
      - ✅ Available
 
@@ -202,7 +199,7 @@ See :ref:`requirements_workflows`.
           :colors: LimeGreen, Gold, LightBlue, LightGray
           :filter-func: needs_filters.area_verification_status(requirements_engineering)
 
-.. rubric:: Implementation status: 🔄 25% (9/36 deliverables complete)
+.. rubric:: Implementation status: 🔄 27% (9/33 deliverables complete)
 
 .. list-table::
    :header-rows: 1
@@ -240,14 +237,6 @@ See :ref:`requirements_workflows`.
      - ❌ Open
      - ❌ Open
 
-   * - Orchestrator
-     - 🔄 83% (26/31)
-     - 🔄 0% (0/2)
-     - 🔄 0% (0/2)
-
-       | `executor <https://github.com/eclipse-score/score/blob/main/docs/modules/orchestrator/executor/docs/requirements/chklst_req_inspection.rst>`__
-       | `orchestrator <https://github.com/eclipse-score/score/blob/main/docs/modules/orchestrator/orchestrator/docs/requirements/chklst_req_inspection.rst>`__
-
    * - Persistency
      - ✅ Available (41/41)
      - 🔄 94% (36/38)
@@ -351,7 +340,7 @@ See :ref:`arch_workflow`.
           :colors: LimeGreen, Gold, LightBlue, LightGray
           :filter-func: needs_filters.area_verification_status(architecture_design)
 
-.. rubric:: Implementation status: 🔄 17% (6/36 deliverables complete)
+.. rubric:: Implementation status: 🔄 15% (5/33 deliverables complete)
 
 .. list-table::
    :header-rows: 1
@@ -389,14 +378,6 @@ See :ref:`arch_workflow`.
      - ✅ Available (3/3)
      - ❌ Open
 
-   * - Orchestrator
-     - 🔄 66% (4/6)
-     - ✅ Available (27/27)
-     - 🔄 0% (0/2)
-
-       | `executor <https://github.com/eclipse-score/score/blob/main/docs/modules/orchestrator/executor/docs/architecture/chklst_arc_inspection.rst>`__
-       | `orchestrator <https://github.com/eclipse-score/score/blob/main/docs/modules/orchestrator/orchestrator/docs/architecture/chklst_arc_inspection.rst>`__
-
    * - Persistency
      - ✅ Available (12/12)
      - 🔄 25% (1/4)
@@ -487,7 +468,7 @@ See :ref:`workflow_implementation`.
           :colors: LimeGreen, Gold, LightBlue, LightGray
           :filter-func: needs_filters.area_verification_status(implementation)
 
-.. rubric:: Implementation status: 🔄 38% (18/48 deliverables complete)
+.. rubric:: Implementation status: 🔄 36% (16/44 deliverables complete)
 
 .. list-table::
    :header-rows: 1
@@ -528,12 +509,6 @@ See :ref:`workflow_implementation`.
      - ❌ Open
      - ❌ Open
 
-   * - Orchestrator
-     - ✅ Available
-     - ✅ Available (~38,300 LOC) `orchestrator <https://github.com/eclipse-score/orchestrator>`__
-     - ❌ Open
-     - ❌ Open
-
    * - Persistency
      - ✅ Available
      - ✅ Available (~8,700 LOC) `persistency <https://github.com/eclipse-score/persistency>`__
@@ -636,8 +611,8 @@ See :ref:`verification_workflows`.
    **C0/C1 Coverage** data is sourced from the `reference_integration <https://github.com/eclipse-score/reference_integration>`__
    CI (``Code Quality & Documentation`` workflow, ``bazel coverage --config=ferrocene-coverage``).
    C0 = line coverage, C1 = branch coverage. Rust coverage reports line coverage only.
-   Modules not yet integrated into the reference_integration CI (Time, Config Mgmt) or with
-   disabled coverage extraction (Orchestrator) show ❌ Open.
+   Modules not yet integrated into the reference_integration CI (Time, Config Mgmt)
+   show ❌ Open.
 
 .. note::
 
@@ -652,7 +627,7 @@ See :ref:`verification_workflows`.
    ``--config=asan_ubsan_lsan``, TSan via ``--config=tsan``). All listed workflows are
    zero-tolerance, so a passing ``main`` branch implies **0 sanitizer findings**.
 
-.. rubric:: Implementation status: 🔄 29% (25/87 deliverables complete)
+.. rubric:: Implementation status: 🔄 27% (21/79 deliverables complete)
 
 .. list-table::
    :header-rows: 1
@@ -728,22 +703,6 @@ See :ref:`verification_workflows`.
      - ❌ Open
      - ❌ Open
 
-   * - Orchestrator
-     - ✅ Available
-
-       | (2 tests)
-     - ❌ Open
-     - ✅ Available (9 tests)
-     - ✅ Available (3 tests)
-
-       | `reference_integration <https://github.com/eclipse-score/reference_integration>`__ (cross-module)
-     - ✅ 0 findings
-
-       | `Clippy <https://github.com/eclipse-score/orchestrator/blob/main/.github/workflows/clippy.yml>`__
-     - ❌ Open
-     - ❌ Open
-     - ❌ Open
-
    * - Persistency
      - ✅ Available
 

docs/s_core_v_1/roadmap/overall_status.rst

@@ -12,8 +12,10 @@
    # SPDX-License-Identifier: Apache-2.0
    # *******************************************************************************
 
-🚀 PI 1 — 13 May – 13 July 2026 · `v0.8 <https://github.com/eclipse-score/score/milestone/30>`__
-==================================================================================================
+🚀 Release Gate v0.8 — 13 May – 13 July 2026
+=================================================
+
+Milestone: `score/v0.8 <https://github.com/eclipse-score/score/milestone/30>`__
 
 Focus: Requirements Engineering (PA2) + Architecture Design (PA3)
 ------------------------------------------------------------------
@@ -46,7 +48,7 @@ See the relevant tables in :doc:`overall_status`:
 Feasibility Check
 -----------------
 
-Do we have everything in place to deliver the PI 1 focus items?
+Do we have everything in place to deliver the Release Gate v0.8 focus items?
 
 **Tooling & Process**
 
@@ -70,11 +72,11 @@ Do we have everything in place to deliver the PI 1 focus items?
 - [ ] Every module's ``chklst_req_inspection.rst`` and ``chklst_arc_inspection.rst`` are reviewed and merged into the module repo
 - [ ] The overall status tracker (``overall_status.rst``) reflects the current state for each module
 - [ ] All tracked findings from inspections have a linked GitHub issue with component + milestone set
-- [ ] A final PI 1 review meeting confirms sign-off by module owners and process responsible
+- [ ] A final Release Gate v0.8 review meeting confirms sign-off by module owners and process responsible
 
 **Integration in Reference Integration**
 
 - [ ] All modules with completed requirements and architecture are integrated in this reference integration repository
 - [ ] The reference integration build passes (no broken imports, no unresolved need IDs)
-- [ ] The documentation (this site) builds without warnings for all PI 1 modules
-- [ ] The PI 1 status table in ``overall_status.rst`` is updated to reflect the final state
+- [ ] The documentation (this site) builds without warnings for all Release Gate v0.8 modules
+- [ ] The Release Gate v0.8 status table in ``overall_status.rst`` is updated to reflect the final state