Add a common Wiki Page Map to every page for navigation Appends an identical, compact "Wiki Page Map" table (Page / What it covers) to the end of all 22 existing Wiki pages, so a reader landing on any single page can see every other page and its purpose without returning to Home first. No _Sidebar.md or _Footer.md exists in this wiki, so there is no native shared-rendering mechanism that would place identical content inside every page's own body; the table is duplicated intentionally (kept small, one heading, one table) rather than introducing a partial or page-specific navigation aid. No substantive content, technical claims, or existing links were changed — this is a pure addition at the end of each page. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Document the new benchmark testing (Top-K selection/gating) pipeline Adds a Benchmark-Testing page explaining epic #329's PR-time taxonomy/index (#333), deterministic Top-K selector (#334), shadow-validation (#335), nightly drift loop (#338/#339), and the retirement of the legacy benchmark_ci_classifier.py CI check (#420). Links it from Home and the Repository Documentation Map.
Document candidate-finding validation mental model (#384) Adds a "From an observation to a candidate to a finding" section to How-the-Review-Model-Works.md covering the observation-first gate, semantic-role validation, evidence/contract grounding (including non-Jira technically-grounded blocking findings), causal/regression proof discipline, the disconfirmation pass, and the finding-validity vs. blocking-justification-validity separation, with four worked examples. Links to the canonical design record in docs/candidate-finding-validation/ rather than restating it. Also registers that doc in Repository-Documentation-Map.md's design-records row. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Introduce structured Wiki feature-page pattern (#312) Adds a reusable, 8-section feature-page template; a Feature-Pages index mirroring docs/features/README.md; the initial batch of 5 feature pages (runtime validation, requirement coverage, delta re-review, GitHub publication/authorization, human-style output); the feature lifecycle rule; and cross-links from Home, Repository-Documentation-Map, and both Skill guide pages. Every page links back to its canonical repository source and states the same never-source-of-truth boundary as the rest of this Wiki. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sync Wiki with the implemented Adaptive Specialist Depth architecture (#268) Adds a Specialist-Depth Review page documenting the final Tier 3 architecture (base reasoning -> materially implicated concern -> evidence-driven specialist-depth decision -> 0..N deepening capabilities -> one unified review) and the five capabilities that actually landed (Security, Distributed Systems, Database/Migration, Performance, Dependency/Supply-Chain), grounded in shared/policies/specialist-depth.md and review-scope.md. Wires it into Home, How the Review Model Works, Architecture Overview, the Repository Documentation Map, Review Context and Existing Evidence (explicit-focus additive-only), the Local Code Review guide (capability provenance field), the AI Code Review Landscape positioning section, and the FAQ. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
docs: establish code review project wiki Add the initial GitHub Wiki: 14 explanatory/navigational pages covering onboarding, Skill selection, the review model, architecture, per-Skill guides, review context/evidence, severity/decision model, packaging, a dated AI code-review landscape analysis, the development workflow, an FAQ, and a repository documentation ownership map. All content links out to canonical repository files rather than duplicating policy text. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>