write-wiki

Authors and maintains a team-facing project wiki / knowledge base for contributors and maintainers: architecture overviews, how-tos, runbooks, onboarding guides, and FAQ. Each page type gets its own skeleton: - Architecture overview — components, flows, why it's shaped this way (links ADRs, never restates them) - How-to — one task, exact commands, verification at the end - Runbook — symptom → diagnosis → remediation → escalation, written for 3 a.m. - Onboarding — day-one to first-PR path - FAQ — real questions actually asked Sources accurate content from map-specs and map-code artifacts when present; every code claim carries a pointer. Explanation and procedure — the specs remain the law.