feat(calm): rename observability to deployment-details in deployment decorator

Refs #1908

Author: harveymmaunders

calm/draft/2026-03/standards/deployment/README.md

@@ -4,7 +4,7 @@ This directory contains standardized deployment decorator schemas for tracking d
 
 ## Overview
 
-Deployment decorators attach deployment tracking information to architecture elements without modifying the core architecture definition. They enable tracking of deployment status, timing, observability links, and platform-specific details across the architecture lifecycle.
+Deployment decorators attach deployment tracking information to architecture elements without modifying the core architecture definition. They enable tracking of deployment status, timing, deployment details links, and platform-specific details across the architecture lifecycle.
 
 ## Base Deployment Decorator
 
@@ -14,7 +14,7 @@ The base deployment decorator standard (`deployment.decorator.standard.json`) de
 - **status**: Current deployment status (pending, in-progress, completed, failed, rolled-back) (required)
 - **target-type**: Type of resources this decorator targets - must be ["architecture"] (required)
 - **end-time**: ISO 8601 timestamp of when the deployment completed or failed
-- **observability**: URI linking to logs, metrics, or observability dashboards
+- **deployment-details**: URI linking to logs, metrics, or observability dashboards
 - **notes**: Free-form notes or comments about the deployment
 
 ## Platform-Specific Extensions
@@ -42,7 +42,7 @@ Platform-specific deployment decorators extend the base deployment standard and
     "start-time": "2026-02-23T10:00:00Z",
     "end-time": "2026-02-23T10:05:00Z",
     "status": "completed",
-    "observability": "https://grafana.example.com/d/api-service",
+    "deployment-details": "https://grafana.example.com/d/api-service",
     "notes": "Successful deployment with zero downtime"
   }
 }
@@ -62,7 +62,7 @@ Platform-specific deployment decorators extend the base deployment standard and
     "start-time": "2026-02-23T10:00:00Z",
     "end-time": "2026-02-23T10:08:00Z",
     "status": "completed",
-    "observability": "https://grafana.example.com/d/k8s-prod",
+    "deployment-details": "https://grafana.example.com/d/k8s-prod",
     "notes": "Rolling update with new features",
     "kubernetes": {
       "helm-chart-version": "1.2.3",

calm/draft/2026-03/standards/deployment/deployment.decorator.standard.json

@@ -48,7 +48,7 @@
                             ],
                             "description": "Current status of the deployment"
                         },
-                        "observability": {
+                        "deployment-details": {
                             "type": "string",
                             "format": "uri",
                             "description": "URI linking to deployment logs, metrics, dashboards, or observability platform"

calm/draft/2026-03/standards/deployment/examples/README.md

@@ -86,7 +86,7 @@ See: `kubernetes-deployment.decorator.json`
 1. **Unique IDs**: Use descriptive unique-id values that include the service name and deployment identifier
 2. **Target Type**: Always include `"target-type": ["architecture"]` as deployment decorators only target architecture files
 3. **Timestamps**: Always use ISO 8601 format with timezone (preferably UTC)
-4. **Observability Links**: Link to deployment-specific dashboards or filtered log views
+4. **Deployment Details Links**: Link to deployment-specific dashboards or filtered log views
 5. **Notes**: Include context about what changed, why, and any issues encountered
 
 ## Validation

calm/draft/2026-03/standards/deployment/examples/failed-deployment.decorator.json

@@ -15,7 +15,7 @@
         "start-time": "2026-02-23T08:15:00Z",
         "end-time": "2026-02-23T08:23:45Z",
         "status": "failed",
-        "observability": "https://grafana.example.com/d/payment-processor-prod",
+        "deployment-details": "https://grafana.example.com/d/payment-processor-prod",
         "notes": "Deployment failed due to database migration timeout. Rolling back to 2.9.1."
     }
 }

calm/draft/2026-03/standards/deployment/examples/kubernetes-deployment.decorator.json

@@ -16,7 +16,7 @@
         "start-time": "2026-02-23T14:30:00Z",
         "end-time": "2026-02-23T14:42:15Z",
         "status": "completed",
-        "observability": "https://grafana.example.com/d/platform-services",
+        "deployment-details": "https://grafana.example.com/d/platform-services",
         "notes": "Rolling update with new authentication features",
         "kubernetes": {
             "helm-chart-version": "2.1.0",

calm/draft/2026-03/standards/deployment/examples/multi-target-deployment.decorator.json

@@ -17,7 +17,7 @@
     "data": {
         "start-time": "2026-02-23T12:00:00Z",
         "status": "in-progress",
-        "observability": "https://datadog.example.com/dashboard/release-2024-02-23",
+        "deployment-details": "https://datadog.example.com/dashboard/release-2024-02-23",
         "notes": "Coordinated release across frontend and backend services for new feature rollout",
         "kubernetes": {
             "helm-chart-version": "3.0.0",

calm/draft/2026-03/standards/deployment/examples/simple-deployment.decorator.json

@@ -15,7 +15,7 @@
         "start-time": "2026-02-23T10:00:00Z",
         "end-time": "2026-02-23T10:05:30Z",
         "status": "completed",
-        "observability": "https://grafana.example.com/d/web-service-prod",
+        "deployment-details": "https://grafana.example.com/d/web-service-prod",
         "notes": "Initial production deployment with baseline configuration"
     }
 }