fix: Update navigation and documentation for Historical Fingerprinter challenge

Author: aliyuldashev

docs/challenges/.nav.yml

@@ -1,8 +1,9 @@
 nav:
   - README.md
   - Active Challenges:
-      - ada_detection: ./ada_detection
+      - historical_fingerprinter: ./historical_fingerprinter
       - dev_fingerprinter: ./dev_fingerprinter
   - Inactive Challenges:
+      - ada_detection: ./ada_detection
       - humanize_behaviour: ./humanize_behaviour
       - ab_sniffer: ./ab_sniffer

docs/challenges/ada_detection/.nav.yml

@@ -1,4 +1,3 @@
 nav:
   - README.md
-  - Anti-Detect Automation Detection v2: v2.md
   - "*"

docs/challenges/ada_detection/README.md

@@ -77,7 +77,7 @@ Each file must be named exactly as shown and contain self-contained JavaScript (
 
 ## Challenge Versions
 
-- [**v2** (Active after Feb 14, 2026 14:00 UTC)](./v2.md) - Hardened detection with Fail-Fast scoring
+- [**v2** (Active after Feb 14, 2026 14:00 UTC)](depricated/v2.md) - Hardened detection with Fail-Fast scoring
 - [**v1** (Deprecated)](./depricated/v1.md)
 
 ## Resources & Guides

docs/challenges/ada_detection/depricated/v1.md

@@ -8,7 +8,7 @@ title: Anti-Detect Automation Detection
 
 **ADA Detection v1** focuses on behavioral detection inside NST-Browser where traditional static signals are masked. This version uses a payload-based flow with strict human safety requirements.
 
-For general challenge information, environment details, and plagiarism policies, please refer to the [AAD README](./README.md).
+For general challenge information, environment details, and plagiarism policies, please refer to the [AAD README](../README.md).
 
 ---
 
@@ -94,7 +94,7 @@ Any excessive human misclassification would reduce this to **0.0**.
 
 ## Submission Guide
 
-To build and submit your solution, please follow the [Building a Submission Commit](../../miner/workflow/3.build-and-publish.md) guide.
+To build and submit your solution, please follow the [Building a Submission Commit](../../../miner/workflow/3.build-and-publish.md) guide.
 
 ## Submission Templates
 

docs/challenges/ada_detection/v2.md …hallenges/ada_detection/depricated/v2.mddocs/challenges/ada_detection/v2.md renamed to docs/challenges/ada_detection/depricated/v2.md docs/challenges/ada_detection/v2.md renamed to docs/challenges/ada_detection/depricated/v2.md

@@ -16,7 +16,7 @@ title: Anti-Detect Automation Detection v2
 
 Scoring has transitioned to a **Fail-Fast** model, emphasizing accuracy across three critical pillars: Human Detection, Framework Detection (with a Selenium Safety Gate), and Protocol Accuracy.
 
-For general challenge information, environment details, and plagiarism policies, please refer to the [AAD README](./README.md).
+For general challenge information, environment details, and plagiarism policies, please refer to the [AAD README](../README.md).
 
 ---
 
@@ -138,7 +138,7 @@ Any excessive human misclassification, protocol misses, or missing Selenium dete
 
 ## Submission Guide
 
-To build and submit your solution, please follow the [Building a Submission Commit](../../miner/workflow/3.build-and-publish.md) guide.
+To build and submit your solution, please follow the [Building a Submission Commit](../../../miner/workflow/3.build-and-publish.md) guide.
 
 ## Submission Templates
 

docs/challenges/dev_fingerprinter/v2.md

@@ -16,7 +16,7 @@ For general information and technical setup, please refer to the [Main README](.
 
 ## Mandatory Requirements
 
-1. Use the template provided in the [`templates/commit/src/fingerprinter/`](./templates/commit/src/fingerprinter/fingerprinter.js) directory.
+1. Use the template provided in the `templates/commit/src/fingerprinter/` directory.
 2. Implement your logic within the `fingerprinter.js` file.
 3. Your SDK must:
    - Generate a single string (the "fingerprint").

docs/challenges/historical_fingerprinter/.nav.yml

@@ -1,3 +1,4 @@
 nav:
   - README.md
   - Historical Fingerprinter v1: v1.md
+  - "*"

docs/challenges/historical_fingerprinter/testing_manuals.md

@@ -0,0 +1,72 @@
+---
+title: Testing Manual
+---
+
+# Historical Fingerprinter Testing Manual
+
+This manual provides instructions for testing the Historical Fingerprinter challenge using Docker and Docker Compose.
+
+## Overview
+
+- Tests are designed to evaluate the effectiveness of your detection scripts against the Historical Fingerprinter challenge.
+- Uses Docker for easy submission and testing
+
+## Quick Start Guide
+
+### Prerequisites
+
+- Docker
+- Docker Compose
+
+### Step 0: Clone the Repository [skip if you cloned already]
+
+```bash
+git clone git@github.com:RedTeamSubnet/historical-fingerprinter-challenge.git historical_fingerprinter
+cd historical_fingerprinter
+```
+
+### Step 1: Provide Your all Scripts
+
+- Paste all of your all 3 scripts into **src/hfp_challenge/challenge/fingerprinter/src/submissions** folder with matching names.
+
+### Step 2: Update Configuration Files
+
+```bash
+cp .env.example .env
+cp ./templates/compose/compose.override.dev.yml ./compose.override.yml
+```
+
+### Step 3: Setting up environmental variables
+
+- Change `HFP_CHALLENGE_API_KEY` with your own preferred API key. You can use any string as API key, but make sure to update it in your detection scripts as well.
+
+### Step 4: Start the Challenge Server
+
+```bash
+docker compose up -d challenge-api
+```
+
+### Step 4: Test Your Bot
+
+- Visit <https://localhost:10001/docs>
+- Authenticate using provided authentication API that you put into the `.env` with `HFP_CHALLENGE_API_KEY` variable.
+    ![alt text](https://github.com/RedTeamSubnet/historical-fingerprinter-challenge/blob/08e3deea03d551a5d97b9f93c41b7b31a5c2ee01/docs/images/image.png?raw=true)
+- Test your detection files by running the `/score` endpoint
+- if you see the warning log(like `Please visit endpoint <URI> to complete human verification for the task.`) then open given uri in log in your browser to complete human verification in your side.
+
+## Important Notes
+
+- The server runs on port 10001 by default
+- Make sure port 10001 is available on your system
+- All interactions are logged for analysis. Miners can check logs by running `docker compose logs -f`
+- All commands must be executed from challenge's root directory.
+- If you want score justification, you can check all results with `results` endpoint after running the `score` endpoint.
+
+## Troubleshooting
+
+If you encounter issues:
+
+1. Check if Docker is running
+2. Verify port 10001 is not in use
+3. Check Docker logs using `docker compose logs`
+4. Ensure you have proper permissions to run Docker commands