fix(github): repair the json_escape test harness and re-sync with core

Two CI failures, both mine.

The json_escape parity tests wrote their payload into a per-script
subdirectory of tmp_path that nothing created, so every parametrised
case died with FileNotFoundError before reaching an assertion. They had
never run: bare `bash` resolves to the WSL launcher on my machine, so
`requires_bash` skipped them locally and CI was their first execution.
The helper now creates the directory.

The command-parity test then caught a real drift, which is what it is
for. Upstream #4456 changed core's taskstoissues to report an unreadable
extensions.yml instead of skipping hooks silently, in both the before
and after hook blocks. The extension copy still carried the old wording,
so the diff against core grew from 10 lines to 14. Ported both lines
rather than relaxing the assertion; the diff is back to the three script
paths plus the two that read the new TASKS value.

Rebased onto main to pick up that change.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: Yash-Chindam

extensions/github/commands/speckit.github.taskstoissues.md

@@ -20,7 +20,7 @@ You **MUST** consider the user input before proceeding (if not empty).
 **Check for extension hooks (before tasks-to-issues conversion)**:
 - Check if `.specify/extensions.yml` exists in the project root.
 - If it exists, read it and look for entries under the `hooks.before_taskstoissues` key
-- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
+- If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that `.specify/extensions.yml` could not be read (include the parser error) and that no hooks were checked, including any mandatory (`optional: false`) hooks registered there, then continue normally
 - Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
 - For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
   - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
@@ -77,7 +77,7 @@ git config --get remote.origin.url
 **Check for extension hooks (after tasks-to-issues conversion)**:
 Check if `.specify/extensions.yml` exists in the project root.
 - If it exists, read it and look for entries under the `hooks.after_taskstoissues` key
-- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
+- If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that `.specify/extensions.yml` could not be read (include the parser error) and that no hooks were checked, including any mandatory (`optional: false`) hooks registered there, then continue normally
 - Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
 - For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
   - If the hook has no `condition` field, or it is null/empty, treat the hook as executable

tests/extensions/github/test_github_extension.py

@@ -602,6 +602,9 @@ def _escape(script: Path, tmp_path: Path, value: str) -> str:
         )
         assert body, f"no json_escape found in {script}"
 
+        # Callers pass a per-script subdirectory so the two harnesses do not
+        # collide; pytest only creates tmp_path itself.
+        tmp_path.mkdir(parents=True, exist_ok=True)
         payload = tmp_path / "value.txt"
         payload.write_text(value, encoding="utf-8", newline="")
         harness = tmp_path / "harness.sh"