Control points for new projects & safer ramp defaults
New projects land on internally managed Fireweave Control points infrastructure — no external PostHog project to wire — and ramps refuse to start with their safety rails silently off.
Control points on day one
Create a project and it is already on internally managed Fireweave Control points infrastructure — no external PostHog to connect, no picker, no “wire flags before you can ramp.” Existing projects still on external PostHog are unchanged this week.
Safer by default
Ramp kill-switches now default off, so a new rollout cannot disable its own guardrails by accident. Project- and organization-scoped APIs refuse unauthorized callers instead of failing open — the same access-control bar as the rest of the console.
Improved
- The org-wide rollout event feed is now Audit Logs — same stream, clearer name
- Rollout lists show what a held ramp is waiting on you for, not just that it is “ramping”
- Each project has its own alerts page, scoped to that project’s events
- Coding-agent sessions stay signed in through Cursor trailing-slash and OpenID companion-audience quirks
Fixed
- A carry-over stage cannot advance on an exposure nothing confirmed
- Interrupted hold timers keep their pending action across a wake