Roster authoring and browser service

The handoff preserves the independent Python/C# writer, factual bit schemas, stable references, college fields, extension metadata, match preparation, tests and the browser collaboration service. Standalone authoring is distinct from game acceptance.

The capacity experiment saved and reloaded 906 teams, 13,680 players and 3,790 uniform records with the documented native hooks. Synthetic clone names and stock art were fixtures. It is not proof that every roster size or mod is safe. A shared fixed string pool and per-section bounds remain relevant; unused overall ROS bytes do not imply unlimited names.

The documented hosted editor is https://openhoops.io/rostereditor, web0.3.0.dev3/source60k. It supports email accounts, private projects, owner/editor/viewer permissions, serialized revisions, comments, CSV/grid edits, recovery, workspace backups and private starter templates. The legacy handoff site is separate and does not change that service or expose its private data.

Source and runtime

workspace/roster-editor contains current source. checkpoints/roster-studio-60k preserves the exact deployed-source snapshot and its manifest. The accepted writer-runtime.zip is included separately when recoverable from the archived deployment; its hash is verified against the source60k evidence. Current cloud container/deployment configuration must be adapted intentionally, not copied blindly from a historical build script.

The topology is a Worker with static assets and same-origin HTTP, SQLite Durable Objects for project/account state, private R2 for immutable roster snapshots/metadata/patches, and a managed Python container for stateless authoring. Durable data is in R2/SQLite; the container filesystem is temporary. Accounts, sessions, recovery keys, sign-in email configuration and workspace contents are not source files and are not included in a public handoff.

Operational continuation

Keep project revisions/epochs and collaborator roles guarded. Preserve the original imported ROS, all companion files and before/after receipts. Export a complete workspace backup through supported ownership/authentication before retiring a live service. Restore into an independent destination, then compare ROS and companion exports byte-for-byte and verify rendered fields.

Deployment requires a Cloudflare account, managed container support, the declared Durable Object migrations/R2 bindings, a verified sign-in sender and private starter objects. The source includes deployment instructions and starter hashes; private starter ROS objects are not silently made public.

See browser service, deployment/operations, standalone editor, capacity, metadata and feedback/recovery.

The fictional non-D1 import research/receipts are preserved as development history; live user rosters/accounts remain private service data. Neither a schema check nor a field preview replaces native gameplay verification for a new roster.