Open the question board from the main website

[isPANN]

Clicking Open questions on the homepage or graph currently opens a “To be released” placeholder. This change opens the existing Open Question Board at /problem-reductions/open-questions/, including its search, chronological IDs, problem details and GitHub PR submission dropdown. The old #open-questions and open-problems.html URLs redirect there too.

Merge the registry directory PR before this PR. Registry entries and the GitHub submission links move to registry/<slug>.json; the deployment browser check expects that location.

The documentation workflow checks out GiggleLiu/autoresearch-gadgets on main using the existing PROJECT_READ_TOKEN, builds its board with uv and its committed lockfile, and includes only website/dist/ in the Pages artifact. The board has its own asset release and CSP; registry.json stays byte-for-byte unchanged so repository evidence paths remain valid. Only runs on main deploy; feature-branch dispatches can verify the complete artifact safely.

For example, click Open questions, choose All questions, search Q001, open the question and click Submit a solution. The dropdown selects Q001 and the GitHub edit link targets registry/bfs-tree-support.json.

Validation of the full implementation before the directory move (commit 3fe72b70):

• Built the board and the complete main website, guide, PDF and Rust API with real dependencies.
• All 50 browser checks pass with the site served under /problem-reductions/, including homepage/graph navigation, both legacy URLs and the submission flow.
• All four build tests pass, including asset resolution and preservation of registry evidence paths; the published registry also matches the source export byte-for-byte.
• All 12 newly added executable statements in the website builder are covered by the actual build and build tests.
• Desktop and mobile board appearance inspected; no console errors or mobile overflow.
• Node graph checks, npm audit and actionlint pass.

Four existing browser failures were reproduced on unmodified main and corrected: the CircuitSAT rule now targets DecisionSpinGlass; the ILP documentation check explicitly chooses its intended binary/f64 variant; and the graph layout check compares variant count with the published registry instead of assuming four variants. The layout and content assertions are retained.

The feature-branch documentation run passed: private-source checkout, board build, complete documentation build, all build/browser checks and Pages artifact upload. The existing PROJECT_READ_TOKEN works; no additional secret is required. Deployment was skipped as intended. Regular PR CI also passed for that implementation. Merge into main to deploy the board through the existing Pages workflow.

The previous failed push run had exactly the four browser failures described above; all four are fixed in this PR. The documentation build job uses identical steps and permissions for push and workflow_dispatch, with no event-specific build conditions. Its successful build job on commit 3fe72b70 passed all 50 browser checks and artifact upload. The actual push-triggered run will start when this PR merges into main.

For the registry directory update, rebuilt the board and main website and reran the homepage → board → submission-link browser test against the new layout; it passes. The generated registry export remains byte-for-byte unchanged.