Prime upstream sync candidate ready

[github-actions]

A clean Prime upstream candidate is ready for human review.

• Candidate branch: automation/prime-upstream-fb2db8ee1b61-from-8ba8d79f8db0
• Candidate commit: 5a320cd29e6dee45d10d3a9b3902c414b356977e
• Trusted candidate CI: https://github.com/pylon-code/prime-agent/actions/runs/34612665074
• Open the prefilled pull request: https://github.com/pylon-code/prime-agent/compare/pylon...automation/prime-upstream-fb2db8ee1b61-from-8ba8d79f8db0?expand=1&title=chore%3A%20sync%20Prime%20upstream%20through%20fb2db8ee1b61&body=%23%23%20Upstream%20range%0A%0A-%20Base%20previously%20shared%20with%20Pylon%3A%20%601eee2938b4eeb7a4d72e17035adda669a89b63de%60%0A-%20Prime%20upstream%20head%3A%20%60fb2db8ee1b61c69d53a84404e617bc74d6f205c9%60%0A-%20Compare%3A%20https%3A%2F%2Fgithub.com%2FPrimeIntellect-ai%2Fprime-agent%2Fcompare%2F1eee2938b4eeb7a4d72e17035adda669a89b63de...fb2db8ee1b61c69d53a84404e617bc74d6f205c9%0A%0A%23%23%20Review%20requirements%0A%0A-%20Inspect%20upstream%20source%2C%20issues%2C%20pull%20requests%2C%20and%20release%20notes%20for%20overlaps%20with%20%60.pylon%2Ffeatures.yaml%60.%0A-%20Preserve%20Pylon%20behavior%20unless%20the%20ledger%20records%20an%20explicit%20adopt%2C%20hybridize%2C%20retain%2C%20or%20redesign%20decision.%0A-%20Resolve%20conflicts%20manually.%20This%20workflow%20never%20auto-resolves%20them.%0A-%20Review%20the%20source%20before%20marking%20this%20draft%20ready.%20Merge%20only%20with%20a%20merge%20commit.%0A-%20Trusted%20candidate%20CI%20runs%20without%20secrets%20or%20persisted%20Git%20credentials%3A%20https%3A%2F%2Fgithub.com%2Fpylon-code%2Fprime-agent%2Factions%2Fruns%2F34612665074%0A-%20Run%20affected%20Pylon%20integration%20checks%20before%20merging%20when%20an%20upstream%20change%20touches%20a%20Pylon%20integration%20boundary.%0A%0ACreated%20by%20the%20daily%20Pylon%20upstream%20synchronization%20workflow.%0A

When the form opens:

1. Keep the prefilled title chore: sync Prime upstream through fb2db8ee1b61 and body below.
2. Use Create draft pull request, not Create pull request.
3. Apply the pylon-upstream-sync label.
4. Keep pylon as the base and automation/prime-upstream-fb2db8ee1b61-from-8ba8d79f8db0 as the head.

Expected pull request body

Upstream range

• Base previously shared with Pylon: 1eee2938b4eeb7a4d72e17035adda669a89b63de
• Prime upstream head: fb2db8ee1b61c69d53a84404e617bc74d6f205c9
• Compare: PrimeIntellect-ai/prime-agent@1eee293...fb2db8e

Review requirements

• Inspect upstream source, issues, pull requests, and release notes for overlaps with .pylon/features.yaml.
• Preserve Pylon behavior unless the ledger records an explicit adopt, hybridize, retain, or redesign decision.
• Resolve conflicts manually. This workflow never auto-resolves them.
• Review the source before marking this draft ready. Merge only with a merge commit.
• Trusted candidate CI runs without secrets or persisted Git credentials: https://github.com/pylon-code/prime-agent/actions/runs/34612665074
• Run affected Pylon integration checks before merging when an upstream change touches a Pylon integration boundary.

Created by the daily Pylon upstream synchronization workflow.

The built-in GitHub Actions token cannot create the pull request. Mirror automation intentionally has no separate PAT or app token.