oc-surveying-codebaselisted

# Surveying-Codebase — Cold-start the memory of an onboarded project **Announce at the start (in pt-br):** "Usando surveying-codebase para popular a memória do projeto a partir da própria codebase." **Input:** the codebase of the project being onboarded — no run, no findings buffer. **This is the cold-start twin of `oc-distilling-learnings`.** Both route durable knowledge by blast-radius into the native memory model (project-root `MEMORY.md` / nested `AGENTS.md`-or-`CLAUDE.md` / `kaizen.md`). The ONLY difference is the SOURCE: distilling reads a run's transient findings buffer; surveying reads the **codebase itself**. The routing machine — durability test, blast-radius classes, destinations, retire-on-promote — is identical and is **reused, never re-implemented**: invoke `skill({ name: "oc-distilling-learnings" })` to read the full routing rules. There is no separate learnings store. --- ## When to use - A legacy/existing project enters the harness with no accumulated memory. - `build`'s **Phase 0** reads the native durable index (project-root `MEMORY.md`, root `AGENTS.md`/`CLAUDE.md` router) and finds the memory cold/empty on a non-trivial project. - Manually requested by the operator. - **Re-run** when the codebase changes substantially (new subsystem, big refactor). **One-time / on-demand — not a per-run step.** When NOT to use: a fresh/empty project (nothing durable to extract yet) → just set up the structure (root router table + nested folder stubs); there is noth