Fill in Developer Guide wiki pages
- Getting Started: prerequisites by OS, CMake presets, build/install,
editor setup, Docker CI images
- Coding Style: C++20 standard, formatting rules, naming conventions,
brace style, pointer alignment, comment philosophy, license headers,
debug logging patterns
- Contributing: issue filing, PR workflow, branching, labels, backports,
WIP PRs, communication channels
- Code Review: what reviewers look for, approval requirements, required
CI checks from .asf.yaml, squash merge policy, committer responsibilities
- Testing: Catch2 unit tests, AuTest end-to-end tests, running tests
locally and in parallel, writing new tests with Proxy Verifier,
sandbox structure, test coverage
Reorganize wiki structure with developer handbook pages
Add skeleton pages for a comprehensive developer wiki:
- Home: landing page with navigation and links
- Getting Started: build setup and dev environment
- Coding Style: formatting, naming, best practices
- Contributing: PR workflow and issue filing
- Code Review: review process and merge policy
- Testing: unit tests, AuTests, coverage
- Continuous Integration: CI checks and failure debugging
- Architecture Overview: event model, threading, state machine
- Release Process: branches, versioning, release management
- _Sidebar: persistent navigation for all pages
Update Home page from bare welcome to organized hub.
Update footer copyright year.