[fullsend-ai-coder]

Summary

This changes scripts/lib/github-code-ops.lib.sh so that both _forge_resolve_existing_pr_url and forge_list_prs_for_branch compare GitHub owner logins case-insensitively (jq ascii_downcase). The bundled scripts that inline the lib (post-code.sh, pre-code.sh, pre-code-jira.sh) are regenerated.

Why

REPO_FULL_NAME takes its owner spelling from ISSUE_URL, but gh pr list returns the canonical headRepositoryOwner.login. With an issue URL like https://github.com/Fullsend-Ai/agents/issues/123, the case-sensitive check dropped the matching same-repo PR. Recovery then failed closed, and post-code reported a creation failure for a PR that existed.

Head and base branch matching (headRefName, baseRefName, --head, --base) stays exact because git refs are case-sensitive. GitLab is unchanged.

Testing

• run_gh_create_pr_recover_test in scripts/post-code-test.sh now accepts an optional REPO_FULL_NAME (default org/repo).
• New fixture create-pr-already-exists-owner-case-mismatch-recovers: REPO_FULL_NAME=Org/repo, the API login is org, and there is one matching PR. Recovery returns its URL. This test fails without the lib change.
• forge_list_prs_for_branch has no direct test, so none was added. I checked its jq filter by hand against mixed-case input.
• scripts/post-code-test.sh passes in source and bundled modes, except for 3 signed-commits checks (code-harness-signed-commits-default-off, eval-code-harness-signed-commits-on, signed-commits-off-plain-push). Those 3 also fail on unmodified main.

Caveats

• make cannot run in the sandbox (/bin/sh is not permitted). I regenerated the bundles and checked them for staleness by running scripts/bundle-sh.sh directly over BUNDLE_SRCS. Please confirm with make check-bundle in CI.
• pre-commit could not fetch its hook repos (TLS error). shellcheck v0.10.0 (the pinned rev, with the configured args) passed when run directly, and so did lint-release-cases. scan-secrets covered gitleaks.
• make lint (skillsaw) did not run because uvx is unavailable. It lints only skills and agent docs, which this change does not touch.

🤖 Generated with Claude Code

---

Closes #1833

Post-script verification

• Branch is not main/master (agent/1833-owner-case-insensitive)
• Secret scan passed (gitleaks — f4acd0350dc9445112f4a0a6f781c02a31a64636..HEAD)
• PR body secret scan passed (gitleaks — no-git)
• Final PR description secret scan passed (gitleaks — no-git)

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 11:17 AM UTC · Completed 11:25 AM UTC

Commit: c999042 · View workflow run →

Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $1.30

[fullsend-ai-review]

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Small, well-specified bugfix with complete acceptance criteria coverage and matching scope, moderated to score 2 by protected script modifications and high recent churn across touched files.

[fullsend-ai-review]

Review

Findings

Medium

• [protected-path] scripts/lib/github-code-ops.lib.sh, scripts/post-code.sh, scripts/pre-code.sh, scripts/pre-code-jira.sh, scripts/post-code-test.sh — This PR modifies files under the protected scripts/ path. The PR links issue PR recovery treats GitHub owner logins as case-sensitive #1833, which authorizes the change, and the description explains the rationale. Human approval is still required for protected-path changes, whatever the context.