Sentry captures inherit the building from the request context

Follow-up to #21632 (the class fix): a logError captured inside a request context whose propertyId is set carries the propertyId Sentry tag without per-call plumbing, so sentry-server-policy can demote test-building noise. Alerts JAVASCRIPT-NEXTJS-1K9 and -13B.

Status is DERIVED from each row’s own PR, decision and prod-evidence links by bin/refresh-tracker sentry-context-scope — never typed. Last refreshed 2026-10-21 22:35Z.

Overall
—
 
—
Shipped
—
Merged
—
In flight
—
Open
—
Waiting on you
Groups — click to filter
Status
—

Every row opens: when it was added, why it exists, and the links that prove it. Rows waiting on a human carry a Decide → link straight to the answerable question on the decisions page. Statuses are re-derived from live PR, decision and prod-evidence state by bin/refresh-trackers; nothing here is typed by hand. Merged and shipped both count as done (Gera, 2026-10-19); a prod_evidence permalink is what moves a row from Merged to Shipped.

PropFlow Docs