sync-initiative

Run this Skill after the child loop produces parent-truth. It sets the initiative status to sync_needed, updates the child row in TASK_GRAPH.md, folds stable decisions and contracts into parent artifacts, appends a SYNC_LOG.md entry, then returns the initiative to active status.

Child rows use three canonical statuses: active when more child-local work remains, blocked when an explicit blocker governs, and done when the child outcome is reconciled into parent truth. Untouched pending rows are promoted to ready when dependencies clear.

Yes, the child packet may live in a different owner repo from the parent initiative packet. The Skill reads the child packet including ARTIFACT_CANDIDATES.md from its declared Packet Root without copying it into the parent repo.

Set it to now only when stable reusable residue is ready for a durable-memory pass before more child work. Otherwise keep it as later, and note that durable-memory routing follows residue ownership rather than automatically the parent initiative repo.

Do not write tracked AGENTS.md files, treat sync as a second implementation phase, overwrite stable parent truth with tentative child notes, invent packet-state mutations outside the initiative contract, or copy the child packet into the parent repo.