Draw the feature graphic, and fill the 7-inch tablet slot

[andiwand]

Two listing assets the release never touched, both of them still pictures of the app
as it looked before the 4.14 redesign. Found checking the 4.16.0 listing in the
console.

The 7" tablet slot held five pictures of the old app

sevenInchScreenshots was deliberately left out of the staging table:

# `sevenInchScreenshots` is deliberately not among them: nothing is made for a
# 7" tablet in particular, and play falls back to the phone pictures there.

Play does fall back - where the slot is empty. This one was not, so it went on
showing the pre-4.14 landing screen through every release that rewrote the other two
slots.

The tablet's captures go into both tablet slots now. A 1600x2560 picture is inside
the 7" slot's limits as well as the 10" one's, so nothing new is photographed and the
emulator hour does not move - DIRECTORIES maps a device to a tuple of slots instead
of one, and stage() copies into each. Supply calls clear_screenshots per slot
before uploading, so the five old pictures are deleted rather than left underneath.

The feature graphic is drawn now, not committed

fastlane/metadata/android/en-US/images/featureGraphic.png was the one listing asset
the release uploaded nothing over - checked in, 1024x500, the only en-US one, and
served by Play in all fifteen storefronts. It showed the old UI inside mockup phones.

It is drawn out of the same parts a screenshot is framed from - the ground, the
dashed line, the drawn Pixel and the odt/ods/odp tabs - laid out across the canvas
instead of down. Its capture is the first screenshot's phone-01-recents, and its
headline that screen's, so there is no second line of copy to write and none to
translate fifteen times. One per locale, where the store had one English picture
for all of them.

That is the point of drawing it rather than replacing it. A picture of the app is
worth what the build it came off is worth, and a listing asset nothing regenerates is
one nobody notices going stale - this one managed three releases. To look at it:

ODR_SCREENSHOT_LANGUAGES=en-US bundle exec fastlane android screenshots
# fastlane/framed/en-US/featureGraphic.png

or the framed-phone artifact of any release run, dry run included.

Around it

• store_screenshots.py checks it the way it checks a screenshot - 1024x500 exactly,
  present in every locale, or the set is not a set - and stages it to
  <locale>/images/featureGraphic.png, which is where supply reads one from.
• skip_upload_images becomes !captured, so it rides the rule the screenshots
  already ride: no capture, nothing uploaded, the store keeps what it has. A wedged
  emulator still costs the release its pictures and nothing else.
• The launcher icon is not staged, and supply does not touch what it cannot find, so
  it stays where it is. Still its own job.
• The workflow needs no change: the graphic lands in fastlane/framed/<locale>/ and
  rides the artifacts that are already there.

How it was checked

• A full set built out of the local en-US capture: 285 files staged into the right
  directories, phoneScreenshots / tenInchScreenshots / sevenInchScreenshots and
  the graphic beside them.
• Both new failure modes reported rather than shipped: de-DE: no featureGraphic.png, fr-FR: no tablet 03-sheet.
• All fifteen headlines rendered. Every one fits its column and clears the phone,
  Devanagari and CJK included.
• The gallery screenshots come out unchanged - headline_middle defaults to the
  middle of the canvas, which is where they already were.

🤖 Generated with Claude Code