Document the executable and APT hook as symlinks into the repository\ncheckout. This keeps development changes immediately available at the\ninstalled paths.\n\nKeep the runtime configuration as an installed copy so local settings remain\nindependent from the checkout. Explain the expected paths and the need to\nupdate the APT executable path when choosing different locations.
Document installation, APT protocol handling, dataset selection, recursive
snapshots, naming fields, package shortening, retention chains, and every
runtime configuration parameter.
Explain the relationship with the existing Pre-Invoke stop-gap and make the
expected callback frequency and direct-dpkg limitation explicit. Include
examples that show how affected package names appear in snapshot names.
