Cache the complete snapshot-name listing once per hook invocation instead\nof querying ZFS separately for every dataset and counter candidate. This\nremoves the repeated full-pool scan that becomes expensive when recursive\nsnapshot histories are large.\n\nCache the operation suffix as well and return an explicit success status\nfrom snapshot-name generation so collision retries are unambiguous. Ignore\nAPT configuration-only records because they do not represent package data\nchanges requiring a new pre-install snapshot.
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.
Provide a deployable configuration with the default retention limits,
important package expression, dataset selection behavior, and snapshot name
formatting parameters.
Expose explicit recursive roots for installations such as bpool and rpool,
while retaining property-based selection as the default behavior. Document
operation suffixes for installs, removals, upgrades, downgrades, and mixed
APT callbacks through configuration values.
Parse the APT package action protocol and classify records by operation.
Use the package list to determine important and trivial snapshot chains,
then generate collision-resistant names containing shortened package data.
Select ZFS datasets through the configured property or explicit roots.
Create recursive snapshots atomically, support dry-run output, and prune
old snapshots from the matching retention chain after success.
Preserve the original warning-oriented behavior by reporting snapshot and
retention failures without aborting the package operation.
Install the APT configuration fragment used to invoke the snapshot
helper before dpkg processes package files.
Request protocol version 3 and a dedicated information file descriptor so
the helper can classify package installations, upgrades, downgrades, and
removals without attempting to infer actions from the apt command line.
Define the Conventional Commits types currently used by the project.
Document the initial scope vocabulary for APT integration, hook wiring,
ZFS behavior, configuration, and documentation.
Require every future commit to carry a scope and keep verbose commit body
lines within the repository's 72-character limit. Require new types and
scopes to be documented before they are used.
