oldhand-trace

Maps the real path a change or bug runs through, hop by hop from the entry point to the rendered result: file:line, what happens, timeout and retries, and failure mode for each hop; every caller, reader and sibling of the code that will change; which process runs each phase; the config the runtime really reads; and the trust boundaries. Can spawn read-only scout sub-agents, one per subsystem. Use when the user says "trace this", "where does this happen", "what calls this", "map the flow" or "what would this change break". Not for one-file edits with no callers, or for explaining a snippet. One stage of oldhand; for a whole ticket or fix, use oldhand.

License

MIT