daydokuthon 0.1.0__tar.gz

daydokuthon-0.1.0/Dockerfile

@@ -0,0 +1,15 @@
+FROM python:3.12-slim AS build
+WORKDIR /build
+COPY pyproject.toml README.md PYPI_README.md LICENSE MANIFEST.in server-requirements.lock ./
+COPY src ./src
+RUN pip wheel --no-cache-dir --wheel-dir /wheels -c server-requirements.lock ".[server]"
+
+FROM python:3.12-slim
+COPY --from=build /wheels /wheels
+RUN pip install --no-cache-dir --no-index --find-links=/wheels "daydokuthon[server]" \
+    && useradd --create-home daydokuthon \
+    && mkdir /data && chown daydokuthon:daydokuthon /data
+USER daydokuthon
+WORKDIR /data
+EXPOSE 8001
+CMD ["daydokuthon", "serve", "--host", "0.0.0.0", "--database", "/data/daydokuthon.db"]

daydokuthon-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

daydokuthon-0.1.0/MANIFEST.in

@@ -0,0 +1,15 @@
+recursive-include src/daydokuthon/assets *
+recursive-include src/daydokuthon/data *.json
+include src/daydokuthon/starter.txt
+include src/daydokuthon/py.typed
+recursive-include examples *.py *.json
+recursive-include docs *.md *.json
+include README.md
+include PYPI_README.md
+include LICENSE
+include Dockerfile
+include compose.yaml
+include server-requirements.lock
+prune tools
+prune tests
+global-exclude __pycache__ *.py[cod]

daydokuthon-0.1.0/PKG-INFO

@@ -0,0 +1,171 @@
+Metadata-Version: 2.4
+Name: daydokuthon
+Version: 0.1.0
+Summary: Honeycomb puzzle hackathon SDK, trace judge and replay platform
+License-Expression: Apache-2.0
+Keywords: hackathon,puzzle,honeycomb,calendar,validator
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Education
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: server
+Requires-Dist: fastapi<1,>=0.115; extra == "server"
+Requires-Dist: uvicorn<1,>=0.30; extra == "server"
+Provides-Extra: dev
+Requires-Dist: daydokuthon[server]; extra == "dev"
+Requires-Dist: pytest<10,>=8; extra == "dev"
+Requires-Dist: httpx<1,>=0.27; extra == "dev"
+Requires-Dist: build<2,>=1.2; extra == "dev"
+Requires-Dist: ruff<1,>=0.9; extra == "dev"
+Provides-Extra: publish
+Requires-Dist: build<2,>=1.2; extra == "publish"
+Requires-Dist: twine<8,>=6; extra == "publish"
+Dynamic: license-file
+
+# Daydokuthon
+
+**Write the algorithm. Record the moves. Replay the solution.**
+
+Daydokuthon is a Python SDK and hackathon platform for a honeycomb calendar puzzle. It supplies twelve pieces, a 50-cell hexagonal board, rotations/flips, collision checks, a JSON action recorder, an independent validator, and a replay visualizer. Participants implement their own solving strategy; no completed solver is included.
+
+Requires **Python 3.12 or later**. Licensed under **Apache-2.0**.
+
+## Install
+
+```shell
+# Participant SDK and validator — no third-party runtime dependencies
+python -m pip install daydokuthon
+
+# Add the local visualizer and central organizer server
+python -m pip install "daydokuthon[server]"
+```
+
+The visualizer is bundled. No Node installation, frontend build, database server, or GitHub access is needed.
+
+## Get started
+
+Create a working directory, download `challenge.json` from your organizer, then run:
+
+```shell
+daydokuthon init
+```
+
+This creates `solution.py` with the participant interface:
+
+```python
+from daydokuthon import PuzzleAlgorithm, Simulation
+
+
+class MyAlgorithm(PuzzleAlgorithm):
+    def solve(self, simulation: Simulation) -> None:
+        # Implement your greedy/search/backtracking strategy here.
+        # The supplied starter demonstrates placement of one piece only.
+        ...
+```
+
+Run your implementation to create a trace, validate it, and replay it:
+
+```shell
+daydokuthon run --algorithm solution:MyAlgorithm --challenge challenge.json --output submission.json
+daydokuthon validate submission.json --challenge challenge.json
+daydokuthon replay submission.json --challenge challenge.json
+```
+
+`python -m daydokuthon` supports the same commands. Replay requires the `[server]` extra and opens localhost:8002; use `--no-browser` to open it yourself.
+
+### Trying the SDK without an organizer
+
+Create a local `challenge.json` with these contents:
+
+```json
+{
+  "id": "my-local-challenge",
+  "date": "2026-06-01",
+  "title": "My local challenge",
+  "puzzle_version": "honeycomb-1"
+}
+```
+
+You can use this for local recording, validation and replay. For competition submissions, download the actual challenge: its ID, date and puzzle version must match the server.
+
+## Participant interfaces
+
+```python
+from daydokuthon import BOARD, PIECES, Challenge, HexCoordinate, Simulation
+from datetime import date
+
+simulation = Simulation(Challenge("local", date(2026, 6, 1)))
+print(len(PIECES))       # 12
+print(len(BOARD.cells))  # 50
+
+# Choose candidates in your own algorithm:
+piece = PIECES[0]
+for orientation in simulation.orientations(piece.id):
+    for origin in sorted(BOARD.coordinates):
+        if simulation.can_place(piece.id, origin,
+                                orientation.rotation, orientation.flipped):
+            simulation.place(piece.id, origin,
+                             orientation.rotation, orientation.flipped)
+            simulation.remove(piece.id)  # Record a backtracking step.
+            break
+    break
+```
+
+| Interface | Purpose |
+| --- | --- |
+| `PIECES`, `PIECES_BY_ID` | Immutable piece definitions with stable IDs P01–P12 |
+| `BOARD.cells`, `.coordinates`, `.by_value` | Corrected board layout and lookup |
+| `simulation.date`, `.exposed`, `.occupied`, `.placements` | Puzzle inputs and current state |
+| `simulation.orientations(piece_id)` | Deduplicated rotations and flips |
+| `simulation.can_place(piece_id, origin, rotation=0, flipped=False)` | Check legality without recording |
+| `simulation.place(...)` | Validate and record a whole-piece placement |
+| `simulation.remove(piece_id)` | Validate and record a removal |
+| `simulation.is_solved` | All twelve pieces cover exactly the 47 target cells |
+| `simulation.to_trace()` | JSON-serializable copy of recorded actions |
+| `validate_trace(raw, challenge)` | Independent replay and validation report |
+
+Origins are axial `HexCoordinate(q, r)` values, never pixels. Rotation is an integer from 0 to 5 in 60° steps; `flipped` is boolean. Transformation order is reflection, rotation, normalization, then translation. The final two board rows are `22 23 24 25 26 27 Fri` and `28 29 30 31 Sun Sat`.
+
+Failed moves raise `IllegalMove` and do not change the state or history. Repositioning a piece requires removal followed by placement. Exceptions during an algorithm's `solve` method still export the successfully recorded prefix. Incomplete results exit nonzero and can be replayed for debugging.
+
+## Organizer server
+
+Install `daydokuthon[server]`. Configure an organizer password of at least 12 characters and a persistent signing secret of at least 32 characters.
+
+PowerShell:
+
+```powershell
+$env:DAYDOKUTHON_ADMIN_PASSWORD = Read-Host 'Organizer password (12+ characters)'
+$env:DAYDOKUTHON_SECRET = python -c "import secrets; print(secrets.token_urlsafe(48))"
+daydokuthon serve --database ./daydokuthon.db
+```
+
+Linux/macOS:
+
+```shell
+read -rs -p 'Organizer password: ' DAYDOKUTHON_ADMIN_PASSWORD
+export DAYDOKUTHON_ADMIN_PASSWORD
+export DAYDOKUTHON_SECRET="$(python -c 'import secrets; print(secrets.token_urlsafe(48))')"
+daydokuthon serve --database ./daydokuthon.db
+```
+
+Open **http://127.0.0.1:8001/organizer** to publish challenges and review submissions. Participants use **http://127.0.0.1:8001/** to select a challenge, enter a roll number, and upload their JSON trace.
+
+- Challenges accept any valid date and optional opening/closing times.
+- Every bounded attempt is retained, including invalid JSON, incomplete solutions and late attempts.
+- The server records UTC receipt time after the complete upload arrives, before validation.
+- Private receipt links provide results and replay; only organizers can browse all attempts and export CSV.
+- The validator accepts any legal complete arrangement, independently of the solving approach.
+- The visualizer supports placement/removal animation, stepping, scrubbing, replay and speed controls.
+
+SQLite persistence is included. Default limits are 2 MiB and 10,000 actions; override using `DAYDOKUTHON_MAX_BYTES` and `DAYDOKUTHON_MAX_ACTIONS`. Set `DAYDOKUTHON_SECURE_COOKIE=true` behind HTTPS. Preserve the signing secret across restarts; protect the database and private receipt links. Roll numbers are self-reported identifiers.
+
+Uploaded files are **JSON data only**. The server never executes participant Python. It independently derives piece cells and checks schemas, types, versions, dates, orientations, board bounds, exposed cells, overlaps, removals and final coverage. Invalid traces identify the first failing action and replay only its legal prefix.
+
+Judging is correctness-only. Uploaded traces do not prove algorithm runtime, search efficiency, originality or participant identity. No public solution gallery or completed solver is bundled.

daydokuthon-0.1.0/PYPI_README.md

@@ -0,0 +1,141 @@
+# Daydokuthon
+
+**Write the algorithm. Record the moves. Replay the solution.**
+
+Daydokuthon is a Python SDK and hackathon platform for a honeycomb calendar puzzle. It supplies twelve pieces, a 50-cell hexagonal board, rotations/flips, collision checks, a JSON action recorder, an independent validator, and a replay visualizer. Participants implement their own solving strategy; no completed solver is included.
+
+Requires **Python 3.12 or later**. Licensed under **Apache-2.0**.
+
+## Install
+
+```shell
+# Participant SDK and validator — no third-party runtime dependencies
+python -m pip install daydokuthon
+
+# Add the local visualizer and central organizer server
+python -m pip install "daydokuthon[server]"
+```
+
+The visualizer is bundled. No Node installation, frontend build, database server, or GitHub access is needed.
+
+## Get started
+
+Create a working directory, download `challenge.json` from your organizer, then run:
+
+```shell
+daydokuthon init
+```
+
+This creates `solution.py` with the participant interface:
+
+```python
+from daydokuthon import PuzzleAlgorithm, Simulation
+
+
+class MyAlgorithm(PuzzleAlgorithm):
+    def solve(self, simulation: Simulation) -> None:
+        # Implement your greedy/search/backtracking strategy here.
+        # The supplied starter demonstrates placement of one piece only.
+        ...
+```
+
+Run your implementation to create a trace, validate it, and replay it:
+
+```shell
+daydokuthon run --algorithm solution:MyAlgorithm --challenge challenge.json --output submission.json
+daydokuthon validate submission.json --challenge challenge.json
+daydokuthon replay submission.json --challenge challenge.json
+```
+
+`python -m daydokuthon` supports the same commands. Replay requires the `[server]` extra and opens localhost:8002; use `--no-browser` to open it yourself.
+
+### Trying the SDK without an organizer
+
+Create a local `challenge.json` with these contents:
+
+```json
+{
+  "id": "my-local-challenge",
+  "date": "2026-06-01",
+  "title": "My local challenge",
+  "puzzle_version": "honeycomb-1"
+}
+```
+
+You can use this for local recording, validation and replay. For competition submissions, download the actual challenge: its ID, date and puzzle version must match the server.
+
+## Participant interfaces
+
+```python
+from daydokuthon import BOARD, PIECES, Challenge, HexCoordinate, Simulation
+from datetime import date
+
+simulation = Simulation(Challenge("local", date(2026, 6, 1)))
+print(len(PIECES))       # 12
+print(len(BOARD.cells))  # 50
+
+# Choose candidates in your own algorithm:
+piece = PIECES[0]
+for orientation in simulation.orientations(piece.id):
+    for origin in sorted(BOARD.coordinates):
+        if simulation.can_place(piece.id, origin,
+                                orientation.rotation, orientation.flipped):
+            simulation.place(piece.id, origin,
+                             orientation.rotation, orientation.flipped)
+            simulation.remove(piece.id)  # Record a backtracking step.
+            break
+    break
+```
+
+| Interface | Purpose |
+| --- | --- |
+| `PIECES`, `PIECES_BY_ID` | Immutable piece definitions with stable IDs P01–P12 |
+| `BOARD.cells`, `.coordinates`, `.by_value` | Corrected board layout and lookup |
+| `simulation.date`, `.exposed`, `.occupied`, `.placements` | Puzzle inputs and current state |
+| `simulation.orientations(piece_id)` | Deduplicated rotations and flips |
+| `simulation.can_place(piece_id, origin, rotation=0, flipped=False)` | Check legality without recording |
+| `simulation.place(...)` | Validate and record a whole-piece placement |
+| `simulation.remove(piece_id)` | Validate and record a removal |
+| `simulation.is_solved` | All twelve pieces cover exactly the 47 target cells |
+| `simulation.to_trace()` | JSON-serializable copy of recorded actions |
+| `validate_trace(raw, challenge)` | Independent replay and validation report |
+
+Origins are axial `HexCoordinate(q, r)` values, never pixels. Rotation is an integer from 0 to 5 in 60° steps; `flipped` is boolean. Transformation order is reflection, rotation, normalization, then translation. The final two board rows are `22 23 24 25 26 27 Fri` and `28 29 30 31 Sun Sat`.
+
+Failed moves raise `IllegalMove` and do not change the state or history. Repositioning a piece requires removal followed by placement. Exceptions during an algorithm's `solve` method still export the successfully recorded prefix. Incomplete results exit nonzero and can be replayed for debugging.
+
+## Organizer server
+
+Install `daydokuthon[server]`. Configure an organizer password of at least 12 characters and a persistent signing secret of at least 32 characters.
+
+PowerShell:
+
+```powershell
+$env:DAYDOKUTHON_ADMIN_PASSWORD = Read-Host 'Organizer password (12+ characters)'
+$env:DAYDOKUTHON_SECRET = python -c "import secrets; print(secrets.token_urlsafe(48))"
+daydokuthon serve --database ./daydokuthon.db
+```
+
+Linux/macOS:
+
+```shell
+read -rs -p 'Organizer password: ' DAYDOKUTHON_ADMIN_PASSWORD
+export DAYDOKUTHON_ADMIN_PASSWORD
+export DAYDOKUTHON_SECRET="$(python -c 'import secrets; print(secrets.token_urlsafe(48))')"
+daydokuthon serve --database ./daydokuthon.db
+```
+
+Open **http://127.0.0.1:8001/organizer** to publish challenges and review submissions. Participants use **http://127.0.0.1:8001/** to select a challenge, enter a roll number, and upload their JSON trace.
+
+- Challenges accept any valid date and optional opening/closing times.
+- Every bounded attempt is retained, including invalid JSON, incomplete solutions and late attempts.
+- The server records UTC receipt time after the complete upload arrives, before validation.
+- Private receipt links provide results and replay; only organizers can browse all attempts and export CSV.
+- The validator accepts any legal complete arrangement, independently of the solving approach.
+- The visualizer supports placement/removal animation, stepping, scrubbing, replay and speed controls.
+
+SQLite persistence is included. Default limits are 2 MiB and 10,000 actions; override using `DAYDOKUTHON_MAX_BYTES` and `DAYDOKUTHON_MAX_ACTIONS`. Set `DAYDOKUTHON_SECURE_COOKIE=true` behind HTTPS. Preserve the signing secret across restarts; protect the database and private receipt links. Roll numbers are self-reported identifiers.
+
+Uploaded files are **JSON data only**. The server never executes participant Python. It independently derives piece cells and checks schemas, types, versions, dates, orientations, board bounds, exposed cells, overlaps, removals and final coverage. Invalid traces identify the first failing action and replay only its legal prefix.
+
+Judging is correctness-only. Uploaded traces do not prove algorithm runtime, search efficiency, originality or participant identity. No public solution gallery or completed solver is bundled.