default-workflow: issue creation step fails with shell conditional syntax error

[rysweet]

Problem

The default-workflow recipe fails during Step 3 issue creation when used from an Azure DevOps-hosted repository / workflow context.

Observed failure:

Recipe: default-workflow
Status: ✗ Failed

workflow-prep: failed
step-03-create-issue [error]: bash step failed: Command failed (exit 2):
=== Step 3: Creating Tracking Issue ===
/bin/bash: -c: line 76: syntax error in conditional expression

This happened while running:

amplihack recipe run default-workflow \
  -c task_description='Fix storage PR stack CI failure: callsite-guard rejects direct Storage and LocalFsBackend construction in run checkpoint code after current dev merge. Route checkpoint storage construction through an allowed runtime/storage helper or backend factory, validate, propagate through storage PR stack, push, and monitor CI.' \
  -c repo_path=.

A similar failure occurred earlier in the same storage-stack cleanup effort when the workflow was invoked directly for code changes.

Environment

• Host repo: Azure Repos (https://dev.azure.com/acs-mdash/acs-mdash/_git/hyenas)
• Working directory: /home/azureuser/src/s2/hyenas
• Recipe: default-workflow
• Failing phase: workflow-prep → step-03-create-issue
• Failure type: shell parse error before issue creation

Impact

The workflow cannot complete the canonical default-workflow path for code changes in this environment. Agents are then forced to either stop or continue manually, which violates workflow discipline and causes quality/process drift.

Investigation notes

• Symptom: verified in a live run.
• Root cause: likely shell quoting / conditional-expression generation in the issue-creation step when rendered with this repo/task context.
• Evidence: the recipe runner reports /bin/bash: -c: line 76: syntax error in conditional expression from step-03-create-issue.

Acceptance criteria

• default-workflow no longer fails in step-03-create-issue with a shell parse error when run from an Azure Repos-hosted repository.
• If GitHub issue creation is not applicable for Azure Repos repos, the workflow degrades explicitly and visibly rather than emitting a shell syntax error.
• The issue-creation step is covered by a regression fixture with task descriptions/repo metadata containing punctuation, quotes, and Azure DevOps context.