Leader 1.14.2: an empty __init__.py is not a failure

Leader 1.14.2 (includes 1.14.1 and 1.14.0)

Highlights

• An empty file can be a right answer: a build used to report a failure for every file the model left empty, including the ones
  that are correct that way (a Python __init__.py, a .gitkeep, py.typed, the requirements file of a project with no
  dependencies). It now does for those what it should: nothing.

Fixes

• build: an empty init.py is not a failed answer (5ecfbb0)

1.14.1

Highlights

• Checked against a real build: a build of a small project with Claude Haiku (13 files, $0.03, under 3 minutes) did what the
  1.14.0 notes promise: it named its riskiest requirement, deferred the one SPEC.md left open and said why, ended ⚠ built · 3/4 requirements have a test instead of ✓, and left a .leader/ folder with nothing of the project in it. Two details came out
  of it and are fixed here: the plan review no longer calls a test that uses a fake or a temporary directory a "stand-in", and the
  builder's own wiring check is recorded under its name.

Fixes

• build: tests are not stand-ins, name the wiring check (1ff9203)

Verify: see packaging/README.md (every file has a detached signature from the Leader Releases key; SHA256SUMS is signed).