v0.47.6

Pioneer 0.47.6: Safer task execution

Pioneer now keeps task recovery and authorization tied to the right owner. Codex rollouts recover more safely, skill pack tasks use the right admission checks, and memory access follows the person who started the work.

⚡ Highlights

• Codex rollouts can resume after their generation overlay is removed. Pioneer restores only the selected rollout link, without bringing back credentials, config, or MCP bootstrap files.
• Child tasks keep their original block reason after reconciliation instead of falling back to a generic status.
• CLI tasks using a skill pack now expand the selected skills for admission while preserving the pack for runtime attachments.
• Memory tools now use the initiating principal's current policy. A collaborator cannot lend another run its personal memory permissions.

🛠️ Fixed

• Stale rollout recovery validates the selected path and repairs only its own storage alias.
• Repeated task reconciliation keeps the original child task reason instead of replacing it with child_turn_blocked.

🔧 Changed

• Desktop and mobile bindings now share a client core with scoped snapshots, ordered updates, and idempotent effects.
• Added bounded, opt-in diagnostics for rendering, timeline consistency, and client delivery. Normal builds do not capture or export user content.

🙌 Thanks for making 0.47.6 happen

@superoskin

Full changelog: 0.47.5...0.47.6