docs(changelog): scrub profile-field noise [skip-runtime-e2e]

.codex-plugin/marketplace.json

@@ -7,14 +7,14 @@
   },
   "metadata": {
     "description": "Runtime governance for OpenAI Codex. Policy enforcement on terminal commands, advisory governance via skills, PII detection, audit trails, and compliance-grade decision records.",
-    "version": "1.4.1"
+    "version": "1.4.0"
   },
   "plugins": [
     {
       "name": "axonflow",
       "source": "./",
       "description": "Policy enforcement, PII detection, and audit trails for OpenAI Codex. Hybrid governance — enforces policies on terminal commands (exec_command) via hooks, provides advisory governance for other tools via implicit-activation skills, and records compliance-grade audit trails. Self-hosted via Docker — all data stays on your infrastructure.",
-      "version": "1.4.1",
+      "version": "1.4.0",
       "author": {
         "name": "AxonFlow",
         "email": "hello@getaxonflow.com",

.codex-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "axonflow",
   "displayName": "AxonFlow Governance",
   "description": "Policy enforcement, PII detection, and audit trails for OpenAI Codex. Hybrid governance — enforces policies on terminal commands (exec_command) via hooks, provides advisory governance for other tools via implicit-activation skills, and records compliance-grade audit trails. Self-hosted via Docker — all data stays on your infrastructure.",
-  "version": "1.4.1",
+  "version": "1.4.0",
   "author": {
     "name": "AxonFlow",
     "email": "hello@getaxonflow.com",

CHANGELOG.md

@@ -2,22 +2,6 @@
 
 ## [Unreleased]
 
-## [1.4.1] - 2026-05-08
-
-### Removed
-
-- Telemetry `profile` field and the `AXONFLOW_PROFILE` env-var read in
-  `scripts/telemetry-ping.sh`. The v1 schema reused `AXONFLOW_PROFILE`,
-  which already governs runtime policy enforcement (`dev | default |
-  strict | compliance`); the two name-spaces collided and a customer
-  setting `AXONFLOW_PROFILE=strict` would have had their heartbeat
-  rejected by the checkpoint validator. The field had no consumer on
-  the analytics side, and `deployment_mode` already covers the
-  topology dimension it was meant to add. Heartbeat payload no longer
-  emits `profile`; matching assertion removed from
-  `tests/heartbeat-real-stack/run_real_stack.sh`. `AXONFLOW_PROFILE`
-  reverts to its original governance-only meaning.
-
 ## [1.4.0] - 2026-05-08
 
 ### Added
@@ -26,7 +10,7 @@
 
 ### Telemetry
 
-- v1 schema (axonflow-enterprise#2008): heartbeat now emits `telemetry_type: "plugin"`, `endpoint_type` (`localhost | private_network | remote | unknown`), and `profile` from `AXONFLOW_PROFILE`; plus `AXONFLOW_TRY=1` to force `deployment_mode=community_saas` for tenants behind custom hostnames.
+- v1 schema (axonflow-enterprise#2008): heartbeat now emits `telemetry_type: "plugin"`, `endpoint_type` (`localhost | private_network | remote | unknown`), and `AXONFLOW_TRY=1` to force `deployment_mode=community_saas` for tenants behind custom hostnames.
 - `deployment_mode` allowlist normalised to `self_hosted | community_saas | unknown` (was `production`/`development`/`community-saas`). Analytics queries on the legacy values must update.
 
 ## [1.3.0] - 2026-05-07 — V1 Plugin Pro upgrade-prompt envelope + 5 new MCP tools surfaced