> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/design/system/changelog.md). # Design system changelog ## 2026-10-15 The Toshi side handle and entry pill are shown only to school admins and head teachers; teachers, bursars, librarians, parents, site admins and every other role get no launcher (the panel and its other entry points stay). The pill shows only on dashboard and onboarding pages; on every other page the handle alone is the launcher, so the pill never covers list rows. The 80px collapse now follows whichever element really scrolls (the content area at 1280 and wider), and the phone drawer's Tab and Shift+Tab cycle through every visible control, including the items of an expanded group. The Toshi entry pill no longer moves to dodge list rows. It stays fixed, 24px from the right and 24px from the bottom, or 16px above a bottom `data-sticky-bar`. After the page scrolls more than 80px it collapses to a 44px circle: the K stays in the ring, the label hides, and the aria-label stays the same. It expands again at the top. The page keeps 100px of extra bottom padding while the pill is showing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://klassdocs.gitbook.io/klassapp-documentation/design/system/changelog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.