{"version":"2.1.219","anchor":"admin-workspace-helpers-get-a-random-per-run-token-and-path-","canonical_anchor":"admin-workspace-helpers-get-a-random-per-run-token-and-path-","heading":"Admin-workspace helpers get a random per-run token and path guards","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/admin-workspace-helpers-get-a-random-per-run-token-and-path-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Admin-workspace helpers get a random per-run token and path guards\n\nAdmin workspace helpers gained a random run marker and stricter name and path-traversal checks.\n\n**What**\n\nAdmin-workspace helper code gained a per-run marker and input validation patterns, with no confirmed user-facing surface in this build.\n\n**Details**\n\n- A module initialiser builds a random `zzadminwc`-prefixed marker from 8 random bytes.\n- New regexes reject characters such as `\/`, `@`, `#`, `?`, `\\` and whitespace in names.\n- A separate pattern catches dot-segment path traversal, including the `%2e` encoded form.\n- Whether any of this is reachable for users could not be resolved.\n\n**Evidence**\n\n`zzadminwc`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}