Summary

• restore SecureCaseTrackerProjects and its CamelCase language checkout paths in the desired-state fleet manifest
• restore the regression contract that rejects the legacy lowercase host paths
• align the current README, Level-2 environment registry, learning-series documentation, man pages, and PowerShell examples
• keep the lowercase GitHub repository slugs unchanged and explicitly distinguish them from local checkout paths

Root cause

The schema-2 adoption follow-up accidentally aligned local host paths with the lowercase GitHub repository slugs. That reversed the previously approved CaseTracker workspace canonicalization and caused the maintenance orchestrator to recreate a second checkout tree and reject the existing operational registry.

Documentation impact

UpdateRequired: the manifest is the operational source of truth, while README guidance, both constitution copies, learning-series material, man pages, and script help are updated together. Historical evidence snapshots remain unchanged.

Validation

• python3 -m unittest scripts.tests.test_agentic_workspace_maintenance — 23 tests passed
• python3 -m unittest scripts.tests.test_maintenance_contracts — 14 tests passed
• git diff --check
• JSON parsing and constitution parity checks
• PowerShell parser checks for the changed scripts
• fleet registry validation — 32 canonical propagation targets
• fleet update validation — all 44 declared targets passed; the seven canonical CaseTracker checkouts fast-forwarded successfully
• exact eleven-preset validation for all seven canonical CaseTracker targets
• project statistics rendered and verified CURRENT
• gitleaks and the pre-push secret scan passed

Follow-up boundary

Two propagated documentation/help files intentionally differ in downstream repositories until this source PR is merged and a separately reviewed fleet propagation is performed. The duplicate lowercase checkout directories are not removed by this PR.