fix(v0.6.6): prs create --json and issues create --json always failed

[0xLeif]

Summary

Fixes#15. gh pr create and gh issue create don't accept --json (only list/view do), but both prs create and issues create appended --json number,url,title directly to the create call — every JSON-mode create exited unknown flag: --json before creating anything.

The dangerous part: the natural recovery — drop --json and retry the identical command — looks like a no-op but actually succeeds, silently publishing a real PR/issue with whatever placeholder title/body was in the retry. Hit this live: an agent invocation failed on --json, retried without it, and published a PR titled "test title" on a real repo before anyone caught it.

Fix

Same pattern this file already uses for prs comment/issues comment: create without --json, parse the number out of the URL gh prints on stdout (tail -n1 for safety), then fetch the documented {number, url, title} shape from gh pr view / gh issue view.

Test Plan

• shellcheck --severity=warning on both changed scripts (matches CI)
• bash -n syntax check on both
• --help smoke test on both
• This very PR was opened with the fixed bin/fledge-github-prs create --json — if the fix were broken, this PR wouldn't exist with correct title/body
• plugin.toml bumped to 0.6.6, CHANGELOG.md updated

🤖 Generated with Claude Code

[0xLeif]

Summary

Fixes#15. gh pr create and gh issue create don't accept --json (only list/view do), but both prs create and issues create appended --json number,url,title directly to the create call — every JSON-mode create exited unknown flag: --json before creating anything.

The dangerous part: the natural recovery — drop --json and retry the identical command — looks like a no-op but actually succeeds, silently publishing a real PR/issue with whatever placeholder title/body was in the retry. Hit this live: an agent invocation failed on --json, retried without it, and published a PR titled "test title" on a real repo before anyone caught it.

Fix

Same pattern this file already uses for prs comment/issues comment: create without --json, parse the number out of the URL gh prints on stdout (tail -n1 for safety), then fetch the documented {number, url, title} shape from gh pr view / gh issue view.

Test Plan

• shellcheck --severity=warning on both changed scripts (matches CI)
• bash -n syntax check on both
• --help smoke test on both
• This very PR was opened with the fixed bin/fledge-github-prs create --json — if the fix were broken, this PR wouldn't exist with correct title/body
• plugin.toml bumped to 0.6.6, CHANGELOG.md updated

🤖 Generated with Claude Code

[0xLeif]

Summary

Fixes#15. gh pr create and gh issue create don't accept --json (only list/view do), but both prs create and issues create appended --json number,url,title directly to the create call — every JSON-mode create exited unknown flag: --json before creating anything.

The dangerous part: the natural recovery — drop --json and retry the identical command — looks like a no-op but actually succeeds, silently publishing a real PR/issue with whatever placeholder title/body was in the retry. Hit this live: an agent invocation failed on --json, retried without it, and published a PR titled "test title" on a real repo before anyone caught it.

Fix

Same pattern this file already uses for prs comment/issues comment: create without --json, parse the number out of the URL gh prints on stdout (tail -n1 for safety), then fetch the documented {number, url, title} shape from gh pr view / gh issue view.

Test Plan

• shellcheck --severity=warning on both changed scripts (matches CI)
• bash -n syntax check on both
• --help smoke test on both
• This very PR was opened with the fixed bin/fledge-github-prs create --json — if the fix were broken, this PR wouldn't exist with correct title/body
• plugin.toml bumped to 0.6.6, CHANGELOG.md updated

🤖 Generated with Claude Code

[0xLeif]

Summary

Fixes#15. gh pr create and gh issue create don't accept --json (only list/view do), but both prs create and issues create appended --json number,url,title directly to the create call — every JSON-mode create exited unknown flag: --json before creating anything.

The dangerous part: the natural recovery — drop --json and retry the identical command — looks like a no-op but actually succeeds, silently publishing a real PR/issue with whatever placeholder title/body was in the retry. Hit this live: an agent invocation failed on --json, retried without it, and published a PR titled "test title" on a real repo before anyone caught it.

Fix

Same pattern this file already uses for prs comment/issues comment: create without --json, parse the number out of the URL gh prints on stdout (tail -n1 for safety), then fetch the documented {number, url, title} shape from gh pr view / gh issue view.

Test Plan

• shellcheck --severity=warning on both changed scripts (matches CI)
• bash -n syntax check on both
• --help smoke test on both
• This very PR was opened with the fixed bin/fledge-github-prs create --json — if the fix were broken, this PR wouldn't exist with correct title/body
• plugin.toml bumped to 0.6.6, CHANGELOG.md updated

🤖 Generated with Claude Code

[0xLeif]

Summary

Fixes#15. gh pr create and gh issue create don't accept --json (only list/view do), but both prs create and issues create appended --json number,url,title directly to the create call — every JSON-mode create exited unknown flag: --json before creating anything.

The dangerous part: the natural recovery — drop --json and retry the identical command — looks like a no-op but actually succeeds, silently publishing a real PR/issue with whatever placeholder title/body was in the retry. Hit this live: an agent invocation failed on --json, retried without it, and published a PR titled "test title" on a real repo before anyone caught it.

Fix

Same pattern this file already uses for prs comment/issues comment: create without --json, parse the number out of the URL gh prints on stdout (tail -n1 for safety), then fetch the documented {number, url, title} shape from gh pr view / gh issue view.

Test Plan

• shellcheck --severity=warning on both changed scripts (matches CI)
• bash -n syntax check on both
• --help smoke test on both
• This very PR was opened with the fixed bin/fledge-github-prs create --json — if the fix were broken, this PR wouldn't exist with correct title/body
• plugin.toml bumped to 0.6.6, CHANGELOG.md updated

🤖 Generated with Claude Code

[0xLeif]

Summary

Fixes#15. gh pr create and gh issue create don't accept --json (only list/view do), but both prs create and issues create appended --json number,url,title directly to the create call — every JSON-mode create exited unknown flag: --json before creating anything.

The dangerous part: the natural recovery — drop --json and retry the identical command — looks like a no-op but actually succeeds, silently publishing a real PR/issue with whatever placeholder title/body was in the retry. Hit this live: an agent invocation failed on --json, retried without it, and published a PR titled "test title" on a real repo before anyone caught it.

Fix

Same pattern this file already uses for prs comment/issues comment: create without --json, parse the number out of the URL gh prints on stdout (tail -n1 for safety), then fetch the documented {number, url, title} shape from gh pr view / gh issue view.

Test Plan

• shellcheck --severity=warning on both changed scripts (matches CI)
• bash -n syntax check on both
• --help smoke test on both
• This very PR was opened with the fixed bin/fledge-github-prs create --json — if the fix were broken, this PR wouldn't exist with correct title/body
• plugin.toml bumped to 0.6.6, CHANGELOG.md updated

🤖 Generated with Claude Code

[0xLeif]

Summary

Fixes#15. gh pr create and gh issue create don't accept --json (only list/view do), but both prs create and issues create appended --json number,url,title directly to the create call — every JSON-mode create exited unknown flag: --json before creating anything.

The dangerous part: the natural recovery — drop --json and retry the identical command — looks like a no-op but actually succeeds, silently publishing a real PR/issue with whatever placeholder title/body was in the retry. Hit this live: an agent invocation failed on --json, retried without it, and published a PR titled "test title" on a real repo before anyone caught it.

Fix

Same pattern this file already uses for prs comment/issues comment: create without --json, parse the number out of the URL gh prints on stdout (tail -n1 for safety), then fetch the documented {number, url, title} shape from gh pr view / gh issue view.

Test Plan

• shellcheck --severity=warning on both changed scripts (matches CI)
• bash -n syntax check on both
• --help smoke test on both
• This very PR was opened with the fixed bin/fledge-github-prs create --json — if the fix were broken, this PR wouldn't exist with correct title/body
• plugin.toml bumped to 0.6.6, CHANGELOG.md updated

🤖 Generated with Claude Code

[0xLeif]

Summary

Fixes#15. gh pr create and gh issue create don't accept --json (only list/view do), but both prs create and issues create appended --json number,url,title directly to the create call — every JSON-mode create exited unknown flag: --json before creating anything.

The dangerous part: the natural recovery — drop --json and retry the identical command — looks like a no-op but actually succeeds, silently publishing a real PR/issue with whatever placeholder title/body was in the retry. Hit this live: an agent invocation failed on --json, retried without it, and published a PR titled "test title" on a real repo before anyone caught it.

Fix

Same pattern this file already uses for prs comment/issues comment: create without --json, parse the number out of the URL gh prints on stdout (tail -n1 for safety), then fetch the documented {number, url, title} shape from gh pr view / gh issue view.

Test Plan

• shellcheck --severity=warning on both changed scripts (matches CI)
• bash -n syntax check on both
• --help smoke test on both
• This very PR was opened with the fixed bin/fledge-github-prs create --json — if the fix were broken, this PR wouldn't exist with correct title/body
• plugin.toml bumped to 0.6.6, CHANGELOG.md updated

🤖 Generated with Claude Code