Assessment 03 · Navigation and release evidence

Attempt after lesson 10. Provisional 35–45 minutes. Six questions, two points each. Aim for 10/12 and correct questions 4 and 6 before the capstone handoff.

1. Why does the teaching package use hash routing? What host behavior must be configured for browser-history routes to survive a direct refresh?
2. A route matches /events/:eventId but no loaded record has that ID. What UI is required? How does this differ from an unmatched route and from loading?
3. After client navigation, what should you inspect besides the visible card? Explain the focus and title responsibilities without assuming the router provides them.
4. A test imports capstone/reference while claiming to grade capstone/starter. Why is that evidence invalid? What should the learner command import instead?
5. A DOM test waits one second and finds a CSS class. Suggest more meaningful interaction and query choices, and name a deterministic way to test request ordering.
6. All type checks, reference tests and production builds pass. Which release claims are still unsupported without further evidence? Name at least three and state whether this authorizes live publication.

Provide a brief release-note paragraph with verified scope and remaining acceptance checks. Answers and scoring.