`inspect-service` envelope does not carry `maturity` where the ListingSummary's `inspection.maturity` points, so a client following the href loses the field

[norgejbb-byte]

Repo: DACS-Agent-commerce/Community · Type: nit (shape/consistency) · Source: DACS seller phase-2, STEP-3 public proof (hop 3)

Expected

The ListingSummary.inspection block advertises { artifactType:"directory-service-profile", maturity:"listed", href:"/api/dacs/inspect-service/…" }. A client that follows href should find the same maturity (the service-profile's own field) at a predictable place in the response.

Observed (bytes)

Row (/api/dacs/listings) → inspection:

{ "artifactType":"directory-service-profile","maturity":"listed",
  "href":"/api/dacs/inspect-service/attested-datum-read/1?seller=did%3Ademos%3Aagent%3A36c3…" }

Following the href, GET /api/dacs/inspect-service/attested-datum-read/1?seller=… → top-level keys ["artifactType","source","artifact","expectations"]. There is no top-level maturity and no inspection.maturity; the field the row promised is absent from the resolved envelope (our reader logged maturity=undefined). maturity appears only on the row's inspection block, not on the inspect-service artifact it links to.

Repro

curl -s ".../api/dacs/listings?q=attested-datum-read" | jq '.listings[0].inspection.maturity'          # → "listed"
curl -s ".../api/dacs/inspect-service/attested-datum-read/1?seller=did%3Ademos%3Aagent%3A36c3b6fca189c15951763028362694ec2a62bfb59850910c89b4341d2a66a19f" | jq 'keys, .maturity'   # → [...], null

Suggested direction (one line): echo maturity on the inspect-service envelope (top-level or under artifact) so the row's inspection.maturity and the linked profile agree.

Cross-links: none; cosmetic consistency between the summary and its inspection href.