• Tree inventoried with glob (gitignore/hidden off, .pc/ excluded) and read directory by directory: root files, benchmark/, example/, lib/, lib/src/, lib/src/data/dates/{patterns,symbols}/, test/, tool/. The directory named in the task is the only subdirectory, and .pc/ contains only quilt bookkeeping.
• Prescan result accounted for: the author check found 1 declared holder and no holder missing from debian/copyright, and a grep for Copyright|(c)|© over the whole tree (93 hits) shows every file notice reads the Dart project authors with years 2012-2024, plus the packager in debian/*. The single top-level LICENSE matches Files: *'s 2013, the Dart project authors (year drift only, not noteworthy).
• LICENSE and PATENTS read in full. PATENTS is Google's additional IP-rights (patent) grant for Dart: an extra permission, with no restriction on use or modification, so it needs no separate copyright stanza and does not make any file non-free.
• Generated files accounted for, none of them a missing-source problem: lib/date_symbol_data_local.dart, lib/date_time_patterns.dart and lib/number_symbols_data.dart are marked File generated from CLDR ver. 48 and are the form upstream maintains and edits by hand (their headers document the manual-edit convention); lib/src/data/dates/patterns/.json and .../symbols/.json are generated from exactly those .dart files by tool/generate_locale_data_files.dart, which is present, as lib/src/data/dates/README.txt states. lib/src/data/dates/locale_list.dart is likewise emitted by that tool. The CLDR-derived data therefore ships as editable Dart, not as an opaque blob.
• No built artefacts or binary-only files: every file in the tree is .dart, .json, .md, .yaml, .txt or plain-text; no .jar/.class/.so/.dll/.exe/.pyc, no minified JS/CSS, no images, fonts, sounds or PDFs, and no vendored copy of a library Debian already ships (test/fixnum_test.dart only imports package:fixnum as an upstream dev-dependency).
• debian/control read in full: debhelper-compat (= 14) with %: dh $@; apt-cache shows dh-sequence-single-binary is provided by debhelper 14.5, and debhelper's compat list confirms the single-binary add-on is the documented way to keep compat-14 behaviour explicit. Standards-Version 4.7.4 vs Policy 4.7.4.1 (policy tool) - same first two components, so current. Depends ${misc:Depends}, dart-clock, dart-meta, dart-path correspond to pubspec.yaml's dependencies (clock, meta, path).
• debian/tests/control (Tests: smoke, Depends: @, dart-sdk, Restrictions: allow-stderr) matches the .dsc's Testsuite: autopkgtest / Testsuite-Triggers: dart-sdk, and dart-sdk exists in the archive (3.13.4+dfsg1-6). The test installs the package's own tree at /usr/share/dart/packages/intl via debian/install, which is what the test's package_config.json points at.
• debian/rules read in full: the touch of installed directories uses @$${SOURCE_DATE_EPOCH}, i.e. the value the shell sees; man dpkg-buildpackage (SOURCE_DATE_EPOCH) confirms dpkg-buildpackage sets it from the latest changelog entry when it is not already defined, so touch -d @... is not reached with an empty value in a normal build. Directory mtimes in the tree are the 1970-era values the tarball carries, which is what the override exists to normalise.
• debian/changelog, source/format (3.0 (quilt), no debian/patches - nothing to review there), gbp.conf, upstream/metadata, install, docs, and the .dsc read; the changelog's weekday (Mon, 26 Oct 2026) matches the date, distribution is unstable, and the initial release closes #1152035.
• dart-meta 1.19.0-2 and dart-path 1.9.1-2 exist (same maintainer), and their versions satisfy pubspec's meta: ^1.3.0 and path: ^1.8.0 (apt-cache).
• uscan found the packaged version as the newest upstream release (upstream 0.20.3, packaged 0.20.3).

• dart-clock is in neither the unstable lists nor ftp-master's NEW queue as of 2026-10-26 (apt-cache), while the binary package Depends on it and the smoke test installs the package: if it is not accepted by then the autopkgtest cannot be installed. The name is consistent with the sibling dart-meta/dart-path naming, so this is most likely a package not yet in the lists, not a wrong name.
• debian/tests/smoke's generated package_config.json gives the intl library "languageVersion":"3.4" while pubspec.yaml requires sdk: ^3.9.0; whether any source in lib/ needs a language version above 3.4 (which would make the test fail to compile) cannot be checked without running dart, which this review cannot do.
• The executable bit on debian/tests/smoke and on nothing else: file modes are not visible through the tools available here; autopkgtest needs the script executable.

None.