Search existing upstream issues before opening a reproducible report.
Search first. Do not share credentials, private targets or unredacted logs in a public issue.
Use this question-first map to decide which REA reference to open next. Each row distinguishes an upstream source from an independent explanation and notes a conclusion the resource alone cannot establish.
I maintain the independent guide at reverseengineeringanything.com. The REA toolkit and official documentation belong to their upstream authors at github.com/morluto/rea. This list is an educational resource, not a hosted analysis service or a report of fresh software tests.
Start with the upstream overview, check the current installation and client documents, then use a task-specific reference. Version differences should be resolved against current upstream documentation. List text and curation prepared with AI assistance.