Port a merged change into a second repository

Why use this

1. A change that is straightforward in one SDK can interact differently with error handling, asynchronous behavior or public types in another. Copying the visible diff may preserve the shape of a fix while missing the behavior it was intended to change.

2. A porting review packet could connect the original behavioral intent to target-language decisions and compatibility questions. Maintainers could assess a proposed equivalent change before authorizing repository writes, test execution or a pull request.

Why an agent / simpler alternative

Useful judgment

Translate intent across local conventions and identify assumptions that do not carry between languages.

Simpler alternative

Apply a small manual patch when both repositories share the same structure and behavior.

Unsuitable when

The original change's intended behavior or the target repository's compatibility contract is unclear.

Proposed inputs

1. Name

   Original change packet

   Owner

   Source maintainer

   Minimum scope

   Merged diff, issue rationale and relevant test descriptions

   Quality check

   Separate intended behavior from incidental refactoring.

2. Name

   Target SDK context

   Owner

   Target maintainer

   Minimum scope

   Corresponding interfaces, conventions and supported-version policy

   Quality check

   Identify target-specific error and concurrency semantics.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only supplied excerpts and a target-change proposal without repository access.

Compatibility unknowns

1. Unknown: current runtime, target toolchain, repository permissions and test coverage.

External actions requiring approval

1. Repository writes, pull-request publication, externally exposed code and any merge or release.

Expected deliverable and review checks

Proposed artifact

Source-to-target change map with rationale, compatibility risks and proposed validation cases.

Critical checks

1. Each target edit connects to an intended source behavior.

2. Language-specific differences remain visible rather than being described as automatically equivalent.

Missing output evidence

No new workflow run or output inspection was performed for this overlay; use the canonical source-outcome references.

Failure signals and proposed responses

1. Signal

   The proposed port changes a public return type.

   Why it matters

   A local-looking fix could break existing clients.

   Proposed response

   Flag the interface change and request a target-maintainer compatibility decision.

2. Signal

   The original regression case depends on source-language semantics.

   Why it matters

   Copying its structure may not test the target failure.

   Proposed response

   Describe the underlying observable behavior and propose a target-specific case.

Effort and cost — unknown

Setup work

1. Identify counterpart interfaces and the original bug contract.

Ongoing review

1. Review semantic differences and later authorized test evidence.

Unknowns

1. Unknown: porting complexity, CI costs and maintainer review time.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional diff changes error handling; its target interface uses a different result type and concurrency convention.

Acceptance checks

1. List the semantic decisions needing review.

2. Draft a linked change plan without claiming equivalent runtime behavior.

Stop conditions

1. Real repository writes, compilation, tests or pull-request creation is required.

Limits

1. A plausible translation plan is not a validated port; target-language correctness needs separate authorized engineering work.