Fix configurable visual recap runner shell

[CheckPickerUpper]

Follow-up to #2038 and #2046.

What changed

• run the configurable recap jobs with an explicit Bash shell
• keep the core compatibility bundle and extracted recap CLI bundle byte-identical to the canonical workflow
• cover the copied, reusable, and extracted-package workflows with regression assertions
• add patch changesets for @agent-native/core and @agent-native/recap-cli

Why

The runner configuration accepts GitHub-hosted Windows and macOS labels as well as self-hosted label arrays, but the recap steps use Bash syntax throughout. Without an explicit shell, a valid Windows runner configuration reaches the job and is interpreted by PowerShell. Pinning shell: bash at the job level makes the workflow contract match the configurations setup and doctor already accept.

Verification

• pnpm --filter @agent-native/recap-cli exec vitest --run src/pr-visual-recap-workflow.spec.ts (2 tests)
• pnpm --filter @agent-native/core exec vitest --run src/cli/recap.spec.ts --maxWorkers=25% (199 tests)
• pnpm --filter @agent-native/recap-cli typecheck
• pnpm --filter @agent-native/core typecheck
• pnpm guards (23 checks)
• pnpm exec oxfmt --check ...
• pnpm changeset status
• actionlint on both configurable workflows
• git diff --check

[github-actions]

Visual recap — skipped

The visual recap job did not run for this pull request. This is informational only and does not block the PR.

Recap skipped for ce7e529: external fork PR requires a maintainer to apply the recap label to the current head SHA.

[steve8708]

thanks @CheckPickerUpper! just need a merge conflict resolution then this is good to go

[builder-io-integration]

Builder reviewed your changes — looks good ✅

Review Details

Incremental Code Review Summary

The latest PR head is unchanged from the prior incremental review: it adds synchronized workflow constants to both packages, explicitly selects Bash for recap jobs on configurable runners, and covers the canonical, reusable, core-bundled, and recap-cli-bundled workflows with regression assertions. The package exports and duplicated constants are consistent, and the byte-identity checks protect the installer output from drifting from the canonical workflow.

No new actionable bugs, security issues, performance regressions, or release problems were found. Targeted tests passed again: @agent-native/recap-cli 2/2 and @agent-native/core 199/199. This remains a standard-risk infrastructure/package change.

🧪 Browser testing: Skipped — the PR only changes workflows, package exports, tests, and changesets; there is no user-facing browser impact.

[CheckPickerUpper]

Resolved the conflict against current main, and all checks are green now. Thanks!