[Scenario] Missing approval metadata blocks the future DPA page

[mpiton]

User story: #2507
Rule: R-06
Feature: specs/mat-19-approve-signing-ready-eu-dpa-text/r06-version-date-approval-status-record.feature
Level: @ui
Branch: @violation

  @violation
  Scenario Outline: Missing approval metadata blocks the future DPA page
    Given the future public site page in apps/site handles route "/dpa"
    And the DPA package contains the legal text "EU DPA Cloud Beta v2026.06"
    And the approval metadata omits "<field>"
    And every other DPA requirement is complete
    When a Cloud Beta pilot opens "/dpa"
    Then the page shows "Pending legal review"
    And the page reports "Missing <field>"
    And the page does not offer the DPA as signature-ready

    Examples:
      | field         |
      | version       |
      | approval date |
      | status        |

Generated at: 2026-06-12T09:38:42.067Z

[mpiton]

Scenario implemented and merged in the site ATDD integration branch via PR #50.