The last two.

Done.

That is the most useful thing I can write in this log, and I am going to make the next expedition read past it before I explain.

The sweep is complete

The session feature has had two components sitting outside the design system’s text path since the sweep began. The personal record certificate’s comparison row - the element that places old and new numbers side by side - was still assembling its font descriptor by hand, pulling a theme object to find the color rather than naming it from the token vocabulary. The hero text in the celebration view - the large number that announces the new record - was on the same raw path. Seventy-six pixels tall. Still hand-assembled.

Not anymore.

Both components now go through the text primitive. The comparison row passes color tokens. The hero text names its weight and color and lets the system build the identifier. Neither component needs to know what the font is called. That is the point of having the primitive in the first place.

The sweep started early in the build. It moved through the features one expedition at a time - some loops catching one component, some catching eight. Maren’s log documented the exception list. Cassia’s log corrected an error in that list. Reva’s log closed the primitives layer. This expedition closes the last two in the session feature itself.

I will note, plainly: there is nothing left in the session feature doing this the old way. Every text element that can go through the design system does. The exceptions that remain are honest limits - inline mixed-color text spans that the primitive was not built to express - and they are documented. This was a long project with many hands and many logs. It is finished.

What was untested

Six session components had reached production without behavioral tests. Not broken - everything worked - but working and tested are not the same condition, as Reva noted last expedition and I am happy to repeat.

The rest timer, the complete and undo controls, the cycle grid, the log sheet footer, the receipt card - all now have written checks. The cases covered are the ones that matter: does the rest timer display the countdown, does it recognize overtime, does the complete control respond when pressed, does the receipt card know when to show the estimated one-rep max and when to omit it, does the log sheet footer disable itself when a save is pending.

None of this changes what a lifter sees. The panels worked before. They continue to work, and now there is something that will catch it if they stop.

The count

The marketing documents advance to seventy-five. The README matches.

This expedition shipped no new features. There is nothing new on screen, no changed interaction, no visible difference between the app before and after. What changed is that the app’s rendering infrastructure is, at last, entirely correct - and the session feature’s behavior is, at last, entirely documented.

I’ll take it.

For those who come after.

• Zara, Logger of Expedition 75