Merge branch 'cleanup/errors-deps'

* cleanup/errors-deps:
  apt/release: type the file-verification and armor errors
  new: type the scaffold validator errors
  debian: type the errors of the format primitives
  deps: add thiserror
  pull,package_info,ui,cli: report the pull flow via BuildView
  deps: trim the tokio feature set to the APIs in use
  deps: drop the lazy_static dependency
  data,apt/release,distro_info,new: replace lazy_static with LazyLock
  deps: drop the unused cmd_lib dependency

# Conflicts:
#	src/ui.rs

src/report.rs

@@ -68,10 +68,12 @@ pub struct BuildTarget<'a> {
 /// Observer of a running build: target identification, phases, status
 /// messages, progress and the final outcome.
 ///
-/// Implement this to observe the [`crate::build`] and [`crate::deb`] flows
-/// from any frontend. All events arrive in order from the build thread;
-/// long-lived views are expected to be `Send + Sync` because builds may run
-/// inside async tasks.
+/// Implement this to observe the [`crate::build`], [`crate::deb`] and
+/// [`crate::pull`] flows from any frontend. All events arrive in order from
+/// the build thread; long-lived views are expected to be `Send + Sync`
+/// because builds may run inside async tasks. The pull flow only emits the
+/// [`BuildView::message`], [`BuildView::progress`] and
+/// [`BuildView::progress`] events — no target, phases or outcome.
 pub trait BuildView: Send + Sync {
     /// The build target was identified; the events that follow belong to it
     /// (including the earliest subprocess output, e.g. a chroot download).