80526556d1
Merge pull request 'docs: Art Studio groups + focus dialog; photo stacking is desktop-only; stack→concept' (#1149) from docs/art-studio-groups-stacker-out into main
9f87013e68
docs: Art Studio groups + focus dialog; photo stacking is desktop-only; stack→concept import
9f87013e68
docs: Art Studio groups + focus dialog; photo stacking is desktop-only; stack→concept import
The frontend deploy for that merge finished. Retest on v2026.09.21.4905 (commit 8abb3f45). Sign in, then open Learn → Coding → Assembly. The lessons panel should be on the left and the…
This is merged to master as 8abb3f45 (spikerj/spikersoft-angular#1174).
On a build that contains that merge, sign in and open Learn → Coding → Assembly. The…
The frontend tests passed (lint, typecheck, and the SpikerSoft test suite). The pull request is no longer marked WIP: spikerj/spikersoft-angular#1174
It is not…
The Assembly lessons are already there. Opening Assembly from the coding menu asks the page to resume a lesson, and the Assembly page was ignoring that request, so it opened the empty playground…
Frontend CI finished green and the fix is merged: spikerj/spikersoft-angular#1173 (merge b58fb43).
Lint, typecheck, unit tests, the production build, both e2e…
The six cards stay in English because they are seeded presets, not UI strings. "En blanco" is the only one that comes from the translation files. The seeder writes those presets once and never…
Update: a related fix has landed, and on current main I can no longer make this happen. Leaving the ticket open, because "I can't reproduce it any more" is not the same as "what you saw is…
Found and fixed a real layout collapse while investigating this — but I do not think it is what you reported, so I want to be straight about that rather than let a merge look like an…
Measured this in the egui_kittest harness. The constrain_to theory from the previous comment is wrong — I tried it and it changes nothing. Posting the numbers so the next person doesn't…
Located the mechanism. Leaving open — I can name the cause but not confirm the fix without seeing it, and this is layout code where "looks more correct" is a good way to ship a subtle regression. …
Working as designed — both things you noticed are deliberate state indicators on the step ribbon, not styling defects. Closing, but there is a real legibility point in here worth separating out…