EBL 3.0: SD-2934: Update What's New for END v3.0.3

[HenrikHL]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Add What's New documentation for END v3.0.3 release

📝 Documentation

Walkthroughs

Description

• Add release notes for END v3.0.3 maintenance release
• Update platform list with three new onboarded platforms
• Improve descriptions for endorsementChain and errorCode fields
• Fix relative path references in documentation links

Diagram

flowchart LR
  A["README.md"] -->|Add v3.0.3 release notes| B["Release v3.0.3"]
  B -->|Update platform list| C["DOCU, AEOT, SGTD"]
  B -->|Improve field descriptions| D["endorsementChain, errorCode"]
  A -->|Fix relative paths| E["GitHub links"]

Loading

File Changes

1. ebl/v3/endorsement/README.md 📝 Documentation +13/-3

Add v3.0.3 release notes and platform updates

• Added new release section for v3.0.3 with maintenance release notes
• Updated eblPlatform and codeListProvider lists with three newly onboarded platforms (DOCU,
 AEOT, SGTD)
• Improved descriptions for endorsementChain, eblPlatform, codeListProvider, and errorCode
 fields
• Fixed relative path references in Bill of Lading and Surrender API links
• Minor grammar improvement in v3.0.2 release notes

ebl/v3/endorsement/README.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (1) 📐 Spec deviations (0)

1. v3.0.3 marked as TBD 📎 Requirement gap ✓ Correctness

Description

The new README entry for release v3.0.3 is labeled as TBD 2026, which does not clearly indicate
that EBL 3.0.3 has been published and available through the intended release channel(s). This
conflicts with the requirement that the published patch be explicitly identified as 3.0.3
(including clear release identification).

Code

ebl/v3/endorsement/README.md[R11-13]

+<a name="v303"></a>[Release v3.0.3 (TBD 2026)](https://app.swaggerhub.com/apis-docs/dcsaorg/DCSA_EBL_END/3.0.3)
+---
+This is a "maintenance" release to align with eBL v3.0.3. This version updates the platform list and improves descriptions.

Evidence

PR Compliance ID 1 requires the 3.0.3 patch to be published and clearly identified as such. The
added release section explicitly includes Release v3.0.3 (TBD 2026), which implies the release is
not finalized/published or not clearly identified with a definitive publication date.

Publish patch release EBL 3.0.3
ebl/v3/endorsement/README.md[11-13]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The README adds a `Release v3.0.3` section but labels it `TBD 2026`, which does not clearly indicate that version `3.0.3` has been published per the release compliance requirement.

## Issue Context
Compliance requires the patch release `EBL 3.0.3` to be published and clearly identified as `3.0.3` in the expected release/distribution channel(s). The documentation should reflect a definitive release identification (e.g., an actual release date and/or confirmation wording) rather than `TBD`.

## Fix Focus Areas
- ebl/v3/endorsement/README.md[11-13]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Mixed relative link style 🐞 Bug ⚙ Maintainability

Description

The publications list now mixes relative link formats (./.. and ./../surrender without a
trailing slash), diverging from the consistent ./../ + trailing-slash directory links used in
other eBL v3 module READMEs. This inconsistency creates avoidable churn and makes navigation
patterns harder to follow across modules.

Code

ebl/v3/endorsement/README.md[R8-9]

+- [Bill of Lading](./..) maintained here on GitHub
+- [Bill of Lading Surrender](./../surrender) maintained here on GitHub (the Surrender API)

Evidence

END README uses ./.. and a no-trailing-slash directory link, while other eBL v3 module READMEs use
./../ and trailing / for directory links in the same section.

ebl/v3/endorsement/README.md[8-9]
ebl/v3/surrender/README.md[8-9]
ebl/v3/issuance/README.md[8-9]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The END module README uses a mixed relative-link style in the publications list (`./..` and `./../surrender`), which is inconsistent with other eBL v3 module READMEs.

## Issue Context
Other eBL v3 module READMEs consistently use `./../` to reference the parent and include a trailing slash when linking to directories.

## Fix Focus Areas
- ebl/v3/endorsement/README.md[8-9]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more