docs: end-to-end gardening — links, stale refs, tailscale.md update

Comprehensive documentation gardening across the merged repo:

- tailscale.md: fully rewritten with current ground truth. The netinfra
  pair now runs production Technitium with all knel.net records
  replicated. Both LAN IPs resolve knel.net device names and recurse
  externally. The old "NXDOMAIN / zone is stale" findings are replaced
  with the resolved state and current recommendations.
- AGENTS.md: rewritten with Gitea-compatible clickable relative links
  to all key scripts and docs. Autonomous commit/push policy
  prominently documented. SSH user corrected to localuser.
- README.md: directory table and docs table now use clickable links.
- All .md cross-references converted to Gitea-renderable relative links.
- Stale path references (ProjectCode/, Project-Tests/, ProjectDocs/)
  updated to current names (provisioning/, tests/) across all docs.
- Stale repo name "FetchApply" / "KNELServerBuild" updated to
  "PFVCluster" in actionable docs; historical AI-review docs tagged
  with an HTML comment notice.
- REFACTORING-EXAMPLES.md: tagged as historical (pre-refactor patterns).
- tests/README.md, dns-cluster-setup/README.md, docs/DEPLOYMENT.md,
  docs/SECURITY.md: path references fixed to current structure.

🤖 Generated with [Crush](https://github.com/charmassociates/crush)

Assisted-by: GLM-5 via Crush <crush@charm.land>

tests/README.md

@@ -1,8 +1,8 @@
-# TSYS FetchApply Testing Framework
+# PFVCluster Test Suite
 
 ## Overview
 
-This testing framework provides comprehensive validation for the TSYS FetchApply infrastructure provisioning system. It includes unit tests, integration tests, security tests, and system validation.
+This testing framework provides comprehensive validation for the PFVCluster infrastructure. It includes unit tests, integration tests, security tests, and system validation.
 
 ## Test Categories
 
@@ -30,22 +30,22 @@ This testing framework provides comprehensive validation for the TSYS FetchApply
 
 ### Run All Tests
 ```bash
-./Project-Tests/run-tests.sh
+./run-tests.sh
 ```
 
 ### Run Specific Test Categories
 ```bash
-./Project-Tests/run-tests.sh unit          # Unit tests only
-./Project-Tests/run-tests.sh integration   # Integration tests only
-./Project-Tests/run-tests.sh security      # Security tests only
-./Project-Tests/run-tests.sh validation    # Validation tests only
+./run-tests.sh unit          # Unit tests only
+./run-tests.sh integration   # Integration tests only
+./run-tests.sh security      # Security tests only
+./run-tests.sh validation    # Validation tests only
 ```
 
 ### Run Individual Tests
 ```bash
-./Project-Tests/validation/system-requirements.sh
-./Project-Tests/security/https-enforcement.sh
-./Project-Tests/unit/framework-functions.sh
+./validation/system-requirements.sh
+./security/https-enforcement.sh
+./unit/framework-functions.sh
 ```
 
 ## Test Results
@@ -130,7 +130,7 @@ The testing framework is designed to integrate with CI/CD pipelines:
 
 ```bash
 # Example CI script
-./Project-Tests/run-tests.sh all
+./run-tests.sh all
 test_exit_code=$?
 
 if [[ $test_exit_code -eq 0 ]]; then
@@ -163,12 +163,12 @@ fi
 ```bash
 # Enable debug output
 export DEBUG=1
-./Project-Tests/run-tests.sh
+./run-tests.sh
 ```
 
 ## Contributing
 
-When adding new functionality to FetchApply:
+When adding new functionality to PFVCluster:
 
 1. Add corresponding tests in appropriate category
 2. Run full test suite before committing