@nockdev/awf 6.2.0 → 6.2.1

package/.agent/skills/core/observability/data/otel-core.yaml

@@ -1,195 +1,195 @@
 metadata:
   skill: observability
   domain: otel_core
-  version: 6.2.0
-  updated: '2026-02-05'
-  migrated_from: otel-core.csv
+  version: 6.2.1
+  updated: "2026-02-05"
+  migrated_from: otel-core.yaml
   patterns_count: 30
   columns:
-  - pattern_id
-  - name
-  - category
-  - description
-  - example
-  - level
+    - pattern_id
+    - name
+    - category
+    - description
+    - example
+    - level
 patterns:
-- id: OTEL-001
-  name: SDK Initialization
-  category: OpenTelemetry
-  description: Initialize OTel SDK in app startup
-  example: Configure TracerProvider, MeterProvider
-  level: beginner
-- id: OTEL-002
-  name: TracerProvider
-  category: OpenTelemetry
-  description: Factory for creating Tracers
-  example: Set exporter, sampler, resource
-  level: intermediate
-- id: OTEL-003
-  name: MeterProvider
-  category: OpenTelemetry
-  description: Factory for creating Meters
-  example: Configure views, readers
-  level: intermediate
-- id: OTEL-004
-  name: LoggerProvider
-  category: OpenTelemetry
-  description: Factory for creating Loggers
-  example: Bridge existing logging frameworks
-  level: intermediate
-- id: OTEL-005
-  name: OTLP Exporter
-  category: OpenTelemetry
-  description: Export telemetry via OTLP
-  example: Send to collector or backend
-  level: beginner
-- id: OTEL-006
-  name: Collector
-  category: OpenTelemetry
-  description: Receive, process, export telemetry
-  example: Central pipeline for all signals
-  level: intermediate
-- id: OTEL-007
-  name: Collector Processors
-  category: OpenTelemetry
-  description: Transform telemetry in collector
-  example: batch, filter, attributes processors
-  level: advanced
-- id: OTEL-008
-  name: Semantic Conventions
-  category: OpenTelemetry
-  description: Standardized attribute names
-  example: http.method, db.system, rpc.service
-  level: intermediate
-- id: OTEL-009
-  name: Resource Attributes
-  category: OpenTelemetry
-  description: Describe the entity producing telemetry
-  example: service.name, host.id, cloud.provider
-  level: beginner
-- id: OTEL-010
-  name: Auto-Instrumentation
-  category: OpenTelemetry
-  description: Zero-code instrumentation
-  example: OTel agents for frameworks
-  level: beginner
-- id: OTEL-011
-  name: Manual Instrumentation
-  category: OpenTelemetry
-  description: Add custom spans/metrics
-  example: tracer.startSpan(), meter.createCounter()
-  level: intermediate
-- id: OTEL-012
-  name: Span Creation
-  category: OpenTelemetry
-  description: Create a unit of work trace
-  example: withSpan('operation', () => {})
-  level: beginner
-- id: OTEL-013
-  name: Span Attributes
-  category: OpenTelemetry
-  description: Add metadata to spans
-  example: span.setAttribute('user.id', userId)
-  level: beginner
-- id: OTEL-014
-  name: Span Events
-  category: OpenTelemetry
-  description: Add timestamped events to span
-  example: span.addEvent('cache_miss')
-  level: intermediate
-- id: OTEL-015
-  name: Span Links
-  category: OpenTelemetry
-  description: Connect related but non-parent traces
-  example: Batch processing links
-  level: advanced
-- id: OTEL-016
-  name: Span Status
-  category: OpenTelemetry
-  description: Mark span as ok/error
-  example: span.setStatus(StatusCode.ERROR)
-  level: beginner
-- id: OTEL-017
-  name: Context API
-  category: OpenTelemetry
-  description: Propagate context across async
-  example: Context.current(), with(context)
-  level: intermediate
-- id: OTEL-018
-  name: W3C TraceContext
-  category: OpenTelemetry
-  description: Standard trace propagation headers
-  example: traceparent, tracestate
-  level: intermediate
-- id: OTEL-019
-  name: Baggage
-  category: OpenTelemetry
-  description: Pass user-defined key-value pairs
-  example: tenant_id in baggage
-  level: intermediate
-- id: OTEL-020
-  name: Metrics Types
-  category: OpenTelemetry
-  description: Counter, UpDownCounter, Histogram, Gauge
-  example: Choose appropriate type
-  level: beginner
-- id: OTEL-021
-  name: Metric Views
-  category: OpenTelemetry
-  description: Customize metric aggregation
-  example: Drop attributes, change aggregation
-  level: advanced
-- id: OTEL-022
-  name: Exemplars
-  category: OpenTelemetry
-  description: Link metrics to traces
-  example: Trace context in histogram bucket
-  level: advanced
-- id: OTEL-023
-  name: OTel Bridge
-  category: OpenTelemetry
-  description: Connect existing instrumentation to OTel
-  example: OpenTracing/OpenCensus bridge
-  level: advanced
-- id: OTEL-024
-  name: SDK Configuration
-  category: OpenTelemetry
-  description: Environment-based config
-  example: OTEL_EXPORTER_OTLP_ENDPOINT
-  level: beginner
-- id: OTEL-025
-  name: Span Sampling
-  category: OpenTelemetry
-  description: Control which spans are recorded
-  example: ParentBased, TraceIdRatio
-  level: intermediate
-- id: OTEL-026
-  name: Batch Processing
-  category: OpenTelemetry
-  description: Batch telemetry before export
-  example: BatchSpanProcessor
-  level: intermediate
-- id: OTEL-027
-  name: Delta vs Cumulative
-  category: OpenTelemetry
-  description: Temporality for metrics
-  example: Delta for StatsD, Cumulative for Prometheus
-  level: advanced
-- id: OTEL-028
-  name: OTLP Protocol
-  category: OpenTelemetry
-  description: Binary protocol for telemetry
-  example: gRPC or HTTP/protobuf
-  level: intermediate
-- id: OTEL-029
-  name: SDK vs API
-  category: OpenTelemetry
-  description: Separation of concerns
-  example: Libraries use API, apps configure SDK
-  level: intermediate
-- id: OTEL-030
-  name: Zero-Dependency API
-  category: OpenTelemetry
-  description: No-op API for libraries
-  example: Instrumented libraries without SDK overhead
-  level: advanced
+  - id: OTEL-001
+    name: SDK Initialization
+    category: OpenTelemetry
+    description: Initialize OTel SDK in app startup
+    example: Configure TracerProvider, MeterProvider
+    level: beginner
+  - id: OTEL-002
+    name: TracerProvider
+    category: OpenTelemetry
+    description: Factory for creating Tracers
+    example: Set exporter, sampler, resource
+    level: intermediate
+  - id: OTEL-003
+    name: MeterProvider
+    category: OpenTelemetry
+    description: Factory for creating Meters
+    example: Configure views, readers
+    level: intermediate
+  - id: OTEL-004
+    name: LoggerProvider
+    category: OpenTelemetry
+    description: Factory for creating Loggers
+    example: Bridge existing logging frameworks
+    level: intermediate
+  - id: OTEL-005
+    name: OTLP Exporter
+    category: OpenTelemetry
+    description: Export telemetry via OTLP
+    example: Send to collector or backend
+    level: beginner
+  - id: OTEL-006
+    name: Collector
+    category: OpenTelemetry
+    description: Receive, process, export telemetry
+    example: Central pipeline for all signals
+    level: intermediate
+  - id: OTEL-007
+    name: Collector Processors
+    category: OpenTelemetry
+    description: Transform telemetry in collector
+    example: batch, filter, attributes processors
+    level: advanced
+  - id: OTEL-008
+    name: Semantic Conventions
+    category: OpenTelemetry
+    description: Standardized attribute names
+    example: http.method, db.system, rpc.service
+    level: intermediate
+  - id: OTEL-009
+    name: Resource Attributes
+    category: OpenTelemetry
+    description: Describe the entity producing telemetry
+    example: service.name, host.id, cloud.provider
+    level: beginner
+  - id: OTEL-010
+    name: Auto-Instrumentation
+    category: OpenTelemetry
+    description: Zero-code instrumentation
+    example: OTel agents for frameworks
+    level: beginner
+  - id: OTEL-011
+    name: Manual Instrumentation
+    category: OpenTelemetry
+    description: Add custom spans/metrics
+    example: tracer.startSpan(), meter.createCounter()
+    level: intermediate
+  - id: OTEL-012
+    name: Span Creation
+    category: OpenTelemetry
+    description: Create a unit of work trace
+    example: withSpan('operation', () => {})
+    level: beginner
+  - id: OTEL-013
+    name: Span Attributes
+    category: OpenTelemetry
+    description: Add metadata to spans
+    example: span.setAttribute('user.id', userId)
+    level: beginner
+  - id: OTEL-014
+    name: Span Events
+    category: OpenTelemetry
+    description: Add timestamped events to span
+    example: span.addEvent('cache_miss')
+    level: intermediate
+  - id: OTEL-015
+    name: Span Links
+    category: OpenTelemetry
+    description: Connect related but non-parent traces
+    example: Batch processing links
+    level: advanced
+  - id: OTEL-016
+    name: Span Status
+    category: OpenTelemetry
+    description: Mark span as ok/error
+    example: span.setStatus(StatusCode.ERROR)
+    level: beginner
+  - id: OTEL-017
+    name: Context API
+    category: OpenTelemetry
+    description: Propagate context across async
+    example: Context.current(), with(context)
+    level: intermediate
+  - id: OTEL-018
+    name: W3C TraceContext
+    category: OpenTelemetry
+    description: Standard trace propagation headers
+    example: traceparent, tracestate
+    level: intermediate
+  - id: OTEL-019
+    name: Baggage
+    category: OpenTelemetry
+    description: Pass user-defined key-value pairs
+    example: tenant_id in baggage
+    level: intermediate
+  - id: OTEL-020
+    name: Metrics Types
+    category: OpenTelemetry
+    description: Counter, UpDownCounter, Histogram, Gauge
+    example: Choose appropriate type
+    level: beginner
+  - id: OTEL-021
+    name: Metric Views
+    category: OpenTelemetry
+    description: Customize metric aggregation
+    example: Drop attributes, change aggregation
+    level: advanced
+  - id: OTEL-022
+    name: Exemplars
+    category: OpenTelemetry
+    description: Link metrics to traces
+    example: Trace context in histogram bucket
+    level: advanced
+  - id: OTEL-023
+    name: OTel Bridge
+    category: OpenTelemetry
+    description: Connect existing instrumentation to OTel
+    example: OpenTracing/OpenCensus bridge
+    level: advanced
+  - id: OTEL-024
+    name: SDK Configuration
+    category: OpenTelemetry
+    description: Environment-based config
+    example: OTEL_EXPORTER_OTLP_ENDPOINT
+    level: beginner
+  - id: OTEL-025
+    name: Span Sampling
+    category: OpenTelemetry
+    description: Control which spans are recorded
+    example: ParentBased, TraceIdRatio
+    level: intermediate
+  - id: OTEL-026
+    name: Batch Processing
+    category: OpenTelemetry
+    description: Batch telemetry before export
+    example: BatchSpanProcessor
+    level: intermediate
+  - id: OTEL-027
+    name: Delta vs Cumulative
+    category: OpenTelemetry
+    description: Temporality for metrics
+    example: Delta for StatsD, Cumulative for Prometheus
+    level: advanced
+  - id: OTEL-028
+    name: OTLP Protocol
+    category: OpenTelemetry
+    description: Binary protocol for telemetry
+    example: gRPC or HTTP/protobuf
+    level: intermediate
+  - id: OTEL-029
+    name: SDK vs API
+    category: OpenTelemetry
+    description: Separation of concerns
+    example: Libraries use API, apps configure SDK
+    level: intermediate
+  - id: OTEL-030
+    name: Zero-Dependency API
+    category: OpenTelemetry
+    description: No-op API for libraries
+    example: Instrumented libraries without SDK overhead
+    level: advanced

package/.agent/skills/core/observability/data/profiling-patterns.yaml

@@ -1,135 +1,135 @@
 metadata:
   skill: observability
   domain: profiling_patterns
-  version: 6.2.0
-  updated: '2026-02-05'
-  migrated_from: profiling-patterns.csv
+  version: 6.2.1
+  updated: "2026-02-05"
+  migrated_from: profiling-patterns.yaml
   patterns_count: 20
   columns:
-  - pattern_id
-  - name
-  - category
-  - description
-  - example
-  - level
+    - pattern_id
+    - name
+    - category
+    - description
+    - example
+    - level
 patterns:
-- id: PROF-001
-  name: CPU Profiling
-  category: Profiling
-  description: Measure CPU time per function
-  example: pprof cpu profile Go
-  level: beginner
-- id: PROF-002
-  name: Memory Profiling
-  category: Profiling
-  description: Track heap allocations
-  example: Heap profile, allocation sites
-  level: beginner
-- id: PROF-003
-  name: Flame Graphs
-  category: Profiling
-  description: Visualize call stack hotspots
-  example: Wide = more time spent
-  level: beginner
-- id: PROF-004
-  name: Continuous Profiling
-  category: Profiling
-  description: Always-on production profiling
-  example: Low overhead, historical data
-  level: intermediate
-- id: PROF-005
-  name: pprof
-  category: Profiling
-  description: Go's built-in profiler
-  example: net/http/pprof, go tool pprof
-  level: beginner
-- id: PROF-006
-  name: Valgrind
-  category: Profiling
-  description: Memory debugging for C/C++
-  example: Memcheck, Callgrind
-  level: intermediate
-- id: PROF-007
-  name: Tracy
-  category: Profiling
-  description: Real-time C++ profiler
-  example: Nanosecond resolution
-  level: advanced
-- id: PROF-008
-  name: perf
-  category: Profiling
-  description: Linux kernel profiler
-  example: perf record, perf report
-  level: intermediate
-- id: PROF-009
-  name: async-profiler
-  category: Profiling
-  description: JVM sampling profiler
-  example: CPU and allocation profiling
-  level: intermediate
-- id: PROF-010
-  name: py-spy
-  category: Profiling
-  description: Python sampling profiler
-  example: No code changes needed
-  level: beginner
-- id: PROF-011
-  name: Pyroscope
-  category: Profiling
-  description: Continuous profiling platform
-  example: Open source, multi-language
-  level: intermediate
-- id: PROF-012
-  name: Parca
-  category: Profiling
-  description: Continuous profiling CNCF
-  example: eBPF-based collection
-  level: advanced
-- id: PROF-013
-  name: Allocation Profiling
-  category: Profiling
-  description: Track memory allocation rate
-  example: Find allocation hotspots
-  level: intermediate
-- id: PROF-014
-  name: Block Profiling
-  category: Profiling
-  description: Find goroutine blocking
-  example: Mutex contention in Go
-  level: advanced
-- id: PROF-015
-  name: Goroutine Profiling
-  category: Profiling
-  description: Track active goroutines
-  example: Detect goroutine leaks
-  level: intermediate
-- id: PROF-016
-  name: Wall Clock Profiling
-  category: Profiling
-  description: Include waiting time
-  example: Not just CPU time
-  level: intermediate
-- id: PROF-017
-  name: Off-CPU Analysis
-  category: Profiling
-  description: Time waiting on I/O/locks
-  example: Complement to CPU profiling
-  level: advanced
-- id: PROF-018
-  name: eBPF Profiling
-  category: Profiling
-  description: Kernel-level profiling
-  example: Low overhead, production safe
-  level: advanced
-- id: PROF-019
-  name: Profile Diffing
-  category: Profiling
-  description: Compare profiles over time
-  example: Before/after optimization
-  level: intermediate
-- id: PROF-020
-  name: Profile-to-Trace
-  category: Profiling
-  description: Link profiles to traces
-  example: OTel profiling signal
-  level: advanced
+  - id: PROF-001
+    name: CPU Profiling
+    category: Profiling
+    description: Measure CPU time per function
+    example: pprof cpu profile Go
+    level: beginner
+  - id: PROF-002
+    name: Memory Profiling
+    category: Profiling
+    description: Track heap allocations
+    example: Heap profile, allocation sites
+    level: beginner
+  - id: PROF-003
+    name: Flame Graphs
+    category: Profiling
+    description: Visualize call stack hotspots
+    example: Wide = more time spent
+    level: beginner
+  - id: PROF-004
+    name: Continuous Profiling
+    category: Profiling
+    description: Always-on production profiling
+    example: Low overhead, historical data
+    level: intermediate
+  - id: PROF-005
+    name: pprof
+    category: Profiling
+    description: Go's built-in profiler
+    example: net/http/pprof, go tool pprof
+    level: beginner
+  - id: PROF-006
+    name: Valgrind
+    category: Profiling
+    description: Memory debugging for C/C++
+    example: Memcheck, Callgrind
+    level: intermediate
+  - id: PROF-007
+    name: Tracy
+    category: Profiling
+    description: Real-time C++ profiler
+    example: Nanosecond resolution
+    level: advanced
+  - id: PROF-008
+    name: perf
+    category: Profiling
+    description: Linux kernel profiler
+    example: perf record, perf report
+    level: intermediate
+  - id: PROF-009
+    name: async-profiler
+    category: Profiling
+    description: JVM sampling profiler
+    example: CPU and allocation profiling
+    level: intermediate
+  - id: PROF-010
+    name: py-spy
+    category: Profiling
+    description: Python sampling profiler
+    example: No code changes needed
+    level: beginner
+  - id: PROF-011
+    name: Pyroscope
+    category: Profiling
+    description: Continuous profiling platform
+    example: Open source, multi-language
+    level: intermediate
+  - id: PROF-012
+    name: Parca
+    category: Profiling
+    description: Continuous profiling CNCF
+    example: eBPF-based collection
+    level: advanced
+  - id: PROF-013
+    name: Allocation Profiling
+    category: Profiling
+    description: Track memory allocation rate
+    example: Find allocation hotspots
+    level: intermediate
+  - id: PROF-014
+    name: Block Profiling
+    category: Profiling
+    description: Find goroutine blocking
+    example: Mutex contention in Go
+    level: advanced
+  - id: PROF-015
+    name: Goroutine Profiling
+    category: Profiling
+    description: Track active goroutines
+    example: Detect goroutine leaks
+    level: intermediate
+  - id: PROF-016
+    name: Wall Clock Profiling
+    category: Profiling
+    description: Include waiting time
+    example: Not just CPU time
+    level: intermediate
+  - id: PROF-017
+    name: Off-CPU Analysis
+    category: Profiling
+    description: Time waiting on I/O/locks
+    example: Complement to CPU profiling
+    level: advanced
+  - id: PROF-018
+    name: eBPF Profiling
+    category: Profiling
+    description: Kernel-level profiling
+    example: Low overhead, production safe
+    level: advanced
+  - id: PROF-019
+    name: Profile Diffing
+    category: Profiling
+    description: Compare profiles over time
+    example: Before/after optimization
+    level: intermediate
+  - id: PROF-020
+    name: Profile-to-Trace
+    category: Profiling
+    description: Link profiles to traces
+    example: OTel profiling signal
+    level: advanced