Move everything else to ghidra/ directory

The only stuff left in delink/ was also for using with Ghidra, so we may
as well also put it in ghidra/.

documentation/gettingstarted.md

@@ -112,7 +112,7 @@ object files for objdiff.
 
 ### Producing Object Files
 Close all of your Ghidra windows and open a Unix-style shell (e.g. Git Bash if
-on Windows) in the decompilation repository's `delink/` directory.  The
+on Windows) in the decompilation repository's `ghidra/` directory.  The
 `delink.sh` script is our automated tool for extracting all the object files
 that have been identified so far.  Invoke it with three arguments:
 
@@ -214,12 +214,12 @@ request to merge it back into the online copy.
 ## Contributing to Delinking
 Getting the JSRF binary delinked is just as important as decompiling the
 resulting object files, but takes a bit more investment.  The concrete task of
-a delinking contributor is to populate `symboltable.tsv` in the `ghidra/`
-directory and `objects.csv` in the `delink/` directory, which together enable
-consistent delinking of object files.  The former lists symbols at different
-addresses through the whole executable, while the latter lists the address
-ranges that have been identified as separable objects.  Both of these things
-are figured out by combing over the whole executable in Ghidra.
+a delinking contributor is to populate `symboltable.tsv` and `objects.csv` in
+the `ghidra/` directory, which together enable consistent delinking of object
+files.  The former lists symbols at different addresses through the whole
+executable, while the latter lists the address ranges that have been identified
+as separable objects.  Both of these things are figured out by combing over the
+whole executable in Ghidra.
 
 
 ### Updating `symboltable.tsv`