Python Control points & optional initialise add-ons
Initialise now wires Python services to the fireweave package on PyPI, so a Python surface can evaluate Fireweave Control points in production the same way TypeScript already does. Observability and other add-ons stay offers — declining one that is off no longer parks the run.
Python joins the Control points path
A Python service initialised this week binds the fireweave PyPI package — remote evaluation in production, the local provider in development, through the same init_fireweave call. Control points only: initialise does not ship a half-wired Python deploy path.
Optional add-ons are offers
Observability and other initialise add-ons are offers, not preconditions. Declining one the project has never enabled continues the run; a provisioning miss for an add-on nobody turned on no longer costs you the harness.
Improved
- fw --version names the distribution channel (stable vs staging) next to the version
- Initialise installs SDKs with the repo’s own package manager
Fixed
- A rollback to 0% occupies the baseline instead of clamping it away