# Affiliate card metadata — rollout verification

## Delivery status

**The API and console changes deployed successfully to preview and production** at behavior revision `a91bd6b92d36941b66d356bcd1ecf884391a458e`.

- [Preview deployment](https://github.com/cosbor11/wikiup/actions/runs/43565949354): successful.
- [Production deployment](https://github.com/cosbor11/wikiup/actions/runs/43565949320): successful.
- Preview API and console smoke checks completed November 13, 2026, **10:33:45 PM PST**.
- Production API and console smoke checks completed November 13, 2026, **10:37:27 PM PST**.
- All evidence times use Hummingbird’s **America/Los_Angeles**, PST, offset **−08:00**.

This report is a documentation-only follow-up to that verified behavior revision. A later `/api/version` revision containing this report does not change the contract. No database migration was required for the renamed fields or simplified location response. The public booking-site app was unchanged and its deployment was skipped.

## Verified contract

| Field | Contract |
| --- | --- |
| `description` | Catalog excerpt, plain text, at most 240 characters; direct content preserves its existing full description. Replaces catalog `shortDescription`. |
| `tagLine` | Plain text, at most 100 characters, or null. Replaces `accommodationSummary` in affiliate responses. Existing stored owner text is preserved. |
| `mapLocation` | Exact `{latitude, longitude}` pair or null. No status or precision fields. |
| `stayType`, `starRating`, `priceTier` | Existing semantics and nullable unknown values are preserved. |

API reference fields/examples, the [JSON schema](./travel-listings.schema.json), [partner guide](./hidden-san-diego-integration.md), [card metadata guide](./listing-card-metadata.md), and [location guide](./listing-locations.md) agree on these names. The previous missing-field report at November 13, 9:03:11 PM PST preceded the original metadata deployment; the current checks below verify the renamed contract directly.

## Authenticated live preview checks

Used a temporary affiliate API key for the existing preview affiliate account. The key was revoked and revocation checked after testing. No property, guest, reservation, payment, booking, or OTA data was changed.

| Request | Property-local check time, Nov 13, 2026 | Result | Correlation ID |
| --- | --- | --- | --- |
| `GET /api/travel/listings?destination=julian&page=1&pageSize=12&includeImages=false` | 10:28:15 PM PST | HTTP 200; all five metadata fields; images deferred | `a5a3f4709bda2ae3-LAX` |
| `GET /api/travel/listings?destination=julian&page=1&pageSize=12&includeImages=true` | 10:28:19 PM PST | HTTP 200; same metadata; image ready | `a5a3f4893ec92ae3-LAX` |
| Direct content for the returned hotel | 10:28:17 and 10:28:20 PM PST | HTTP 200; new names; same coordinates and tagline | Not recorded |

All requests enforced `Cache-Control: private, no-store, max-age=0`. Both catalog responses preserved the listing/property IDs and property timezone, returned `failures: []`, `partial: false`, `pageComplete: true`, `complete: true`, and `nextPage: null`. Neither catalog nor direct content returned the old metadata names. The public location object contained only latitude and longitude.

### Sanitized live excerpt

These are the actual public fields from the authenticated preview catalog, not invented sample facts. Both image modes returned the same values:

```json
{
  "id": "hotel:c31ef118-5c7f-11f1-0000-910230779ee6",
  "type": "hotel",
  "stayType": null,
  "description": "quiet mountain escape just minutes from downtown Julian. Stay among oaks, pines, fresh air, hot-tub soaks, and friendly llamas at Wikiup Hummingbird Hotel — a small, peaceful inn made for weekend getaways, romantic retreats, and slow days…",
  "starRating": null,
  "priceTier": null,
  "tagLine": null,
  "mapLocation": {
    "latitude": 33.088338,
    "longitude": -116.590737
  },
  "timeZone": "America/Los_Angeles"
}
```

The four null facts are not configured on this preview property. They are present in the contract and may be entered by the owner; verification did not invent or populate them. Coordinates match the saved owner-approved point. This is not an independent physical survey.

## Deployment smoke checks

Both environments passed:

- API `/api/version` and console `/internal/diagnostics` matched the behavior revision; console API origins matched their environments.
- API and console health returned HTTP 200.
- Published schema required all five nullable metadata fields, used `description` / `tagLine`, set `tagLine.maxLength` to 100, and omitted the old names.
- Unauthenticated affiliate catalog access returned JSON HTTP 401 with no-store headers.
- Real overview widgets returned nonempty HTML; referenced JavaScript and CSS loaded successfully.
- Deployed property-page assets included the Tagline editor and fixed 16:9 cover crop.

## Automated and rendered checks

- GitHub Actions test gates passed: **384 API suites / 2,987 tests** and **77 console suites / 461 tests**, plus deployment guard checks.
- API and console TypeScript passed; targeted console lint passed.
- Ten local Chromium component checks passed: five map confirmation/failure cases and five property-editor cases, covering mobile, light/dark, dropdown affordances, Tagline’s 100-character limit, and existing save behavior. Screenshots were inspected.
- Partner documentation was rendered and inspected at 390px and 1440px; links were visible and there was no horizontal overflow.
- Unit tests cover hotel/inn/rental metadata, both image modes, nulls/bounds, full detail descriptions, exact-location projection, old approximate-confirmation rejection, permissions, blacklist, pagination and partial failures. Database/provider operations in those tests were mocked. Browser component callbacks were mocked; no customer property was edited.

## Verification limits

- Authenticated live data checks cover the existing preview Hummingbird hotel, not independent live inn and rental fixtures.
- **Authenticated production catalog was not exercised:** the configured production identity has no active affiliate account. No production affiliate account or key was created to bypass that precondition. Production deployment, public schema, health, authorization denial, widget routes, and console assets were verified.
- No availability, checkout, payment, booking-attribution, or live geocoding mutation was performed for this metadata release. Hidden San Diego’s frontend and credentials were not changed or certified by these checks.
- Earlier retained PMS integration cleanup remains unresolved. No fixture-mutating PMS/channel suite was started or its blocker bypassed; certification data remains intact.

Detailed response journals and temporary-key cleanup evidence are retained privately under `work/travel-private/`; secrets and private account identifiers are excluded from this public report.
