Problem Solving & Design B

The domain model is cleanly separated, well-typed, and covers all the brief's core scenarios including age-zero and boundary cases, with a comprehensive test suite verifying each path.

• +Domain logic lives entirely in domain.ts with no DOM dependency, making it independently testable and reusable — the current year is injected rather than read from Date().
• +The YEAR_THRESHOLD constant makes the year-vs-age disambiguation rule explicit and named rather than a magic number buried in a condition.
• +The test suite covers edge cases including age zero, the 149 boundary, future birth years, and placeholder substitution across the full message pool.
• -The fun message pool cycles deterministically by age modulo pool length, so entering the same age always yields the same message — there is no randomness or variation on repeated use.

Completeness C

Core candle-planning features are fully implemented, but the measured gaps around failure handling, error surfacing, empty states, and loading states are contradicted by the actual code, which does implement all four.

• +The empty state renders a full illustrated cake scene with a descriptive prompt when the input is blank, giving users clear guidance before they type anything.
• +A skeleton loading screen with animated shimmer placeholders appears on boot before the first result renders, giving users a visible pending indication.
• +Invalid input triggers both an inline error message and a visible error card, so the user always sees a reason when their entry is rejected.
• +The analyze function wraps all interpretation logic and returns a typed discriminated union, so every failure path produces a structured reason rather than throwing.
• -The birthday message is deterministic per age (age % pool length), so the same age always produces the same message — it does not change each time as the brief asks.
• -The input field has no focus styling beyond the global :focus-visible rule, and there is no hover or active state defined for it, leaving interaction feedback minimal.
• -

Technical Craft B

The submission demonstrates strong craft: CSS custom properties define a complete shared visual system, CSS-only flame animations respect prefers-reduced-motion, and ARIA attributes are applied thoughtfully throughout.

• +All colours, spacing tokens, and font stacks are defined as CSS custom properties in :root with a full dark-mode override block, forming a consistent shared visual system.
• +A prefers-reduced-motion media query disables all animations and transitions site-wide, respecting user accessibility preferences.
• +The result region uses aria-live and aria-busy so screen readers are notified of dynamic content updates without requiring focus movement.
• +The :focus-visible rule provides a high-contrast 3px outline using the --focus token, ensuring keyboard navigation is visibly indicated without affecting mouse users.
• -The responsive breakpoint only adjusts padding and numeral candle dimensions at 560px; there is no layout reflow for narrow screens such as stacking or font-size changes below that width.