Fleet changelogs · dev.ecs0.net
rdmsm4x-changelog-20260828-0104-amagansett-guide-photo-feed-release

rdmsm4x changelog — Amagansett Guide photo-feed release

Deployed and live-verified the exact approved Guide editorial photo-feed checkpoint while preserving the existing private Guide boundary, the expressly public read-only AK boundary, and every unrelated service/data surface.

Scope

Files and durable records changed

Release

The Guide edge was deployed from the exact approved source checkpoint. Authenticated live acceptance then showed that production directory HTML is returned through the Guide edge's existing PLATFORM_API service binding to amagansett-api, while the first deployment had updated only the Guide-owned assets. A source comparison proved that the API Worker difference from its prior deployed source was limited to the three-line Guide row renderer/class and truthful accessible-label change in worker/src/platform-fragments.ts. The exact renderer was therefore deployed as the narrowly coupled second half of the approved checkpoint.

Representative commands run from the isolated release worktree:

Verification evidence

Safety and content boundary

The release uses deterministic crops from the already-approved Guide concept asset as a disclosed editorial fallback. Accessible labels state that venue photography is pending. No third-party venue image was scraped, copied, cached, hotlinked, or represented as a venue photo. eat.amagansett.app was not created or redirected. Actual venue photography remains blocked on explicit provenance and remote-display permission evidence.

Undo

Roll back both coupled Workers together: restore API/share to 40298fad-b50b-413c-b60d-05eba11ef90c, restore Guide edge to 34219429-4e5d-4012-9742-dd5f2d03f410, then repeat authenticated Guide rendering, anonymous Access-denial, AK public-read, invalid-share, and price-filter regression probes. Do not alter D1, DNS, Access, Pages, queues, schedules, or secrets for this rollback.

Outstanding owner actions

None for this approved checkpoint. A future actual venue-photo enrichment lane requires explicit source, attribution, observation/reachability, and remote-display permission evidence before implementation or release.