Plateau With Accessiblity, Pre /tsugi/lms removal

This tag includes a large fraction of accessibility improvements that need a bit more time to consider solid. But it is a plateau before the /tsugi/lms folder is removed. As history, the /tsugi/lms was introduced in December 2025 as a way to collect and build features like Pages and Announcements. But then once tsugi-php was merged into tsugi, the /tsugi/lms functionality was rebuilt in /lib/src/Controllers as controllers are a more elegant way to capture a Tsugi "tool" and are more unit testable. As of late February 2026, there should no longer be any functionality used in production tsugi systems and the /tsugi/lms should be ablt to be removed. This plateau will likely be the last with /tsugi/lms.

Pre-Accessibility Plateau

We are about to start work on accessibiltiy - this is a safe place to come back to and to compare in case things get weird.

Post Badge Innovations (solid)

This is a pretty safe jump-back point - it ran all of the 4E web sites for a while with no issues.

Post Lumen Removal - Plateau

This is code post lumen removal that seems solid and ran in production for a while. A nice safe jump back tag.

Pre Lumen Removal

This tag will be before we merge the Lumen removal PR

Before Merging koseu-php into tsugi repo

The koseu-php is being merged into the tsugi repo at the /tsugi/koseu path. After this we won't separately release koseu a a packagist artifact unless a need arises to do so.

Before Removing PostgreSQL Support

This is a tag to come back to in case the PostgreSQL code removal removal has issues. Note that the previous tag just made it so the routines for PostgreSQL and SQLite returned false all the time. After this the actual code to partially support PostgreSQL will be removed.

Pre PHPStan

This is a safe place to go back to before the PHPStan fixes from Sam and Matt.

Pre Dependency Advance

We got a dependabot notice about a symfony security bug so decided to allow for a small dependency advance mid-winter. Taking this tag in case we need to run rapidly backwards.

Pre PostgreSQL Removal

Many year ago I tried to make the code portable between PostgreSQL and MySQL. It never really worked. Now that I am using AI to work on the code base - it is confused and tries to generate code that works with both. I want to take it out because it never worked and adds unnecessary complexity. So this tag is a snapshot before that removal happens in case we need to track back.