Audit, reorganize, and modernize the project wiki

### Description

Turn the project wiki into a current, navigable source of durable team knowledge by auditing existing pages, defining a clear information architecture, updating or retiring stale content, and establishing lightweight ownership.

### Action Items

- [ ] Inventory every wiki page, its purpose, audience, owner when known, last meaningful update, inbound links, and apparent accuracy.
- [ ] Classify each page as retain, update, merge, move to the repository, archive, or retire; preserve history and redirects/links where practical.
- [ ] Propose and implement a clear wiki home page and information architecture for onboarding, development, operations, product/project context, and historical/reference material.
- [ ] Update developer-contribution and Docker/setup pages so they align with the current branches, tooling, verification commands, and canonical contributor documentation.
- [ ] Remove or clearly mark obsolete workflows, branch names, tools, and team processes; do not leave stale pages as the default path for new contributors.
- [ ] Repair or replace broken, redirected, and duplicate links across the wiki, repository documentation, issue templates, and onboarding materials.
- [ ] Decide which content belongs in version-controlled repository documentation versus the wiki, then migrate or cross-link it without creating competing sources of truth.
- [ ] Add lightweight page ownership and review-date conventions for high-value pages.
- [ ] Validate the reorganized wiki through a new-contributor navigation pass and gather maintainer review before retiring material.

### Additional Information

Related work: #748 modernizes repository contributor documentation. Coordinate the two so there is one canonical source for each topic and no circular or stale wiki links.

Preserve useful historical context, but distinguish it clearly from current operating guidance. This task should not silently delete pages before their replacement or archival destination is confirmed.

Start by inventorying every project wiki page and reading the current developer-contribution and Docker/setup pages. Compare repository documentation with related issue #748, then map canonical destinations, ownership, and review dates before changing links or retiring content. Done means maintainers approve a navigable wiki, updated contributor guidance, repaired links, and confirmed archival or migration destinations.

Written by the indexing model from the issue text.