Amanoba shipped steadier lesson rules, a refreshed memory game, and a stronger design foundation
This week focused on learner-facing stability: clearer quiz completion rules, a more consistent memory game experience, and a shared UI runtime for future course surfaces.
Lesson completion now follows the course quiz policy
Lesson pages now read the active course-level quiz policy when deciding whether a learner can mark a lesson complete. That makes the on-screen requirement match the real course rule, including question count and maximum wrong-answer limits where those rules are configured.
For learners, the practical result is less ambiguity: if a quiz is required, the lesson page keeps the quiz action visible, blocks premature completion, and explains the requirement in clearer product language.
The memory game moved onto the refreshed Amanoba UI foundation
The Memory Match game now uses the same Mantine-based control and card primitives as the refreshed Amanoba interface. Difficulty choices, stats cards, pause and restart actions, and the completion dialog now sit on a more consistent UI layer.
Rewards, challenge completion, final score, moves, and time remain part of the game flow, but the surface is cleaner and more aligned with the rest of the learner experience.
A shared runtime prepares more learner screens for the new design system
Amanoba now has a Mantine runtime provider wired into the localized app layout, with a product theme, color-scheme handling, modals, and notifications available across locale routes.
This is mostly foundation work, but it matters to learners because it lets future course, practice, and account screens move toward one consistent interaction model instead of each area carrying its own one-off controls.
Product updates are easier to publish and read
The public blog and news surfaces continue to be backed by the same content source, so weekly updates can appear consistently at both the blog route and the news alias.
The release-note archive also moved into a published wiki workflow, making it easier to keep public-facing release history separated from internal implementation notes.