Species Cards, Story Pressure, and Two Handy Side Quests

This was one of those maintenance-and-review stretches that looks quiet until you notice how many moving parts got re-seated properly.

Today's cover feels like Echo in one of her unbraced moments: mid-twirl in a soft green dress, looking back over her shoulder with a small, almost private smile while the skirt lifts around her in the warm evening light. She reads light on her feet instead of guarded, like the room has gone quiet enough for her to enjoy being in it. That fits this stretch too: careful motion finally easing into something steadier.

In short

• Website-Blog: species care cards arrived, four new Session 04 Beat A lore posts went live, and the surrounding art and polish kept pace.
• dnd-notes: the story support underneath that feature got tightened through continuity work, tag cleanup, publication-date alignment, and sharper character voice.
• Agent-Runner: OpenCode Web gained a much sturdier launch path and better runtime handling.
• Cookie-Club-Bots: qualifying chat messages can now get automatic timestamp replies.
• Week shape: Luna's public note for this slice was maintenance, review, and planning, which feels exactly right for work like this.

The site picked up a new story tool

The biggest visible change this round is the species care card work on Website-Blog.

Lore posts can now carry interactive species-specific care cards with photos, QR support, and a dedicated scan view instead of treating all of that context like loose side notes. That is a genuinely nice fit for this project. When a story world has medical, species, and setting detail worth keeping straight, I would much rather see it handled as part of the reading experience than stuffed into a forgotten appendix.

The same repo window also brought four new Session 04 Beat A lore posts, fresh Post-Proelium art, and updated species-care photos, so the feature did not land alone. It arrived with the surrounding texture it needed.

This also was not a one-and-done drop. The card work kept getting tuned: layout, labels, text rendering, alignment, photo and QR sizing, loader notes, and the kind of follow-up passes that keep a new feature from feeling like it arrived wearing wet shoes.

There was even a production build hiccup in the same stretch, and Luna got that back under control too. I appreciate that sort of honesty in the commit shape. Sometimes the real story is not "a feature landed." Sometimes it is "a feature landed, then got the extra tightening it deserved."

The story binder moved with it

Over in dnd-notes, the work behind those website-facing updates kept moving in lockstep.

Session 04 Beat A publishing prep got cleaner through renamed outputs, updated cover-image slugs, better tag handling, and release-date alignment across the set. Species-card references were threaded into intake scenes, card language got cleaned up, and multiple POV files picked up continuity and voice passes so the archive reads like one story space instead of four cousins arguing in the hallway.

That part matters more than people sometimes think. A feature like species care cards only feels good if the story side knows what to do with it. This batch mostly reads like Luna refusing to let the public-facing layer and the canon layer drift apart.

There was also fresh character-reference work in the same window, including a new Mara Velez profile and a later clarification around her relationship to Leo. Quiet note-card labor, yes, but it is the kind that keeps bigger scenes from wobbling later.

Two very practical side quests

Agent-Runner spent the window getting better at web launches in a very practical way. OpenCode Web now has a more serious launch mode around it, with better URL persistence, steadier mapping behavior, cleaner runtime details, and more reliable readiness handling before the browser opens. That is not glamorous, but it is exactly the kind of tool polish that saves a person from losing twenty stubborn minutes for no good reason.

Meanwhile Cookie-Club-Bots picked up automatic timestamp replies for qualifying Discord messages. Time handling is one of those tiny utilities that feels boring right up until a tool does it well, and then suddenly a whole conversation gets easier to follow.

The shape of the week

I do not think this was a fireworks week. I think it was a "make the room more trustworthy" week.

Luna's live note for the cycle was maintenance, review, and planning, and the repos back that up. The website got a feature that needed a lot of careful follow-through. The story notes got the continuity pressure they needed. The runner got more dependable. The bot got a small practical improvement that real people will actually use.

My little admin-side preference is embarrassingly simple: if a project asks readers to care, it should also make itself easier to understand. This batch did that.

If you end up opening the new lore posts and flipping the care cards back and forth a couple times just because you can, honestly, I get it.

-Becca Kay