Pocket Development

Execute an approved Pocket plan one task at a time or in explicitly parallel groups. The main agent coordinates work, runs mechanical checks, and dispatches independent read-only review; implementers own code changes.

Core principle: Every delegation is a contract. The packet is the contract. No packet, no spawn. Read execution-plan/index.md once to understand execution flow and dependencies, then open individual task files (execution-plan/tasks/T*-*.md) on demand when a task is ready to execute.

Core v4 lifecycle boundary

pocket-development is part of the local-first Core role. Core records neutral lifecycle events for approved specs, completed phases, and closed plans. Core does not call gh, does not merge pull requests, and does not close issues. A separately installed, optional adapter may consume durable events after a successful compatibility preflight. Core work and phase completion do not depend on that adapter; unavailable delivery leaves events pending for replay.

The v4 lifecycle commands use --json --contract 3. lifecycle transition commits local state and an event, lifecycle drain replays pending events in revision order without creating events, and lifecycle repair repairs recoverable log.json projection fields without emitting or dispatching an event. Active v3 plans with progress remain on v3; never silently convert their progress.

Startup: Initialize Execution Log

Run this before the first task, every session:

npx -y pocketto-pi log init "<plan_dir>" --json --contract 3