flow-next-tracker-sync

# flow-next-tracker-sync The flow spec is the source of truth and quality layer. The tracker is a co-editable projection. Tracker activity never starts agents or changes Flow task state. ## Load the reached path Read [steps.md](steps.md) for the operation sequence and [references/adapter-interface.md](references/adapter-interface.md) for the normalized contract. Load only references needed by the reached path: - Body comparison or conflict: [references/body-merge.md](references/body-merge.md). - Status projection: [references/status-sync.md](references/status-sync.md). - Comment or question-valve content: [references/comments-sync.md](references/comments-sync.md). - Hybrid identifiers: [references/identity.md](references/identity.md). - Linear transport shape: [references/linear-ladder.md](references/linear-ladder.md), then only the reached MCP or GraphQL reference. - GitHub, GitLab, or Jira transport shape: the matching provider reference only. Never load an unselected provider merely because another reference links it. ## Deterministic boundary `flowctl tracker` owns tracker transport, normalization, credentials, retries, capability degradation, lifecycle ordering, receipts, and atomic local state. The skill supplies only approved semantic inputs and reacts to the structured result. Do not reconstruct provider requests in skill prose or shell. Use the lifecycle facade for event-driven projection: ```bash FLOWCTL="${CODEX_HOME:-$HOME/.codex}/scripts/flowctl" [...