Make reference-household limitations visible beside results and keep results in view

The calculator accepts exact ages, care schedules, provider details, and up to six children, but its instant estimate maps them onto a small set of reference households. Differences are explained below the results; the headline can still say “Eligible” even when key inputs were ignored. The exact API can also be unavailable or older than the grid model, so it does not always resolve the mismatch.

Suggested interface changes:

• When entered inputs differ from the grid, put “Reference household qualifies” (or equivalent) beside the amount and show the material ignored inputs there.
• Keep the approximation status visible in the headline instead of relying on a note further down the page.
• Consider a sticky result summary or desktop inputs/results layout, so users can see results while changing inputs; preserve usable mobile flow.
• Explain what users can do when an exact calculation is unavailable or cannot replace the estimate due to model-version lag.

Acceptance: changing a child's age, care hours, activity status, provider details, or child count away from supported grid values must not leave a result that appears to describe the exact entered household. Verify responsive layout and that warnings remain visible alongside the headline.

Sources: src/components/CalculatorResults.tsx, src/components/Calculator.tsx, src/lib/dataLookup.ts.

Read src/components/CalculatorResults.tsx and src/components/Calculator.tsx first, then trace the grid and exact-lookup behavior in src/lib/dataLookup.ts. Verify that unsupported inputs visibly identify reference-household results beside the amount and that approximation warnings remain in the headline. Check desktop and mobile flows while changing child, care, provider, and household inputs.