docs-validation: expand curated markdown scope to include all documentation hubs

Add all documentation subdirectories to the curated markdown linting targets, replacing the previous exclusion-based approach with comprehensive coverage. Update validation to check for required README files across all hubs and verify priority documentation metadata markers. Implement lazy loading for optional dependencies (numpy, redis, bcrypt, jwt, websockets) in agent-coordinator and related modules to improve startup

docs/about/DOCUMENTATION_COMPLIANCE_AUDIT.md

@@ -0,0 +1,135 @@
+# Documentation Compliance Audit
+
+**Level**: All Levels  
+**Prerequisites**: Familiarity with the AITBC docs tree and template standard  
+**Estimated Time**: 15-20 minutes  
+**Last Updated**: 2026-04-27  
+**Version**: 1.0
+
+## 🧭 **Navigation Path:**
+**🏠 [Documentation Home](../README.md)** → **📖 About** → **✅ Compliance Audit** → *You are here*
+
+**breadcrumb**: Home → About → Compliance Audit
+
+---
+
+## 🎯 **See Also:**
+- **📋 [Template Standard](DOCUMENTATION_TEMPLATE_STANDARD.md)** - Required metadata and structure
+- **🎯 [10/10 Roadmap](DOCS_10_10_ROADMAP.md)** - Quality goals and remediation themes
+- **📊 [Organization Analysis](DOCS_ORGANIZATION_ANALYSIS.md)** - Historical structure review
+- **🏠 [Documentation Home](../README.md)** - Main docs entry point
+- **🧭 [Master Index](../MASTER_INDEX.md)** - Full documentation catalog
+
+---
+
+## 🎯 **Audit Scope**
+
+This checklist tracks the current remediation target:
+
+- missing top-level index pages
+- standardized metadata on priority documents
+- breadcrumbs and cross-links on high-traffic pages
+- historical exceptions that should remain intentionally archived
+- repeatable validation so docs do not drift again
+
+---
+
+## ✅ **Top-Level Index Coverage**
+
+### Required directory indexes
+- [x] `about/README.md`
+- [x] `11_agents/README.md`
+- [x] `agent-sdk/README.md`
+- [x] `advanced/README.md`
+- [x] `analytics/README.md`
+- [x] `apps/README.md`
+- [x] `archive/README.md`
+- [x] `backend/README.md`
+- [x] `beginner/README.md`
+- [x] `blockchain/README.md`
+- [x] `completed/README.md`
+- [x] `contracts/README.md`
+- [x] `deployment/README.md`
+- [x] `development/README.md`
+- [x] `exchange/README.md`
+- [x] `expert/README.md`
+- [x] `general/README.md`
+- [x] `guides/README.md`
+- [x] `governance/README.md`
+- [x] `implementation/README.md`
+- [x] `infrastructure/README.md`
+- [x] `intermediate/README.md`
+- [x] `maintenance/README.md`
+- [x] `mobile/README.md`
+- [x] `nodes/README.md`
+- [x] `openclaw/README.md`
+- [x] `packages/README.md`
+- [x] `policies/README.md`
+- [x] `reference/README.md`
+- [x] `releases/README.md`
+- [x] `reports/README.md`
+- [x] `security/README.md`
+- [x] `summaries/README.md`
+- [x] `trail/README.md`
+- [x] `website/README.md`
+- [x] `workflows/README.md`
+
+### Documented exceptions
+- [x] `cli-technical/` is a special external technical entry point with a compliant landing page
+- [x] `testing/` is a special external documentation entry point with a compliant landing page
+
+---
+
+## ✅ **Priority Document Checks**
+
+### Core docs entry points
+- [ ] `docs/README.md` has `Level`, `Prerequisites`, `Estimated Time`, `Last Updated`, `Version`
+- [ ] `docs/README.md` has a navigation path and breadcrumb
+- [ ] `docs/README.md` links to `MASTER_INDEX.md` and the core learning paths
+- [ ] `docs/beginner/README.md` has standardized metadata and cross-links
+- [ ] `docs/intermediate/README.md` has standardized metadata and cross-links
+- [ ] `docs/advanced/README.md` has standardized metadata and cross-links
+- [ ] `docs/expert/README.md` has standardized metadata and cross-links
+- [x] `docs/project/README.md` has standardized metadata and cross-links
+- [x] `docs/apps/README.md` has standardized metadata and cross-links
+- [ ] `docs/about/README.md` links to the template standard and audit checklist
+
+### Historical or special content
+- [ ] `docs/archive/README.md` clearly marks archive content as historical
+- [ ] `docs/completed/README.md` clearly marks completed work as historical
+- [ ] `docs/implementation/README.md` remains intentionally lightweight until a future cleanup pass
+
+---
+
+## ✅ **Cross-Link Checks**
+
+- [ ] Root docs point at the current hierarchy, not obsolete paths
+- [ ] Beginner, project, and app landing pages point at each other where appropriate
+- [ ] About pages link back to the template standard and the audit checklist
+- [ ] Release notes link from the master index and release index
+- [ ] Policy and governance documents cross-reference each other cleanly
+
+---
+
+## ✅ **Validation Steps**
+
+1. Review the directory tree and confirm each top-level docs area has an index.
+2. Confirm priority docs include the template fields and navigation sections.
+3. Record exceptions instead of leaving them ambiguous.
+4. Re-run the docs validation workflow after making any navigation changes.
+
+---
+
+## 📝 **Current Remediation Notes**
+
+- Historical content stays in place unless it is clearly duplicated or misleading.
+- The goal is discoverability and consistency, not flattening every directory.
+- The following directories now have landing pages added in this pass: `about/`, `deployment/`, `development/`, `guides/`, `governance/`, `mobile/`, `nodes/`, `policies/`, `reference/`, `releases/`, `reports/`, `summaries/`, `trail/`, and `workflows/`.
+- The project and apps landing pages now include template-compliant related resources and quality metrics sections.
+- Any future docs area should either include a README index or be documented here as an intentional exception.
+
+---
+
+*Last updated: 2026-04-27*  
+*Version: 1.0*  
+*Status: Audit checklist*