Prime upstream sync candidate ready

[github-actions]

A clean Prime upstream candidate is ready for human review.

• Candidate branch: automation/prime-upstream-80bf72c8855c-from-81faafa37747
• Candidate commit: 4591e8acfb2adf5552c90edbf5f1373e192290b0
• Trusted candidate CI: https://github.com/pylon-code/prime-agent/actions/runs/33236575533
• Open the prefilled pull request: https://github.com/pylon-code/prime-agent/compare/pylon...automation/prime-upstream-80bf72c8855c-from-81faafa37747?expand=1&title=chore%3A%20sync%20Prime%20upstream%20through%2080bf72c8855c&body=%23%23%20Upstream%20range%0A%0A-%20Base%20previously%20shared%20with%20Pylon%3A%20%60d60fab8a76d9c169f945341f0ee3bde21903bb55%60%0A-%20Prime%20upstream%20head%3A%20%6080bf72c8855cacd0e299159682f11fcecc4f2924%60%0A-%20Compare%3A%20https%3A%2F%2Fgithub.com%2FPrimeIntellect-ai%2Fprime-agent%2Fcompare%2Fd60fab8a76d9c169f945341f0ee3bde21903bb55...80bf72c8855cacd0e299159682f11fcecc4f2924%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%2F33236575533%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 80bf72c8855c 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-80bf72c8855c-from-81faafa37747 as the head.

Expected pull request body

Upstream range

• Base previously shared with Pylon: d60fab8a76d9c169f945341f0ee3bde21903bb55
• Prime upstream head: 80bf72c8855cacd0e299159682f11fcecc4f2924
• Compare: PrimeIntellect-ai/prime-agent@d60fab8...80bf72c

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/33236575533
• 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.

[github-actions]

A clean Prime upstream candidate is ready for human review.

• Candidate branch: automation/prime-upstream-5b6c0e94e11a-from-02a53ddf7d55
• Candidate commit: ec12a2d42e15617c05befad97de43f1e2717331b
• Trusted candidate CI: https://github.com/pylon-code/prime-agent/actions/runs/33254368190
• Open the prefilled pull request: https://github.com/pylon-code/prime-agent/compare/pylon...automation/prime-upstream-5b6c0e94e11a-from-02a53ddf7d55?expand=1&title=chore%3A%20sync%20Prime%20upstream%20through%205b6c0e94e11a&body=%23%23%20Upstream%20range%0A%0A-%20Base%20previously%20shared%20with%20Pylon%3A%20%60d60fab8a76d9c169f945341f0ee3bde21903bb55%60%0A-%20Prime%20upstream%20head%3A%20%605b6c0e94e11a97fcfdd7a9fc9dc4f7acbda9c853%60%0A-%20Compare%3A%20https%3A%2F%2Fgithub.com%2FPrimeIntellect-ai%2Fprime-agent%2Fcompare%2Fd60fab8a76d9c169f945341f0ee3bde21903bb55...5b6c0e94e11a97fcfdd7a9fc9dc4f7acbda9c853%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%2F33254368190%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 5b6c0e94e11a 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-5b6c0e94e11a-from-02a53ddf7d55 as the head.

Expected pull request body

Upstream range

• Base previously shared with Pylon: d60fab8a76d9c169f945341f0ee3bde21903bb55
• Prime upstream head: 5b6c0e94e11a97fcfdd7a9fc9dc4f7acbda9c853
• Compare: PrimeIntellect-ai/prime-agent@d60fab8...5b6c0e9

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/33254368190
• 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.

[github-actions]

A clean Prime upstream candidate is ready for human review.

• Candidate branch: automation/prime-upstream-5b6c0e94e11a-from-8551520f42d0
• Candidate commit: a37efe92f88ae7234dcea1d065c0d3d76ac048cc
• Trusted candidate CI: https://github.com/pylon-code/prime-agent/actions/runs/33263277542
• Open the prefilled pull request: https://github.com/pylon-code/prime-agent/compare/pylon...automation/prime-upstream-5b6c0e94e11a-from-8551520f42d0?expand=1&title=chore%3A%20sync%20Prime%20upstream%20through%205b6c0e94e11a&body=%23%23%20Upstream%20range%0A%0A-%20Base%20previously%20shared%20with%20Pylon%3A%20%60d60fab8a76d9c169f945341f0ee3bde21903bb55%60%0A-%20Prime%20upstream%20head%3A%20%605b6c0e94e11a97fcfdd7a9fc9dc4f7acbda9c853%60%0A-%20Compare%3A%20https%3A%2F%2Fgithub.com%2FPrimeIntellect-ai%2Fprime-agent%2Fcompare%2Fd60fab8a76d9c169f945341f0ee3bde21903bb55...5b6c0e94e11a97fcfdd7a9fc9dc4f7acbda9c853%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%2F33263277542%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 5b6c0e94e11a 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-5b6c0e94e11a-from-8551520f42d0 as the head.

Expected pull request body

Upstream range

• Base previously shared with Pylon: d60fab8a76d9c169f945341f0ee3bde21903bb55
• Prime upstream head: 5b6c0e94e11a97fcfdd7a9fc9dc4f7acbda9c853
• Compare: PrimeIntellect-ai/prime-agent@d60fab8...5b6c0e9

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/33263277542
• 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.

[rynfar]

Regeneration claim after #11

PR #14 is merged as fd5cadc600f867a0a5a989064cce22934e9dad94, and issue #11 is closed. I am claiming the required fresh #8 candidate from that exact post-#11 pylon; stale candidate a37efe92f88ae7234dcea1d065c0d3d76ac048cc will not be reused.

• base: origin/pylon@fd5cadc600f867a0a5a989064cce22934e9dad94
• Prime upstream: upstream/main@a903d4b6768f484bd6d459b7b0aa7dee38e461e2
• branch: sync/prime-upstream-a903-from-fd5cadc
• isolated worktree: /Users/rynfar/.prime/worktrees/prime-upstream-a903-from-fd5cadc
• intended merge shape: merge commit with exact parents fd5cadc600f867a0a5a989064cce22934e9dad94 and a903d4b6768f484bd6d459b7b0aa7dee38e461e2

Owned regeneration scope:

• manually resolve the four known overlap files from the independently approved synthetic receipt:
  • packages/coding-agent/src/core/agent-session.ts
  • packages/coding-agent/src/modes/daemon/daemon-supervisor.ts
  • packages/coding-agent/test/agent-session-recursion.test.ts
  • packages/coding-agent/test/daemon-supervisor-monitor.test.ts
• audit all nonconflicting upstream changes against .pylon/features.yaml and .pylon/upstream-review.md;
• update fork ledgers only where the audit requires an adopt, hybridize, retain, or redesign decision;
• run affected Pylon, compatibility, process, full check/build, and hosted candidate validation;
• open only a reviewed draft PR against pylon, then record exact-head maintainer approval before merge.

No other active checkout or worktree will be modified. #13 and rynfar/comet#5 remain downstream and unclaimed until this regenerated artifact is reviewed and merged.