docs(versioning): define daily bot sync as third-figure resource release

CHANGELOG.md

@@ -25,10 +25,12 @@ and this project uses semantic version tags with a fixed role per figure:
 - Improved search-page readability and usability in `docs/search/index.html`.
 - Expanded short task labels into clearer full-form labels in UI controls and resource cards.
 - Standardized title casing for key UI labels and actions.
+- Documented that daily GitHub Actions bot resource sync updates are released as third-figure resource versions.
 
 ### Fixed
 - Prevented long resource titles and long unbroken strings from overflowing card boundaries.
 - Improved capitalization and display formatting for source and task text in search results.
+- Fixed quick-link paths from search page to dataset, ASR, and TTS pages to avoid 404 errors.
 
 ## [v1.0.1] - 2026-02-18
 ### Added

docs/release_process.md

@@ -31,6 +31,11 @@ Examples:
 - `v1.1.1`: code-fix release.
 - `v2.0.0`: next major milestone.
 
+Daily bot rule:
+
+- Daily GitHub Actions bot sync updates (`resource_sync.yml`) are resource updates.
+- If only bot-driven resource catalog changes are shipped, use the next `vMAJOR.CODE.RESOURCE+1` tag.
+
 ## Release Notes Location
 
 - Store release notes in [releases/README.md](releases/README.md).

docs/releases/v1.1.1.md

@@ -21,6 +21,10 @@ Code-fix release focused on search-page UI correctness, readability, and termino
 - `python scripts/validate_normalization.py data/processed/normalization_seed_v0.1.tsv`
 - `python -m pytest -q`
 
+## Daily Bot Updates
+
+- Daily GitHub Actions bot resource sync updates are treated as third-figure resource releases.
+
 ## Versioning Rule Applied
 
 This release follows the project rule:

docs/resource_cycle_runbook.md

@@ -43,5 +43,11 @@ After discovery, promote only approved resources:
 - Do not auto-promote candidates without evidence and license review.
 - Keep `status: verified` only for reviewed entries.
 - Do not promote "reference-only" resources where Pashto is incidental; only Pashto-centric resources are eligible.
-- Treat spelling variants as valid Pashto markers during review (`pashto`, `pukhto`, `pushto`, `pakhto`, `پښتو`).
+- Treat spelling variants as valid Pashto markers during review (`pashto`, `pukhto`, `pushto`, `pakhto`, `pashto-script`).
 - Generated files must be committed after catalog updates.
+
+## Versioning for Daily Bot Updates
+
+- Daily candidate-sync updates from GitHub Actions (`resource_sync.yml`) are resource updates.
+- When those updates are reviewed and released, increment the third figure in `vMAJOR.CODE.RESOURCE`.
+- Example sequence: `v1.1.1` (code fix) -> `v1.1.2` (bot resource release).