v0.1.4 — Remove files_to_edit; promote now requires human approval

Breaking

• files_to_edit removed entirely. The concept (introduced as a permission
  whitelist, downgraded to an advisory hint in 0.1.2) is gone from the whole
  pipeline:

  • the Ticket model no longer carries the field
  • ticket init no longer scaffolds it
  • the spec.md template drops its "Editable Files" section
  • update-metadata no longer infers it (and actively strips a stale field
    from older tickets)
  • pick / takeover JSON output no longer includes it

  Edit-scope guidance now lives solely in spec.md prose — the agent stays
  within the scope the spec describes.

  Migration: none required. Old tickets that still contain the field keep
  working — unknown metadata fields are ignored, and the next update-metadata
  run cleans the field up automatically.

Added

• Promote requires explicit user approval. codoop-ticket's Finalize stage
  now mandates showing the ticket summary (id / title / modules) and getting
  user confirmation before ticket promote, and forbids --force without
  prior approval. pending/ is the Loop 3 pickup queue — an unreviewed promote
  means an agent may start building from an unapproved design.

Fixed

• README links to the removed LOOP3_EXECUTION_GUIDE.md now point to
  docs/loop-3-agent-centric.md
• Stale skills/codoop-flow/scripts/ CLI paths updated to the actual
  codoop-ticket / codoop-execute script locations
• Removed discover --agent CLI examples replaced with the in-session
  /skill codoop-discover invocation

Full Changelog: v0.1.3...v0.1.4