diff --git a/quest/m0/benchmark/records-endpoint.md b/quest/m0/benchmark/records-endpoint.md index 1f23cb0c..112327c4 100644 --- a/quest/m0/benchmark/records-endpoint.md +++ b/quest/m0/benchmark/records-endpoint.md @@ -38,3 +38,32 @@ no repository had committed yet). Tests: a session in a checkout whose remote Kixel Quest serves is sent with its `owner/repo`; one it refuses stays queued on the host; and the override variable redirects both records and breakages. + +Decided 2026-11-15 (maintainer, `/quest-plan` of `/quest-run`'s +follow-ups): ✅ hold this quest until the forge reads land, and name the +deploy it waits on (rejected: only the Required link, leaving the deploy to +the Goal's end check; neither, relying on coordinators to know). + +Decided 2026-11-15 (same interview): ✅ the record wire stays lockstep for +now, revisited if records sit queued for days (rejected: the parser +ignoring unknown keys, which silently drops new fields at an older store +and still leaves a newer store refusing older hosts; ignoring them and +making new fields optional, which leaves every field optional for good). +`parseRecord` keeps rejecting any key it does not know, so Kixel Quest's +store and the hosts must run quest versions with the same record format; a +refused upload stays queued and retries each pass, so a lagging side delays +records rather than losing them. + +## Waiting + +- kixel-ai/kixel.quest: deploy `main`, so the store serves the record + endpoint. Check that `curl -s -A quest -X POST -H 'Authorization: Bearer + bogus' -H 'Content-Type: application/json' -d '{}' + https://kixel.quest/records -o /dev/null -w '%{http_code}'` prints `401`, + not `404`; its `quest/m0/deploy.md` automates deploys, and the maintainer + can run `just deploy` there meanwhile. + +## Required + +- [Forge reads](/quest/m0/github-quota/forge-reads.md) - `KixelQuest.serves()` + and the shared Kixel Quest token this sends with