In-progress specs

Specs where part of the work is live and part is not. The folder is a filing decision; each spec's own status line is where you find out which half you are reading.

A spec belongs here when a reader could otherwise be misled — a phased build partway through, a feature shipped on one surface but not the other, or something written and working locally but not committed or deployed. It does not stay here: when the rest lands it moves to ../implemented/; if the work is abandoned, the built parts get their own spec and the rest goes to ../archived/.

Index and status-change procedure: ../README.md.

Spec	Built	Not yet
Millennium Invitational	The 24 October 2026 team event's site, pushed to the site's main: an opt-in teamScoring: "games" in the engine (a matchup won on games won, a bracket ranked by games won, total points, then head-to-head wins and points), the team template re-skinned from the pubmat and logo, and its events.json entry in event-data	The short link and QR image, the workbook fixes, sync setup and the dry run
Code and access protection	Built 2026-10-12, and deployed (all of it is in sage-tools-api 3.4.0 and the site's main): the played/series fix (sage-tools-api 3.1.1), the server reading workbooks as its service account (3.2.0), the attendance list through the API (3.3.0), the site's attendance view with its harness, the runbook and docs for Restricted facility workbooks, and LICENSE files	The owner's tasks (spike S1, quota checks O1–O2, then O3), and the Google, GitHub and Cloud settings of §2, §5, §6 and §7