Doc: update Traceability KIT documentation for release 26.09

[JK181196]

Description

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files

[Copilot]

🟡 Changes recommended

There are multiple confirmed documentation consistency/formatting issues (aspect naming, lifecycle operation alignment, and changelog list formatting) that should be fixed before merge.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Hi, I’m the KIT Master Builder — your Eclipse Tractus-X KIT architect and reviewer.

This PR updates the Traceability KIT (versioned docs under version-26.06) to align the Block Notification documentation with the standalone standard by switching from a status-model description to a lifecycle-based concept, and refreshes Special Characteristics references and the Traceability KIT changelog for release 26.09.

Changes:

• Reworked Block Notification documentation across Adoption/Architecture/Development views toward a lifecycle-based interaction model.
• Updated Special Characteristics / SpecialCharacteristicMeasurement references (incl. version bump to 3.0.0 and manufacturer BPN field naming in examples).
• Added a new 9.0.0 changelog entry for release 26.09.

File summaries

File	Description
docs-kits_versioned_docs/version-26.06/kits/traceability-kit/software-development-view/parts/aspect-models.mdx	Updates Special Characteristics aspect model references (v3.0.0) and example field naming; some naming/link consistency needs adjustment.
docs-kits_versioned_docs/version-26.06/kits/traceability-kit/software-development-view/app-provider.mdx	Replaces the previous status-model explanation with lifecycle-based Block Notification text; needs consistency with Architecture View (Feedback op + heading).
docs-kits_versioned_docs/version-26.06/kits/traceability-kit/changelog.mdx	Adds a 9.0.0 entry for release 26.09; list formatting and one identifier name need correction.
docs-kits_versioned_docs/version-26.06/kits/traceability-kit/architecture-view.mdx	Updates Block Notification interaction description and adds the Special Characteristics aspect model to the overview; one aspect name is inconsistent with other views.
docs-kits_versioned_docs/version-26.06/kits/traceability-kit/adoption-view.mdx	Refines Block Notification description in the Adoption View to match the updated concept.

Review details

• Files reviewed: 5/5 changed files
• Comments generated: 5
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[stephanbcbauer]

👋 Hi! I'm the KIT Master Builder — your Eclipse Tractus-X KIT architect and reviewer. I've reviewed the current branch changes around the new eSDScom KIT and here is my feedback.

✅ What I like

• The KIT structure is solid and consistent with the repo pattern: adoption-view, development-view, changelog.md, and a dedicated resources/ folder.
• The legal headers and ## NOTICE footer are in place, which matches the spirit of TRG 7.07 and the repo’s KIT documentation expectations.
• The Kit3DLogo import/render pattern is correctly used.

⚠️ Changes I would fix before merging

• Broken route in the master data:

  • In data/kitsData.js, the KIT is registered with:
    • /docs-kits/next/kits/esdscom-kit/adoption-view
  • In this repo, there is no docs-kits/next folder at all; the actual docs structure is docs-kits/kits/....
  • This means the gallery entry and navigation likely point to a 404 page. This is the most concrete issue I found.
  • Per the KIT conventions and the folder structure in the project, this should point to the live docs path, not a non-existent version folder.

• Sidebar alphabetical ordering:

  • In sidebarsDocsKits.js, the eSDScom KIT block is placed after Environmental and Social Standards KIT.
  • The repo expects KIT categories to be ordered alphabetically by label. If this is enforced, eSDScom KIT should be placed before Environmental and Social Standards KIT.

• Copyright inconsistency:

  • docs-kits/kits/esdscom-kit/changelog.md uses Copyright(c) 2025 while the other KIT pages use 2026.
  • The year should be consistent with first creation and the file’s metadata. This matters for legal clarity and TRG 7.07 compliance.

💡 Suggestions

• I’d also sanity-check the route and generated index path once more across the full KIT gallery and sidebar because a wrong route here blocks discoverability even when the content is otherwise correct.
• If the intention is a development-only “next” docs version, it should be created in the same pattern as the other versioned docs. Otherwise, keep it on the normal /docs-kits/kits/... path.

📋 Summary

• The content is promising and mostly aligned with the KIT template.
• The route issue is the real blocker. The rest are polish and compliance details I’d fix before merge.

[stephanbcbauer]

Review started by @ther3sa and @stephanbcbauer

• IMPORTANT: @JK181196 please sign the ECA... without signed ECA, we are not allowed to merge the PR @ther3sa FYI
• the title of the PR describes changes for 26.09 but the changes are done in the versioned section for 26.06 -> this means the changes are not visible for the current version and the following -> is this intended?
• Is you company listed in the NOTICE section?
• PLease have a look at the findings from CoPilot and KIT Master Builder

THX