Exact route safety
Registered routes such as /content-architecture/, /semantic-pipeline/, /glossary/, /route-index/, and /public-copy-seo-refinement/ return without alias redirects when already canonical.
Redirect Loop Hotfix
Public Route Redirect Loop Hotfix
A static v6.7.0 deployment-blocker hotfix documenting exact-route redirect-loop prevention, canonical route safety, and public route stability for content architecture and other static pages.
v6.7.0 deployment blocker hotfix
Public static routes now avoid self-redirect loops.
The live error on /content-architecture/ was consistent with an exact route being processed as an alias and redirected back to its own canonical URL. This hotfix makes exact registered routes win before alias handling, preserves trailing-slash canonicalization for non-canonical exact routes, and disables WordPress canonical redirects for custom static routes.
Canonical slash behavior
Non-canonical exact route requests, such as /content-architecture, still redirect once to /content-architecture/ and then render without looping.
WordPress canonical guard
Custom static routes opt out of WordPress canonical redirect guessing so routed pages are handled by the theme renderer instead of bouncing through core canonical logic.
Deployment note
After installing the hotfix package, refresh WordPress permalinks if any static route still 404s, then verify /content-architecture/, /semantic-pipeline/, /route-index/, and /evidence-packets/ manually.
Boundary preserved
No runtime AI behavior, no endpoint execution, no writable GET actions, no state mutation through query-string URLs, and no command-and-control claim over other domains.