Treasure Hunt — UAT access

Choose a principal, or enrol a child. Then open the game or the admin console.

UAT access, not authentication. This deployment identifies a player by a principal id that the page stores and the client sends as a header. A real sign-in with passwords and a parent's consent receipt is Authentication.md's work and is not built yet — treat every account here as a test account, and never enter a real child's details.

1 · Enter the access code

Access code (the deployment's UAT_ACCESS_CODE)

2 · Enrol a child (guardian path)

The guardian is the principal you unlocked with; the child is a new principal id. This writes a consent row, a learner row and a guardian link — the same three rows POST /enrol/child writes for a real parent.

Child's principal id (e.g. p-uat-01)

Grade

Terms version

allow reflection notes (off by default)

What to test

Start a sitting, answer the cards, and check that the answer you chose explains itself afterwards — the rationale names the decision, and each wrong option says why it tempted before what it breaks. Then open the admin console and check the settings, the licences and the content flags.