fix(md-copy): leading semicolon on the injected payload (ASI safety)

[phase3dev]

Summary

Addresses the Codex PR-review note on #6 (P2): prefix the injected webview payload with a leading ;.

When the self-contained IIFE is appended to webview/index.js after a bundle whose final statement is an expression with no trailing semicolon, JavaScript would parse it as a call on that expression (lastExpr(function(){...})()) and throw before the webview app initializes. The leading ; makes the patch safe regardless of the bundle's final token. This matches the design's "robust across builds" intent.

Not triggered by the current 2.1.170 bundle (it ends with }); this is forward-hardening.

Regenerated the three embeds (bash / node / python) from the updated source.

Test plan

• New node-exec test: append the block after a no-semicolon bundle and confirm it runs without throwing (tests/test_md_patcher.py)
• python3 -m unittest discover -s tests (86 cases)
• python3 tools/gen-embeds --check --strict · bash -n / ShellCheck / node --check

🤖 Generated with Claude Code

[phase3dev]

Superseded by #8. The leading-; ASI fix this PR added to #6's payload is already on main: the md-copy redesign in #8 rewrote the injected payload (which is why this PR now conflicts) and ships the leading ; in the source (webview-inject.js) and all three generated embeds (bash/node/python), plus the identical regression test test_appended_block_is_asi_safe_after_no_semicolon_bundle (tests/test_md_patcher.py). Nothing here is missing from main, so closing rather than merging.