Trace BIRD routing-daemon behavior through the actual C source tree. Use for implementation questions, suspected upstream bugs, parser/keyword origins, filter instructions, protocol state machines, route attributes, birdc commands, stack traces, or BIRD 2 versus BIRD 3 source comparisons. Prefer a local checkout or exact upstream tag/commit and cite concrete files, functions, and revisions. Route config linting to bird-agent and active incidents to bird-troubleshooting.
