LLM misinterprets workspace-root-basename as parent directory

This is an issue observed from multiple azure-cloud-migrate integration test failures. The skill asks the agent to do things like

```
1. **Create** `-azure/` at workspace root
```

When the workspace is "/tmp/skill-test" and the agent needs to create such a directory to contain files for a "serverless-face-blur-service" app, the agent interprets this instruction as "create /tmp/serverless-face-blur-service-azure", instead of creating "/tmp/skill-test-azure" or "/tmp/skill-test/skill-test-azure". This triggers failures in the tests since they were searching for output from those two directories.

Example run:
https://agreeable-dune-0f718070f.1.azurestaticapps.net/nightly-runs.html?file=2026-05-14%2F25860219936%2Fazure-cloud-migrate%2Fazure-cloud-migrate_-_Integration_Tests_brownfield-lambda-webapp_migrates_lambda-refarch-webapp_to_Azure%2Fagent-metadata-2026-05-14T13-21-40-013Z.md