diff --git a/README.md b/README.md
index ecf097d..7cb6cef 100644
--- a/README.md
+++ b/README.md
@@ -239,3 +239,76 @@ Independent API audit completed after the readiness pass:
 - Readiness issue: present on every repo
 - Required topics: present on every repo
 - Audit failures: 0
+
+## Detailed Wiki Pass: 2026-05-20
+
+Read each Gitea repository individually using the repository tree, mapped local project source where available, README files, and common manifest/build signals. Rewrote the wiki layer with project-specific evidence rather than generic stewardship text.
+
+### Pages Updated
+
+Every repo now has detailed content for:
+
+- `Home`
+- `Setup`
+- `Operations`
+- `Security`
+- `Releases`
+- `Provenance`
+- `Hardware` for hardware/firmware-oriented repos or `Architecture` for software/automation repos
+
+Every repo also now has:
+
+- `Project Inventory`
+
+### Detail Sources
+
+The wiki pass inspected:
+
+- Gitea repository description, visibility, default branch, language, and topics
+- Gitea repository file tree
+- mapped local source directories where available
+- README headings and summary content
+- `package.json`
+- `requirements*.txt`
+- `platformio.ini`
+- `CMakeLists.txt`
+- `Dockerfile`
+- `docker-compose*.yml`
+- Arduino `.ino` sketches
+
+### Content Added
+
+The generated wiki pages now include:
+
+- project purpose and classification
+- evidence reviewed
+- local source mapping, when known
+- setup signals and setup gaps
+- architecture or hardware interpretation
+- visible project file inventory
+- directory and file-type concentration
+- maintainer operations workflow
+- security risk profile
+- release gates
+- provenance requirements and unknowns
+
+Keeper decision: when a repo only contains stewardship files or placeholder content, the wiki says so directly. No fake setup commands, fake architecture, or fake release readiness were invented.
+
+### Safety Boundary
+
+Security-sensitive repositories were documented for authorized lab, defensive, research, and maintenance use only. The wiki pass did not add operational misuse instructions.
+
+### API Repair
+
+The first detailed wiki write used the wrong Gitea wiki content field and produced blank wiki file contents. This was detected by cloning a wiki repository directly and repaired by rerunning the pass with `content_base64`.
+
+### Verification
+
+Independent verification completed after the repair:
+
+- Repositories audited: 58
+- Required detailed wiki pages: present on every repo
+- `Project Inventory`: present on every repo
+- `Home` pages: non-empty and contain detailed evidence markers on every repo
+- `Project Inventory` pages: non-empty and contain file/build signal sections on every repo
+- Audit failures: 0