rc-analyzelisted

# Deep Codebase Analysis Investigate the codebase to answer the user's analytical prompt — whether that is how something works, why a bug happens, or whether two parts of the system are consistent — then deliver a thorough, evidence-based report. This skill is read-only — it explains, traces, diagnoses, and assesses; it does not change code. It is standalone and stack-agnostic; it detects the stack and reasons in that stack's idioms. ## Code navigation (Serena) If the Serena MCP is available, prefer its symbolic tools over whole-file reads — they are LSP-accurate and token-efficient: - `get_symbols_overview` to grasp a file's structure before reading it; `find_symbol` (by name path, e.g. `Type/method`) to jump straight to a definition. - `find_referencing_symbols` to map every caller of a symbol before reasoning about impact. Fall back to Grep/Glob + Read when Serena is unavailable or for plain-text (non-symbol) searches. ## Required Inputs - The analytical prompt: the question or topic to investigate (e.g. "how does run shutdown work", "why does the daemon exit before flushing the journal", "is the locking around the run registry consistent or is there a race", "what is the impact of changing the event journal format", "where does config validation happen and is it consistent"). - Optional: a slug or scope (specific files/directories/packages) to focus the analysis. ## Resolving the `.rc` base directory RC supports monorepos, where more than one `.rc` directory can