document-codelisted

# Document Code Read undocumented functions and write summaries back to Loom. Every summary you store eliminates a future file read. ## Steps ### 1. Find documentation gaps Call `suggest_questions(limit=7)` — look for `MISSING_SUMMARY` type entries. These are hot functions (many callers) with no cached summary. Call `god_nodes(limit=20)` — most-called functions. Cross-reference with search results to find which ones have null summaries. If the user specified a keyword/module argument: ``` search_code("<argument>", limit=20) ``` Filter results where `summary` is null. ### 2. Prioritize Work in this order: 1. Hot functions with no summary (`god_nodes` + null summary) 2. `suggest_questions` `missing_summary` results 3. Functions with `summary_stale: true` (source changed, summary outdated) 4. Any function you have to read for other reasons ### 3. For each undocumented function First try `get_context(node_id)` — often enough to write a good summary without reading source: - Signature tells you inputs/outputs - Callers tell you how it's used - Callees tell you what it relies on If `get_context` is insufficient, read the source: ``` Read("<path>", offset=<start_line>, limit=<end_line - start_line + 10>) ``` ### 4. Write the summary ``` store_understanding( node_id="<exact node_id>", summary="<one sentence: what it does AND why it exists>" ) ``` Quality check: - Under 120 characters - Describes WHAT + WHY (not HOW) - Includes key behavior: return value, side ef