Update to OBI Image Creation

{
  "description": "Identify and reconcile people, groups, locations, objects, structures, animals, and other reusable entities for an Open Bible Images project. Use before composition or character continuity work when scene elements need canonical OBI identity, or when review/feedback suggests the wrong entity or identity was used.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 215
    },
    {
      "relative_path": "references/entity-record.md",
      "size_in_bytes": 673
    }
  ],
  "name": "obi-entities",
  "skill_md_contents": "---\nname: obi-entities\ndescription: Identify and reconcile people, groups, locations, objects, structures, animals, and other reusable entities for an Open Bible Images project. Use before composition or character continuity work when scene elements need canonical OBI identity, or when review/feedback suggests the wrong entity or identity was used.\n---\n\n# OBI Entities\n\nBuild the project's entity set using [references/entity-record.md](references/entity-record.md). Reuse an existing OBI entity when it genuinely represents the same thing.\n\nWhen a canonical project JSON file is supplied, preserve all other sections, update only `entities`, increment its artifact revision and the project revision, and append a history/capability-run entry. If the work was triggered by feedback or review, link the entity revision back to that finding. If no project file is supplied, label the result `unpersisted`.\n\n## Workflow\n\n1. Read the brief, Scripture scope, research claims, existing composition, available OBI entity records, and the exact feedback/review finding when applicable.\n2. List every narratively or visually material person, group, place, object, structure, animal, and natural feature relevant to the question.\n3. Search for canonical OBI matches using stable identifiers and relationships, not title similarity alone.\n4. Record one of: matched, proposed_new, generic, uncertain, or excluded.\n5. For people, preserve the distinction between Entity, Portrayal, Variant, and scene-specific Appearance.\n6. Record time, age, location, ownership, part-of, and identity relationships when they affect continuity.\n7. When responding to feedback, revise only the affected entity match or identity decision and preserve unrelated entity records.\n8. Surface ambiguous matches and proposed new entities for human decision.\n9. If an entity correction changes the intended scene, return disposition `needs_composition_revision`; if it only changes a person's portrayal/appearance, return `needs_entity_revision` with a handoff to `$obi-character-continuity`.\n\n## Boundaries\n\n- Do not create or merge canonical OBI entities without explicit authorization.\n- Do not identify unnamed biblical figures more specifically than the text or evidence permits.\n- Do not turn every incidental background item into a canonical entity.\n- Do not define camera, lighting, or layout; those belong to composition.\n- Do not invent a character appearance; route that work to `$obi-character-continuity`.\n- Do not silently replace an existing entity merely because a review comment questions it; verify the identity first.\n\nCompletion means the composition can refer to stable entity records without hiding unresolved identity decisions, and any feedback-driven correction has a clear downstream handoff.\n\n## User-facing response\n\nShow only material entity matches, ambiguities, or decisions. For feedback-driven work, state whether the questioned identity was confirmed, corrected, or remains uncertain, and show the next action such as **Update character** or **Revise composition** when needed. Keep routine background entities and full record fields in the project file unless requested.\n"
}