Work log: Textorium — March 16, 2026
What shipped today
Two big housekeeping items: closing v1.5 and establishing a proper release history on GitHub.
Issue #13 (dynamic email signature with latest blog post) was closed as won’t-fix — it’s a polymathic-h concern, not a Textorium feature. This had been stalled in needs-clarification since March 12, blocking the v1.5 milestone. With it closed, v1.5 is now fully resolved at 18/18 issues.
The project had no GitHub releases or tags despite three App Store submissions. We created retroactive releases for v1.0.0 (initial launch), v1.0.1 (critical frontmatter corruption fix), and v1.0.2 (performance and polish), each tagged to the correct commit. Then we prepped v1.0.3 with a version bump, but an accidental version entry in App Store Connect forced a bump to v1.0.4 (build 5). The release notes cover the error-surfacing initiative: seven silent failure fixes, multi-format date parsing, a main-thread blocking fix, and a timer leak fix. v1.0.4 was archived, uploaded, and submitted to App Review.
Completed
- #13 — Add dynamic email signature with latest blog post (closed as won’t-fix, moved to polymathic-h)
- GitHub releases created: v1.0.0, v1.0.1, v1.0.2, v1.0.3, v1.0.4
- v1.0.4 submitted to App Store Review
Release progress
v1.5: 18/18 closed. Milestone complete. Ready to close formally.
Carry-over
- v1.5 milestone — needs formal closure via
/milestone close v1.5 - App Store review — v1.0.4 is pending Apple review
- Marketing site visual QA — still hasn’t had a production browser check (dark mode, 404, OG tags, blog section)
Risks
- The old root-level
Textorium.xcodeproj(pre-monorepo) was accidentally modified by areplace_allduring the version bump. Reverted in this session, but it’s a landmine — future version bumps should targetmacos/Textorium.xcodeprojspecifically.
Flags and watch-outs
- App Store Connect created the version as 1.0.4 instead of 1.0.3 due to a UI mistake. Both v1.0.3 and v1.0.4 GitHub releases exist — v1.0.3 was never submitted, v1.0.4 is the real App Store version.
- The board is now completely empty — zero open issues.
/scoutis the next productive step to fill the backlog.
Next session
- Check App Store review status for v1.0.4.
/milestone close v1.5to formally close the milestone.- Visual QA of textorium.app in production — browser check for dark mode, 404, OG tags, blog section, focus styles.
- Run
/scoutto discover new issues and fill the backlog for the next development cycle.
Why customer tools are organized wrong
This article reveals a fundamental flaw in how customer support tools are designed—organizing by interaction type instead of by customer—and explains why this fragmentation wastes time and obscures the full picture you need to help users effectively.
Infrastructure shapes thought
The tools you build determine what kinds of thinking become possible. On infrastructure, friction, and building deliberately for thought rather than just throughput.
Server-side dashboard architecture: Why moving data fetching off the browser changes everything
How choosing server-side rendering solved security, CORS, and credential management problems I didn't know I had.
The work of being available now
A book on AI, judgment, and staying human at work.
The practice of work in progress
Practical essays on how work actually gets done.
AI agents need org charts, not pipelines
Every agent framework organizes around tasks. The agencies that actually work organize around competencies. The AI community is about to rediscover this the hard way.
The delegation problem nobody talks about
When your automated systems start finding real bugs instead of formatting issues, delegation has crossed a line most managers never see coming.
What your systems won't tell you
The most dangerous gap in any organization isn't between what you know and what you don't. It's between what your systems know and what they're willing to say.