feat(task3): open the development and test phases - #21
Merged
Merged
Conversation
Both hidden datasets exist now: 680 cases each, split so that no company appears on both sides, with the gold in the private workspaces and the questions published without answers or rule labels. The two rows derive their state rather than carrying a hard-coded true. Development runs on the same scoring workspace as practice, so it shares that flag; test has its own. A literal `true` is how a build with no Task 3 configuration ends up announcing an open phase -- the defect this table was rewritten to prevent. The test that pinned both rows to pending asserted a fact that has changed. It now asserts what still holds: no row may claim to be open while the site has no verified workspace, and development and practice, sharing a workspace, may never report different states. A new test carries the other half. "Development: Live" is an empty claim if the questions are nowhere to be found, so an open ranked phase must say where to get them, on the hub and in the guide both. It asserts only that direction -- a pending phase may still say where its data will live. Verified by mutation in final mode. Note: `npm test` reports one pre-existing failure, "renders direct web upload routes without a GitHub Issue intake", which expects /TASK 1 LIVE/ that the homepage redesign in a98fd52 removed. It fails identically on a clean main and is untouched here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NTMENQHcMNFRj6XC3NqxiD
Yan2266336
pushed a commit
that referenced
this pull request
Sep 23, 2026
Task 3's ranked phases opened in #21 while the rule forbidding teams from reading the expected values off a public data-quality service was still sitting on a branch, and the guide's link to the terms 404s because it lost the base path. This publishes both. Conflict resolved in tests/rendered-html.test.mjs: each branch inserted a test before the same anchor. Both are kept -- they guard different things, one that the rule is actually published on the pages participants read, one that an open ranked phase says where to get its questions. Both re-verified by mutation after the merge. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NTMENQHcMNFRj6XC3NqxiD
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both hidden datasets exist now: 680 cases each, split so that no company appears on both sides, with the gold in the private workspaces and the questions published without answers or rule labels.
The two rows derive their state rather than carrying a hard-coded true. Development runs on the same scoring workspace as practice, so it shares that flag; test has its own. A literal
trueis how a build with no Task 3 configuration ends up announcing an open phase -- the defect this table was rewritten to prevent.The test that pinned both rows to pending asserted a fact that has changed. It now asserts what still holds: no row may claim to be open while the site has no verified workspace, and development and practice, sharing a workspace, may never report different states.
A new test carries the other half. "Development: Live" is an empty claim if the questions are nowhere to be found, so an open ranked phase must say where to get them, on the hub and in the guide both. It asserts only that direction -- a pending phase may still say where its data will live. Verified by mutation in final mode.
Note:
npm testreports one pre-existing failure, "renders direct web upload routes without a GitHub Issue intake", which expects /TASK 1 LIVE/ that the homepage redesign in a98fd52 removed. It fails identically on a clean main and is untouched here.Claude-Session: https://claude.ai/code/session_01NTMENQHcMNFRj6XC3NqxiD