pactkit-tracelisted

# PactKit Trace Deep code analysis and execution path tracing via static analysis. ## When Invoked - **Plan Phase 1** (Archaeology): Trace existing logic before designing changes. - **Act Phase 1** (Precision Targeting): Confirm call sites before touching code. ## Protocol ### 1. Feature Discovery - Use `Grep` to locate entry points (API route, CLI arg, Event handler). - Map core files involved — don't read everything yet. ### 2. Call Graph Analysis - Run `visualize --mode call --entry <function_name>` to obtain call chains. - Read `docs/architecture/graphs/call_graph.mmd` to see all reachable functions. ### 3. Deep Tracing - Follow call chain file by file, recording data transformations. - Note how data structures change (e.g., `dict` -> `UserObj` -> `JSON`). #### Layered Output: Interface Summary vs Full Implementation | Module Role | Output Level | Content | |-------------|-------------|---------| | Target (to be modified) | Full implementation | Complete function bodies | | Related (dependency, not modified) | Interface summary | Signature + types + docstring only | **Interface Summary Extraction by Language:** - **Python**: `def name(params) -> ReturnType:` + docstring + `@decorator` annotations - **TypeScript**: `export function/interface/type` declarations + JSDoc comments - **Go**: Exported `func Name(params) ReturnType` + struct definitions + godoc comment Interface summary is produced on-the-fly during trace output — no separate files are generated (DRY: