Docs updates (#55)

* version bumps

* wip

* tmp

* wip

* wip

* wip

* more files

* more

* wip

* registries

* more

* wip selectors

* synapse

* registration flow

* connection handling

* state propagation

* testing 1

* moving stuff

* cleanup

* Update documentation links for Scheduler, Configuration Sourcing, and Lifecycle events

* Remove Testing section from navigation and update documentation links for Core Framework

* testing

* include contributions

* docs: Update links in fixtures and hass documentation for consistency

Author: zoe-codez

blog/01-building-a-basic-automation.md

@@ -170,7 +170,7 @@ export function WeatherReport({ scheduler, logger, hass }: TServiceParams) {
 }
 ```
 
-> See [Scheduler](/docs/core/tools/scheduler) for more specific documentation.
+> See [Scheduler](/docs/core/services/builtin/core_scheduler) for more specific documentation.
 
 ## 🎬 Bringing it all together
 

docs/core/advanced/async-local-storage.md

@@ -0,0 +1,59 @@
+---
+title: AsyncLocalStorage (ALS)
+---
+
+AsyncLocalStorage (ALS) is a Node.js feature that allows you to store data that is accessible throughout an entire async operation chain, without explicitly passing it through every function call. The Digital Alchemy framework provides special support for ALS to enable request-level context tracking and correlation.
+
+Think of it as a "thread-local storage" for async operations - data stored in ALS is automatically available to all code that runs within the same async context, regardless of how deep the call stack goes.
+
+## How ALS Works in the Framework
+
+### 1. ALS Service
+
+The framework provides an ALS service that manages the storage context:
+
+```typescript
+type AlsExtension = {
+  asyncStorage: () => AsyncLocalStorage<AsyncLocalData>;
+  getStore: () => AsyncLocalData;
+  run(data: AsyncLocalData, callback: () => TBlackHole): void;
+  enterWith(data: AsyncLocalData): void;
+  getLogData: () => AsyncLogData;
+};
+```
+
+### 2. Logger Integration
+
+When ALS is enabled in logger configuration, the framework automatically:
+
+- Extracts ALS data from the current context
+- Merges it into log messages
+- Provides timing information if available
+
+```typescript
+MY_APP.bootstrap({
+  loggerOptions: {
+    als: true  // Enable ALS integration
+  }
+});
+```
+
+##
+
+## ALS Data Structure
+
+The framework expects ALS data to follow this structure:
+
+```typescript
+interface AsyncLocalData {
+  logs: AsyncLogData;
+  http?: RequestLocals;
+}
+
+interface AsyncLogData {
+  reqId?: string;
+  correlationId?: string;
+  startTime?: number;
+  [key: string]: unknown;
+}
+```

…/home-automation/synapse/entity-types.md docs/core/advanced/boot-perf-metrics.mddocs/home-automation/synapse/entity-types.md renamed to docs/core/advanced/boot-perf-metrics.md docs/home-automation/synapse/entity-types.md renamed to docs/core/advanced/boot-perf-metrics.md

@@ -0,0 +1,6 @@
+---
+title: Advanced
+id: core_advanced
+sidebar_position: 5
+description: ""
+---

docs/core/advanced/bootstrap.md

@@ -0,0 +1 @@
+<!-- Bootstrap overrides -->