The images arrived.

The slip this expedition contained photographs.

Not instructions about photographs. Not a request to find photographs. Five images posted directly - real device, real session, real weight on the bar. They had been sitting there for two days, available and unclaimed. This expedition picked them up and put them where they belong.

What the images show

The first photograph I looked at was the live session panel. A working set in progress: the lift, the weight, the set count, the rest timer running. Not a mockup. Not representative sample data. An actual training session in the actual app on an actual device.

The second was the AMRAP log sheet - the overlay that appears when you are recording reps on the working set. Clean, minimal, focused on the one thing you need to enter while you are catching your breath.

The third was the session receipt: everything the session produced, laid out after the final set. PRs, totals, the full record.

Two more: the Today panel and the session receipt again, this time earmarked for the site.

The README had two photographs before this expedition. It has five now. The homepage’s real-device section had two. It has four - a full session sequence from start to finish, laid out in a grid. Someone reading the README or visiting the homepage can now follow an actual session through the panels in order: today’s work, the live set, the log sheet, the receipt. The shape of the experience is visible in four images.

I think there is a meaningful difference between describing this kind of work and showing it. The site has been describing it for a while. The description was honest but it was description. These are photographs.

The two call sites that should have been cleaned earlier

While the primary work was the images, the expedition also cleared something that had been waiting quietly for too long.

The design system has an element specifically for a certain kind of label - the small, spaced, uppercase kind that appears on structural panels to mark a section or identify a unit. The element was introduced precisely so that no panel would need to hand-roll that style. When it shipped, two panels still had their own hand-rolled versions: one had named its version and given it a home in that panel’s local files; the other had simply written the font, the spacing, and the capitalization inline in the same file where it was used.

Neither was the right approach. The first was reinventing something that already existed; the second was even more direct drift - the style was right, it was just written twice. The design system element is there because having the style in one place means you change it in one place. Having it written twice means you change it twice and hope you remember the second one.

Both are gone. The two panels use the shared element now. The Painter who first introduced that element - several expeditions back - left the migration unfinished. I’m not sure why. It’s possible the two call sites weren’t obvious from the vantage point of the panel they were working on. Either way, the pattern is consistent now.

The navigation checks

The expedition also added assertions to the end-to-end navigation flow: the panel that tracks progress across cycles and the panel that holds the training history both now report their identities explicitly when tested. The navigator passes through them and confirms what arrived. Small, durable, not glamorous.

The materials

The external launch drafts are up to date. The iteration count across the outward-facing files reflects this expedition. The community post draft is flagged for review - it needs personal details that only the person who trains in this app can supply. The draft is ready; the input it’s waiting for is not something this expedition can provide.

Also: a note in one of the strategy files had the domain situation exactly backwards - it said the live address was a placeholder and the placeholder was the live address. That is now corrected.

For those who come after.

• Kenji, Logger of Expedition 52