feat: log memory warnings instrumentation #40
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Note
Add memory warning auto-instrumentation that logs pressure events and integrate new CPU/memory stress tools and navigation in the Example app.
Options.AutoInstrumented.memoryWarningsand semantic attrSemanticConvention.systemMemoryWarning.MemoryPressureMonitorauto-instrumentation to log warning/critical memory pressure events.MemoryPressureMonitorinObservabilityClientFactorywhen logs are enabled andautoInstrumentationincludes.memoryWarnings..memoryWarningsinClientconfig.CpuLoadGenerator,MemoryPressurizer, andSystemUnderPressureViewwith navigation (Path.stressSamples) and UI entry point.@EnvironmentObject/@StateObjectforBrowserand update navigation wiring.16.6for the app target.Written by Cursor Bugbot for commit 3e48c8d. This will update automatically on new commits. Configure here.