Fix documentation accuracy across 74 files

Comprehensive audit of all HORUS documentation against actual codebase.
Key fixes: corrected API method names, removed nonexistent builder
methods, fixed Python hardware node constructor signatures, removed
false AVX512 claims, corrected SIMD thresholds, added planned-feature
notices for unimplemented APIs, fixed metrics field names, and removed
deleted message type pages.

Author: neos-builder

MDX_GUIDELINES.md

@@ -26,15 +26,15 @@
 
 **WRONG**:
 ```markdown
-### Error: "Failed to create Hub<T>"
+### Error: "Failed to create Topic<T>"
 ```
 
 **CORRECT**:
 ```markdown
-### Error: "Failed to create `Hub<T>`"
+### Error: "Failed to create `Topic<T>`"
 ```
 
-**Why**: MDX interprets `Hub<T>` as a JSX component. Always wrap generic types in backticks.
+**Why**: MDX interprets `Topic<T>` as a JSX component. Always wrap generic types in backticks.
 
 ### 3. Comparison Operators in Text
 
@@ -89,7 +89,7 @@ Inside code blocks, you can use `<` and `>` normally:
 
 ```markdown
 \`\`\`rust
-let hub: Hub<f32> = Hub::new("topic")?;
+let topic: Topic<f32> = Topic::new("sensor")?;
 if value < 100 {
     // This is fine inside code blocks
 }
@@ -101,7 +101,7 @@ if value < 100 {
 Inside backticks, you can use `<` and `>`:
 
 ```markdown
-Use `Hub<T>` for pub-sub messaging.
+Use `Topic<T>` for IPC messaging.
 Values `<100` are considered low.
 ```
 
@@ -117,7 +117,7 @@ Values `<100` are considered low.
 ## Quick Checklist Before Committing
 
 - [ ] Search file for `<[0-9]` patterns outside code blocks
-- [ ] Search file for `<[A-Z]` patterns (like `Hub<T>`) outside backticks
+- [ ] Search file for `<[A-Z]` patterns (like `Topic<T>`) outside backticks
 - [ ] Check that all comparison operators use HTML entities
 - [ ] Verify headings don't start with raw numbers
 - [ ] Build locally: `npm run build` should show no MDX errors
@@ -141,8 +141,8 @@ If you see "Error loading doc" messages, you likely have an MDX syntax issue.
 **Fix**: Change to `&lt;1`
 
 ### "Unexpected character before name, expected a letter"
-**Cause**: Using generic types without backticks (e.g., `Hub<T>`)
-**Fix**: Wrap in backticks: `` `Hub<T>` ``
+**Cause**: Using generic types without backticks (e.g., `Topic<T>`)
+**Fix**: Wrap in backticks: `` `Topic<T>` ``
 
 ## Files to Check
 

README.md

@@ -107,7 +107,7 @@ We welcome contributions! To contribute to the documentation:
 
 Common mistakes to avoid:
 - Using `<` directly in text (e.g., `<1%` should be `&lt;1%`)
-- Writing generic types without backticks (e.g., `Hub<T>` should be `` `Hub<T>` ``)
+- Writing generic types without backticks (e.g., `Topic<T>` should be `` `Topic<T>` ``)
 - Starting headings with numbers
 
 General guidelines:

components/DocsSidebar.tsx

@@ -65,6 +65,7 @@ const sections: SidebarSection[] = [
       { title: "Message Types", href: "/concepts/message-types", order: 7 },
       { title: "Real-Time Nodes", href: "/concepts/realtime-nodes", order: 9 },
       { title: "HFrame Transforms", href: "/concepts/hframe", order: 10 },
+      { title: "Zero-Overhead IPC", href: "/concepts/zero-overhead-ipc", order: 11 },
       { title: "Multi-Language", href: "/concepts/multi-language", order: 13 },
     ],
   },
@@ -90,17 +91,15 @@ const sections: SidebarSection[] = [
             children: [
               { title: "Overview", href: "/rust/api/messages", order: 0 },
               { title: "Control", href: "/rust/api/control-messages", order: 1 },
-              { title: "Coordination", href: "/rust/api/coordination-messages", order: 2 },
-              { title: "Diagnostics", href: "/rust/api/diagnostics-messages", order: 3 },
+              { title: "Diagnostics", href: "/rust/api/diagnostics-messages", order: 2 },
               { title: "Force", href: "/rust/api/force-messages", order: 4 },
               { title: "Geometry", href: "/rust/api/geometry-messages", order: 5 },
 
               { title: "ML", href: "/rust/api/ml-messages", order: 7 },
               { title: "Navigation", href: "/rust/api/navigation-messages", order: 8 },
               { title: "Perception", href: "/rust/api/perception-messages", order: 9 },
               { title: "Sensor", href: "/rust/api/sensor-messages", order: 10 },
-              { title: "Timing", href: "/rust/api/timing-messages", order: 11 },
-              { title: "Vision", href: "/rust/api/vision-messages", order: 12 },
+              { title: "Vision", href: "/rust/api/vision-messages", order: 10 },
             ]
           },
         ]
@@ -173,12 +172,9 @@ const sections: SidebarSection[] = [
       { title: "BlackBox Recorder", href: "/advanced/blackbox", order: 7 },
       { title: "Circuit Breaker", href: "/advanced/circuit-breaker", order: 9 },
       { title: "Safety Monitor", href: "/advanced/safety-monitor", order: 10 },
-      { title: "Checkpoint System", href: "/advanced/checkpoint", order: 11 },
-      { title: "Model Registry", href: "/advanced/model-registry", order: 12 },
-      { title: "Record & Replay", href: "/advanced/record-replay", order: 13 },
-      { title: "Redundancy", href: "/advanced/redundancy", order: 14 },
-      { title: "Telemetry", href: "/advanced/telemetry", order: 15 },
-      { title: "Real-Time Configuration", href: "/advanced/rt-config", order: 16 },
+      { title: "Model Registry", href: "/advanced/model-registry", order: 11 },
+      { title: "Record & Replay", href: "/advanced/record-replay", order: 12 },
+      { title: "Real-Time Configuration", href: "/advanced/rt-config", order: 13 },
     ],
   },
   {

components/PrevNextNav.tsx

@@ -53,7 +53,6 @@ const allPages: DocLink[] = [
   { title: "Hardware Discovery", href: "/rust/api/hardware" },
   { title: "Messages Overview", href: "/rust/api/messages" },
   { title: "Control Messages", href: "/rust/api/control-messages" },
-  { title: "Coordination Messages", href: "/rust/api/coordination-messages" },
   { title: "Diagnostics Messages", href: "/rust/api/diagnostics-messages" },
   { title: "Force Messages", href: "/rust/api/force-messages" },
   { title: "Geometry Messages", href: "/rust/api/geometry-messages" },
@@ -62,7 +61,6 @@ const allPages: DocLink[] = [
   { title: "Navigation Messages", href: "/rust/api/navigation-messages" },
   { title: "Perception Messages", href: "/rust/api/perception-messages" },
   { title: "Sensor Messages", href: "/rust/api/sensor-messages" },
-  { title: "Timing Messages", href: "/rust/api/timing-messages" },
   { title: "Vision Messages", href: "/rust/api/vision-messages" },
   { title: "Rust Examples", href: "/rust/examples" },
   { title: "Basic Examples", href: "/rust/examples/basic-examples" },

content/docs/advanced/blackbox.mdx

@@ -18,17 +18,7 @@ The BlackBox system:
 
 ## Enabling BlackBox
 
-### Via Scheduler Builder (Recommended)
-
-```rust
-use horus::prelude::*;
-
-// Enable with 16MB buffer
-let scheduler = Scheduler::new()
-    .with_blackbox(16);  // 16MB flight recorder
-```
-
-### Via Deploy Preset
+### Via Deploy Preset (Recommended)
 
 The `deploy()` preset enables blackbox automatically with 16MB:
 
@@ -44,13 +34,7 @@ let scheduler = Scheduler::deploy();
 ```rust
 use horus::prelude::*;
 
-// Using the builder method
-let config = SchedulerConfig::standard()
-    .with_black_box(true, 10);  // Enabled with 10MB buffer
-
-let scheduler = Scheduler::new().with_config(config);
-
-// Or set fields directly
+// Set blackbox fields on SchedulerConfig
 let mut config = SchedulerConfig::standard();
 config.monitoring.black_box_enabled = true;
 config.monitoring.black_box_size_mb = 10;
@@ -137,7 +121,7 @@ blackbox.record(BlackBoxEvent::DeadlineMiss {
 ### Get All Events
 
 ```rust
-let events = blackbox.get_events();
+let events = blackbox.events();
 println!("Total events: {}", events.len());
 
 for record in &events {
@@ -155,7 +139,7 @@ Each `BlackBoxRecord` contains:
 Filter for error-related events (errors, deadline misses, WCET violations, circuit breaker changes, emergency stops):
 
 ```rust
-let anomalies = blackbox.get_anomalies();
+let anomalies = blackbox.anomalies();
 for record in &anomalies {
     println!("[tick {}] {:?}", record.tick, record.event);
 }
@@ -178,13 +162,16 @@ The Scheduler provides read and write access to its blackbox:
 ```rust
 use horus::prelude::*;
 
-let mut scheduler = Scheduler::new()
-    .with_blackbox(16);
+let mut config = SchedulerConfig::standard();
+config.monitoring.black_box_enabled = true;
+config.monitoring.black_box_size_mb = 16;
+
+let mut scheduler = Scheduler::new().with_config(config);
 
 // Read-only access
 if let Some(bb) = scheduler.blackbox() {
-    let events = bb.get_events();
-    let anomalies = bb.get_anomalies();
+    let events = bb.events();
+    let anomalies = bb.anomalies();
     println!("Recorded {} events, {} anomalies", events.len(), anomalies.len());
 }
 
@@ -223,7 +210,7 @@ std::thread::spawn(move || {
 
 | Parameter | Default | Description |
 |-----------|---------|-------------|
-| Buffer size | 0 (disabled) | Set via `BlackBox::new(mb)` or `with_blackbox(mb)` |
+| Buffer size | 0 (disabled) | Set via `BlackBox::new(mb)` or `config.monitoring.black_box_size_mb` |
 | Records per MB | ~5,000 | Estimated at ~200 bytes per record |
 | Max pre-allocated | 100,000 records | Initial capacity cap |
 | Min buffer | 1,000 records | Minimum regardless of size |
@@ -245,21 +232,20 @@ After a failure, use the blackbox to investigate what happened:
 ```rust
 use horus::prelude::*;
 
-let mut scheduler = Scheduler::new()
-    .with_blackbox(16);
+let mut scheduler = Scheduler::deploy();
 
 // ... run application ...
 
 // After a failure, inspect the blackbox
 if let Some(bb) = scheduler.blackbox() {
-    let anomalies = bb.get_anomalies();
+    let anomalies = bb.anomalies();
     println!("=== ANOMALIES ({}) ===", anomalies.len());
     for record in &anomalies {
         println!("[tick {}] {:?}", record.tick, record.event);
     }
 
     // Look at all events around the failure
-    let all_events = bb.get_events();
+    let all_events = bb.events();
     println!("\n=== LAST {} EVENTS ===", all_events.len());
     for record in all_events.iter().rev().take(20) {
         println!("[tick {}] {:?}", record.tick, record.event);

content/docs/advanced/circuit-breaker.mdx

@@ -189,17 +189,7 @@ The scheduler automatically manages circuit breakers for nodes:
 ```rust,ignore
 use horus::prelude::*;
 
-// Using builder method
-let config = SchedulerConfig::standard()
-    .with_circuit_breaker(true);
-
-let scheduler = Scheduler::new().with_config(config);
-
-// Or use the convenience alias
-let config = SchedulerConfig::deterministic()
-    .circuit_breaker();  // Same as .with_circuit_breaker(true)
-
-// Or configure thresholds directly
+// Configure thresholds directly
 let mut config = SchedulerConfig::standard();
 config.fault.circuit_breaker_enabled = true;
 config.fault.max_failures = 5;
@@ -208,8 +198,8 @@ config.fault.circuit_timeout_ms = 5000;
 
 let scheduler = Scheduler::new().with_config(config);
 
-// Circuit breaker events are recorded to BlackBox
-// CircuitBreakerChange { name, new_state, failure_count }
+// Note: standard() preset already has circuit_breaker_enabled = true
+// safety_critical() and deterministic() presets have it disabled
 ```
 
 ## Per-Node Configuration