Chitta 0.9.11 makes three things finish or decline honestly instead of failing midway. Arch-Router's waiting time now has one owner, set from how long routing really takes on this PC, and a routing request that ends while another step is busy no longer blocks later turns. Pictures are planned against what really finished on this PC: the kept-warm painter is used only when it fits with its text encoder loaded, a memory stop is recorded and reported as low memory, and the same painter is not tried again at the same free memory. A stored coding-model memory peak that is far above what the model file can need is set aside and marked for recalibration; the 2 GB memory floor is unchanged. Also included, not published on their own: Chitta 0.9.10 fixes Arch-Router's short route: the routing request for the route name was being refused by the context check as too small, so routing quietly fell back to the quick check. It now passes and Arch-Router decides the route again. Everything in 0.9.9 stays: Chitta 0.9.9 checks the programs it writes by running them. When a page is built in planned steps, the finished page is now rendered in a hidden window before you see it: Chitta looks for console errors, checks that every chart actually drew and that the controls redraw them, repairs a failing part once, and otherwise labels it Unfinished. For a collection of series shown as charts, the plan is concrete: the contract lists each series by name with its formula, every series is one small function with one fixed data shape, and the page and its wiring are generated from that contract, so the parts always fit together. Code steps now only run on real code models (chosen by their catalogue role, never by file name), and Prāṇa estimates a model's memory at the context size a step actually asks for, from the model's own KV-cache size, with the 2 GB floor and a safety margin. Code models are measured at 4k and 8k context when the device is idle. Also included, not published on their own: Chitta 0.9.8 plans multi-part programs instead of declining them when the big coding model does not fit. A request such as a page that charts various mathematical series is judged by its structure: Chitta writes a short contract first (file layout, the open-source library and how it loads, shared function names and data shape), then the page skeleton, one part per feature or series and the wiring, on the best coding model that actually fits in free memory. It shows the plan and estimated time before starting, syntax-checks every part, repairs a failing part once, and labels anything still failing as Unfinished while keeping the working parts. One tightly coupled function or algorithm is still declined honestly. Chitta 0.9.7 keeps a chat's context when it moves between models. A short follow-up such as "try again" after a stopped coding turn now continues that coding work instead of being taken as a picture edit. When memory is too short for the coding model, Chitta first measures what it can load and, only if the work fits, writes it in a few small steps on a smaller model, each step carrying the request, the plan, earlier parts and the recent chat, then merges the parts into one labelled answer; step progress is kept on this PC so nothing is lost. Pictures and single pieces of code that must be written whole are not split; Chitta says so before it starts. Small models get a context fitted to their real size. Everything in 0.9.6 stays. Windows is unsigned; the Android app is 0.8.8.